-
Notifications
You must be signed in to change notification settings - Fork 370
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-8296] - APIv4, Validation & Endpoints for OBJGen2 #10677
Conversation
if (typeof cors_enabled === 'boolean') { | ||
setCORSData(cors_enabled); | ||
setSelectedCORSOption(cors_enabled); | ||
} |
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.
Type guard needed based on the way this was originally written. We are utilizing getAccess
as a general entrypoint for calling getBucketAccess
or getObjectACL
which have different type signatures. Not a fan, so I may clean up in a future PR.
Coverage Report: ✅ |
Looking at both E2E tests 👀 Edit: I see... going to put this back into draft temporarily until I update factories |
@@ -120,7 +120,7 @@ describe('object storage access key end-to-end tests', () => { | |||
it('can create an access key with limited access - e2e', () => { | |||
const bucketLabel = randomLabel(); | |||
const bucketCluster = 'us-east-1'; | |||
const bucketRequest = objectStorageBucketFactory.build({ | |||
const bucketRequest = createObjectStorageBucketFactory.build({ |
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.
Note: This is the start of cleaning up the factories. We were using the response interface as the type signature for the payload which I fixed here.
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.
Looks good
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.
Didn't observe any issues with Object Storage ✅
@@ -88,16 +89,23 @@ export interface ObjectStorageObjectURL { | |||
url: string; | |||
} | |||
|
|||
export interface ObjectStorageEndpointsResponse { |
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.
Should drop the Response
in this type name and make Endpoint
singular?
export interface ObjectStorageEndpointsResponse { | |
export interface ObjectStorageEndpoint { |
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.
Agreed - I'll update
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 actually make this name change in my next PR which deals with semantics.
Waiting to merge until after release is cut ✂️ |
Description 📝
Under this proposal, Cloud Manager uses this to determine which S3 endpoints or types of endpoints are available to the requesting customer when using the API to create a bucket in a particular region.
Changes 🔄
/v4/object-storage/endpoints
regions
array will contain newendpoint_type
fieldcors_enabled
upon creation because it defaults to true. This behavior should be updated to explicitly setcors_enabled
to either true or false.s3_endpoint
andendpoint_type
cors_enabled
andcors_xml
will benull
Note
When the new API features are disabled, this endpoint will silently ignore any new request fields, even if they are present and non-null. APIv4 will safely discard these fields instead of passing them to OSA.
Target release date 🗓️
N/A
Preview 📷
No visual changes
How to test 🧪
No testing to be done, just review the endpoint, spelling, and typescript types
When reviewing, compare type to the API specification linked on the internal ticket