-
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
r/aws_verifiedaccess_instance_logging_configuration #33864
r/aws_verifiedaccess_instance_logging_configuration #33864
Conversation
Community NoteVoting for Prioritization
For Submitters
|
f6eb067
to
ee62d68
Compare
ee62d68
to
95b4d19
Compare
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=TestAccVerifiedAccessInstanceLoggingConfiguration_' PKG=ec2 ACCTEST_PARALLELISM=2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/ec2/... -v -count 1 -parallel 2 -run=TestAccVerifiedAccessInstanceLoggingConfiguration_ -timeout 360m
=== RUN TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsIncludeTrustContext
=== PAUSE TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsIncludeTrustContext
=== RUN TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsLogVersion
=== PAUSE TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsLogVersion
=== RUN TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsCloudWatchLogs
=== PAUSE TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsCloudWatchLogs
=== RUN TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsKinesisDataFirehose
=== PAUSE TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsKinesisDataFirehose
=== RUN TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsS3
=== PAUSE TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsS3
=== RUN TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsCloudWatchLogsKinesisDataFirehoseS3
=== PAUSE TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsCloudWatchLogsKinesisDataFirehoseS3
=== RUN TestAccVerifiedAccessInstanceLoggingConfiguration_disappears
=== PAUSE TestAccVerifiedAccessInstanceLoggingConfiguration_disappears
=== CONT TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsIncludeTrustContext
=== CONT TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsS3
--- PASS: TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsIncludeTrustContext (51.94s)
=== CONT TestAccVerifiedAccessInstanceLoggingConfiguration_disappears
--- PASS: TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsS3 (60.81s)
=== CONT TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsCloudWatchLogs
--- PASS: TestAccVerifiedAccessInstanceLoggingConfiguration_disappears (24.77s)
=== CONT TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsKinesisDataFirehose
--- PASS: TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsCloudWatchLogs (45.39s)
=== CONT TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsCloudWatchLogsKinesisDataFirehoseS3
--- PASS: TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsKinesisDataFirehose (151.93s)
=== CONT TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsLogVersion
--- PASS: TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsLogVersion (50.41s)
--- PASS: TestAccVerifiedAccessInstanceLoggingConfiguration_accessLogsCloudWatchLogsKinesisDataFirehoseS3 (211.80s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/ec2 323.603s
@GlennChia Thanks for the contribution 🎉 👏. |
This functionality has been released in v5.21.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. |
Description
New resource:
aws_verifiedaccess_instance_logging_configuration
Relations
Relates #29689
References
Output from Acceptance Testing
Additional information
Default values per Instance
When Verified Access Instances are created, they come with a logging configuration with the following default values
Hence, when the
aws_verifiedaccess_instance_logging_configuration
resource is deleted, it should reset the logging configuration to the aboveValue for
bucket_owner
When S3 Logging configuration is set without a
bucket_owner
, the API will compute a value and return it. This presents issues when the S3 block is removed in Terraform. Removing it setsenabled
tofalse
but because there is still abucket_owner
value, the API returns an errorThe parameter AccessLogs.S3.BucketOwner cannot be used when AccessLogs.S3.Enabled is false
Hence, the expands function checks if
enabled
is first set totrue
before passing the value ofbucket_owner
. Ifenabled
isfalse
none of the other values matter and should not be passed to the API.Value for
ClientToken
ClientToken
usesuuid, err := uuid.GenerateUUID()
andaws.String(uuid)
instead ofaws.String(id.UniqueId()),
because of Regex Validation onClientToken
specifically for theModifyVerifiedAccessInstanceLoggingConfiguration
API.