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

Bug: conflicting s3 bucket policies #14

Open
jverhoeks opened this issue Jun 16, 2021 · 1 comment
Open

Bug: conflicting s3 bucket policies #14

jverhoeks opened this issue Jun 16, 2021 · 1 comment
Labels
bug 🐛 An issue with the system

Comments

@jverhoeks
Copy link

Found a bug? Maybe our Slack Community can help.

Slack Community

Describe the Bug

The s3 bucket policy conflicts with the bucket policy in the storage module. Every apply the policy is changed either one of the policies is active.

Expected Behavior

Changes to the policy are active and the terraform plan is consistent

Steps to Reproduce

Steps to reproduce the behavior:
Create module with

module "aws_config_storage" {
  source = "cloudposse/config-storage/aws"

  access_log_bucket_name  = local.log_bucket
  allow_ssl_requests_only = true
}
  1. Run plan and apply
  2. Run again plan and apply and it keeps changing

Screenshots

If applicable, add screenshots or logs to help explain your problem.

Environment (please complete the following information):

Terraform v0.14.11

  • provider registry.terraform.io/hashicorp/aws v3.45.0

Additional Context

Same problem in the flowlogs and cloudtrail bucket modules.

@jverhoeks jverhoeks added the bug 🐛 An issue with the system label Jun 16, 2021
@ghost
Copy link

ghost commented Aug 22, 2022

Related issue: this module does not respect the the policy variable. In the terraform-aws-cloudtrail-s3-bucket module, var.policy is incorporated as the source_json in the data document, which is absent in this module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 An issue with the system
Projects
None yet
Development

No branches or pull requests

1 participant