-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Add feature catalog files #12416
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
base: main
Are you sure you want to change the base?
Add feature catalog files #12416
Conversation
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 8m 49s ⏱️ Results for commit 9db648b. ♻️ This comment has been updated with latest results. |
- name: "DeleteBucketLifecycle" | ||
description: "Deletes the lifecycle configuration from the specified bucket." | ||
documentation: "https://docs.aws.amazon.com/AmazonS3/latest/API/API_DeleteBucketLifecycle.html" | ||
emulation_level: "mocked" |
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.
Tried to experiment here with emulation_level
being added at the api level, let me know your thoughts on this?
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.
We could use the cumulative of emulation_level
of api's to derive the one for a feature.
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.
does it happen often that emulation_level
of the feature is different from emulation level on api level? In this example emulation level is mocked
on both levels
0c8f8a1
to
c9946e4
Compare
Motivation
Add feature coverage file prototype for: ApiGateway, S3 and StepFunctions services