-
Notifications
You must be signed in to change notification settings - Fork 30
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
feat: add expire_rule support for buckets #687
Conversation
/run pipeline |
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 probably want to expose this as variable(s) in each of the patterns too, otherwise consumers of our DAs can't use it. cc @toddgiguere for feedback too
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.
@akocbek @ocofaigh everything looks good in this PR, but we will need to decide what to do with override.json in the future (I think). I can think of 2 ways to keep override.json updated:
- as we introduce new features through variable properties, we also add them to the sample override files to showcase
- override.json sample is derived off of the default landing zone configuration, and would match what is produced from a standard deploy in the
config
output
If option 1 is what we want, then we have done this change correctly.
If option 2 is the direction, then we would want to keep the override.json samples in line with the config produced from a standard landing zone deployment
/run pipeline |
/run pipeline |
Pipeline failed with |
/run pipeline |
🎉 This PR is included in version 5.12.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers