-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
resource/aws_guardduty_member: Support invite argument updates #4604
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.
one minor comment, otherwise LGTM 👍
detector_id = "${aws_guardduty_detector.test.id}" | ||
disable_email_notification = true | ||
email = "%[3]s" | ||
invite = %[4]t |
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.
by taking this approach (%[1]s
vs %s
) golint won't be able to determine if the types are wrong
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.
I really want to fix this upstream 😄
We should probably decide if we want to holistically go through all the test configurations and pick a format string style (indexed/unindexed) or use TF variables. Let's chat.
This has been released in version 1.20.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Followup to #4357
Reference: #2489
Changes proposed in this pull request:
invite
argument updatesOutput from acceptance testing: