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_macie_s3_bucket_association plans mutually exclusive classification_type settings #12589

Closed
MKgridSec opened this issue Mar 31, 2020 · 2 comments
Labels
service/macie Issues and PRs that pertain to the macie service.

Comments

@MKgridSec
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v0.12.23
+ provider.aws v2.55.0

Affected Resource(s)

  • aws_macie_s3_bucket_association

Terraform Configuration Files

resource "aws_macie_s3_bucket_association" "bucket_example" {
  bucket_name = "bucketymcbucketface"

  classification_type {
    one_time = "NONE"
  }
}

Debug Output

Panic Output

Expected Behavior


An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_macie_s3_bucket_association.bucket_example will be created
  + resource "aws_macie_s3_bucket_association" "bucket_example" {
      + bucket_name = "bucketymcbucketface"
      + id          = (known after apply)

      + classification_type {
          + one_time   = "NONE"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Actual Behavior

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_macie_s3_bucket_association.bucket_example will be created
  + resource "aws_macie_s3_bucket_association" "bucket_example" {
      + bucket_name = "bucketymcbucketface"
      + id          = (known after apply)

      + classification_type {
          + continuous = "FULL"
          + one_time   = "NONE"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Steps to Reproduce

  1. terraform plan
  2. Review plan output: of note: both classification types appear, which are contradictory/ mutually exclusive settings per https://www.terraform.io/docs/providers/aws/r/macie_s3_bucket_association.html

Important Factoids

I'm trying to only classify newly uploaded files and not perform a full classification of the bucket.

References

@ghost ghost added the service/macie Issues and PRs that pertain to the macie service. label Mar 31, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Mar 31, 2020
@ewbankkit
Copy link
Contributor

@MKgridSec Thanks for raising this.
In your example it's the classification_type.continuous attribute that is being set to FULL (which is the default and only currently available value). This will not conflict with the classification_type.one_time attribute.

@github-actions github-actions bot removed the needs-triage Waiting for first response or review from a maintainer. label Oct 5, 2021
@github-actions
Copy link

github-actions bot commented Jun 4, 2022

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
service/macie Issues and PRs that pertain to the macie service.
Projects
None yet
Development

No branches or pull requests

3 participants