Closed gtmtech closed 1 year ago
Voting for Prioritization
Volunteering to Work on This Issue
Closed by #30736, merged to main
via #31392
This functionality has been released in v5.0.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 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.
Description
https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateOrganizationConfiguration.html#guardduty-UpdateOrganizationConfiguration-request-autoEnableOrganizationMembers specifies that there is are 2 different types of arguments related to autoEnabling -
autoEnable
andautoEnableOrganizationMembers
.In
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/guardduty_organization_configuration
, onlyautoEnable
is supported.It would be good to have support for
autoEnableOrganizationMembers
as well as this is currently missing functionalityAffected Resource(s) and/or Data Source(s)
Potential Terraform Configuration
References
Couldn't find any existing issues about this including in closed.
Would you like to implement a fix?
No