fix: Include aws_s3_directory_bucket ID in s3_bucket_id output
#325
Conversation
This file contains hidden or 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
toneill818
changed the title
bryantbiggs
changed the title
s3_bucket_id output
bryantbiggs
changed the title
s3_bucket_id outputaws_s3_directory_bucket ID in s3_bucket_id output
bryantbiggs
approved these changes
Jun 4, 2025
antonbabenko
pushed a commit
that referenced
this pull request
Jun 4, 2025
## [4.10.1](v4.10.0...v4.10.1) (2025-06-04) ### Bug Fixes * Include `aws_s3_directory_bucket` ID in `s3_bucket_id` output ([#325](#325)) ([0d8fc54](0d8fc54))
|
This PR is included in version 4.10.1 🎉 |
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.
Description
Use the id of the s3 bucket or the directory bucket instead of the policy.
Motivation and Context
When attaching a policy after the bucket creation, any resource dependent on the output
s3_bucket_idwill show needing modified and possibly destroyed and recreated. This change will use the bucket resources directly to determine the bucket id instead of reading the policy first.Breaking Changes
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request