-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upcoming: [M3-8378] - OBJ Cleanup #10857
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work with the clean-up 👍. Good catch on removing the react-hook-form logic for now.
- Removed react-hook-form logic as planned ✅
- No crash on details/create drawer page ✅
- Rate limit table visible only for E2 and E3 endpoint types ✅
- The Create Bucket drawer now displays each additional step once we have the preceding information selected ✅
Apart from the above, I observed a strange behavior: when the OBJ Gen 2
flag is enabled, reloading the application while on the SSL tab or Properties tab doesn't load the data (with mocked or real data).
I noticed:
const { data: bucketsData } = useObjectStorageBuckets(isObjectStorageGen2Enabled);
in BucketDetail/index.tsx
at Line 53 returns undefined
when isObjectStorageGen2Enabled is explicitly set after reloading the application on those tabs . The function defaults to true if the flag is not passed, and it works fine in that case. I’m not sure if others are observing the same behavior or if it’s due to account capabilities for me.
And the same in the case of Properties tab, too.
@jaalah-akamai - looks like we caught the same bug 😆 Oops haha, going to close my PR, and could you unskip the BucketRateLimitTable tests in your PR? I'd previously had to skip them due to the bug |
Yea that's expected because there's no real data yet, it's all mocked. Also when you refresh on the tab, our mocked bucket labels and endpoint_types change since they're randomized and the bucket you were looking at no longer exists. See serverHandlers.ts#L979-L985 |
Coverage Report: ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed:
✅ When selecting "Details" for any E2/E3 endpoint bucket:
- Drawer should open and bucket rate limits table should show
✅ When creating a bucket:
- Once a region is selected, endpoint types show
- Once we select endpoint types, bucket rate limits show (except for E0/E1 of course)
❓ On the bucket details page Properties tab for E0-E3 endpoint types:
- Ensure title, description, and table all look good
This is what I saw on the Properties tab of E0 and E1 buckets. There seems to be a Save
button, although there's nothing to Save. Is that unexpected? (The drawer looks fine.)
Tab | Drawer |
---|---|
) : ( | ||
'This endpoint type supports up to 750 Requests Per Second (RPS). ' | ||
)} | ||
Understand <Link to="#">bucket rate limits</Link>. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two questions for my own knowledge, not directly related to these PR's changes:
- Have we moved away from using "Learn more about [topic]." in our copy? This is the first time I remember seeing "Understand [topic]." and it's used multiple times. I was wondering whether that's intentional or due to some inconsistency in tech writing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- I'll confirm with TW
- In rare cases, the dropdown must display a specific endpoint hostname (s3_endpoint) along with the endpoint type to distinguish between two assigned endpoints of the same type. This is necessary for multiple Gen1 (E1) assignments in the same region. Essentially, this mock demonstrates that if an s3_endpoint is provided, we want to display it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TW wants to keep it as is even though we use it in one other place
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for confirming and for the dropdown explanation. Any verdict on the Save
button?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am lacking some context about the feature but PR is doing what it describes and fix the issue mentioned ✅
Related
Properties
Tab for Object Storage Gen2 #10797Changes 🔄
BucketRateLimitTable
and corresponding files. This is far from being ready and it introduced complexity since this component is used in 3 different places. This will most likely be a 2025 initiative to add this logic in when it's ready.BucketRateLimitTable.tsx
since we were repeating that in 3 different places.Target release date 🗓️
N/A
How to test 🧪
Prerequisites
Reproduction steps
(How to reproduce the issue, if applicable)
BucketDetailsDrawer
Verification steps
(How to verify changes)
Pull down branch or preview link
Select "Details" for any E2/E3 endpoint bucket:
Create a bucket and observe:
Go to bucket details page and then properties tab
As an Author I have considered 🤔
Check all that apply