feat(bucketLifecycle): allow for prefix #214
Open
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.
In the case of the central logs bucket (log-centralization-methods), there are 16 different prefixes that logs are aggregated within the single bucket.
Without the ability to assign a prefix, each bucket only has the ability for a bucket wide S3 transition plan.
This allows logs from different sources to be transitioned at different periods.
Further move,
reports.costAndUsageReport.lifecycleRules
does not add a rule prefix in the central bucket (as one might expect):