Skip to content
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

aws_s3_bucket_invalid_region_rule: Fix false positives #442

Merged
merged 1 commit into from
Sep 18, 2019

Conversation

wata727
Copy link
Member

@wata727 wata727 commented Sep 17, 2019

Fixes #441

Unfortunately, BucketLocationConstraint is also outdated. This PR switches the rule into manual maintained one, updates the valid region list.

See also https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region

@@ -23,16 +21,27 @@ func NewAwsS3BucketInvalidRegionRule() *AwsS3BucketInvalidRegionRule {
attributeName: "region",
enum: []string{
"EU",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you use EU, terraform will fail when reading the resource, but the creation will succeed. Although it should not be used newly, EU may already exist as a valid value.
This means to allow false negatives, but it makes sense here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Consider removing/changing aws_s3_bucket_invalid_region check
1 participant