-
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
[Bug]: Add additional configuration parameters to resource:aws_cloudformation_stack_set_instance #26917
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Following |
Closed via #37898. |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
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. |
Terraform Core Version
v1.2.9
AWS Provider Version
v4.31.0
Affected Resource(s)
aws_cloudformation_stack_set_instance
Expected Behavior
When creating an
aws_cloudformation_stack_set_instance
resource, I expect to be able to specify theAccountId
parameter, whilst using thepermission_model
= "SERVICE_MANAGED".Actual Behavior
When trying to deploy an
aws_cloudformation_stack_set_instance
resource, you are able to specifyorganizational_unit_ids
as part of thedeployment_targets
configuration. However, you are not able to provide additional configuration items such as:The above are supported via cloudformation as per: https://awscli.amazonaws.com/v2/documentation/api/latest/reference/cloudformation/create-stack-instances.html
When specifying only AccountId and using the SERVICE_MANAGED permission model, the terraform apply fails. The error message is also misleading as it is possible to target account ids AND use a SERVICE_MANAGED permission model. However the syntax for doing this requires the configuration items listed above.
Relevant Error/Panic Output Snippet
The text was updated successfully, but these errors were encountered: