Stability - s3_lifecycle #448
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ansibullbot
added
WIP
tremble
force-pushed
the
reenable/s3_lifecycle
branch
from
b07817a to
958bc6e
Compare
…ally susceptible to eventual consistency
tremble
force-pushed
the
reenable/s3_lifecycle
branch
2 times, most recently
from
fafc84a to
63170a4
Compare
…o enable/disable a rule)
tremble
force-pushed
the
reenable/s3_lifecycle
branch
from
63170a4 to
958ec4a
Compare
tremble
commented
Mar 25, 2021
alinabuzachis
approved these changes
Mar 25, 2021
|
Tests passing and approval in place. Merging |
alinabuzachis
pushed a commit
to alinabuzachis/community.aws
that referenced
this pull request
Jul 19, 2021
* Add aws retry * re-enable lifecycle tests * changelog * Rename S3 bucket used by tests * Cleanup docs * Use datetime to be a little more flexible with the date formats * Rework and add support for waiting for changes to propagate * Wait for changes to propagate in tests s3 lifecycle events are especially susceptible to eventual consistency * Test examples are also idempotent... * More changelogs * Catch Amazon's "Nothing Changed" error (can happen when just trying to enable/disable a rule)
alinabuzachis
pushed a commit
to alinabuzachis/community.aws
that referenced
this pull request
Jul 19, 2021
* Add aws retry * re-enable lifecycle tests * changelog * Rename S3 bucket used by tests * Cleanup docs * Use datetime to be a little more flexible with the date formats * Rework and add support for waiting for changes to propagate * Wait for changes to propagate in tests s3 lifecycle events are especially susceptible to eventual consistency * Test examples are also idempotent... * More changelogs * Catch Amazon's "Nothing Changed" error (can happen when just trying to enable/disable a rule)
danielcotton
pushed a commit
to danielcotton/community.aws
that referenced
this pull request
Nov 23, 2021
* Add aws retry * re-enable lifecycle tests * changelog * Rename S3 bucket used by tests * Cleanup docs * Use datetime to be a little more flexible with the date formats * Rework and add support for waiting for changes to propagate * Wait for changes to propagate in tests s3 lifecycle events are especially susceptible to eventual consistency * Test examples are also idempotent... * More changelogs * Catch Amazon's "Nothing Changed" error (can happen when just trying to enable/disable a rule)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Attempt to get the s3_lifecycle tests back in service
ISSUE TYPE
COMPONENT NAME
s3_lifecycle
ADDITIONAL INFORMATION
DEPENDS-ON: ansible-collections/amazon.aws#271