We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The latest AWS provider version 4.0.0 introduces multiple breaking changes, especially regarding the aws_s3_bucket resource (see the migration guide).
aws_s3_bucket
The following snippet will mark these violations due to a change in the resource structure:
resource "aws_s3_bucket" "example" { bucket = "example" } resource "aws_s3_bucket_acl" "example" { bucket = aws_s3_bucket.example.id acl = "private" } resource "aws_s3_bucket_server_side_encryption_configuration" "example" { bucket = aws_s3_bucket.example.id rule { apply_server_side_encryption_by_default { kms_master_key_id = aws_kms_key.example.arn sse_algorithm = "aws:kms" } } } resource "aws_s3_bucket_versioning" "example" { bucket = aws_s3_bucket.example.id versioning_configuration { status = "Enabled" } } resource "aws_kms_key" "example" { description = "example" enable_key_rotation = true multi_region = false }
The text was updated successfully, but these errors were encountered:
Do we have any solution for this change ?
Sorry, something went wrong.
@zanilgupta not yet. We need to update the policies to account for this change.
harkirat22
Successfully merging a pull request may close this issue.
Description
The latest AWS provider version 4.0.0 introduces multiple breaking changes, especially regarding the
aws_s3_bucket
resource (see the migration guide).What I Did
The following snippet will mark these violations due to a change in the resource structure:
The text was updated successfully, but these errors were encountered: