-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Macie Macie2 Classification Results - Export Configuration #19856 #26105
Macie Macie2 Classification Results - Export Configuration #19856 #26105
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀.
% make testacc TESTARGS='-run=TestAccMacie2_serial/ClassificationExportConfiguration' PKG=macie2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/macie2/... -v -count 1 -parallel 20 -run=TestAccMacie2_serial/ClassificationExportConfiguration -timeout 180m
=== RUN TestAccMacie2_serial
=== RUN TestAccMacie2_serial/ClassificationExportConfiguration
=== RUN TestAccMacie2_serial/ClassificationExportConfiguration/basic
--- PASS: TestAccMacie2_serial (49.57s)
--- PASS: TestAccMacie2_serial/ClassificationExportConfiguration (49.57s)
--- PASS: TestAccMacie2_serial/ClassificationExportConfiguration/basic (49.57s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/macie2 55.719s
@nickyamanaka Thanks for the contribution 🎉 👏. |
This functionality has been released in v4.25.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #19856
Two things:
so my comparison might be unorthodox to check if the object are empty or if the resource already exists. Can I get some feedback for this approach? I could go checking
if output.Configuration.SetS3Destination != nil
if that makes more sense.Output from acceptance testing: