You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The resources and data sources in this provider are generated from the CloudFormation schema, so they can only support the actions that the underlying schema supports. For this reason submitted bugs should be limited to defects in the generation and runtime code of the provider. Customizing behavior of the resource, or noting a gap in behavior are not valid bugs and should be submitted as enhancements to AWS via the CloudFormation Open Coverage Roadmap.
Terraform CLI and Terraform AWS Cloud Control Provider Version
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Running terraform apply would update resource when template_url parameter is set
Actual Behavior
Running any updated to awscc_cloudformation_stack_set resource which has template_url parameter set cannot be updated. Running terraform apply fails with following error:
Error: AWS SDK Go Service Operation Unsuccessful
with awscc_cloudformation_stack_set.stackset,
on main.tf line 15, in resource "awscc_cloudformation_stack_set" "stackset":
15: resource "awscc_cloudformation_stack_set" "stackset" {
Calling Cloud Control API service UpdateResource operation returned: operation error CloudControl:
UpdateResource, https response error StatusCode: 400, RequestID: 6ad0d2d8-a349-463b-8257-3f3826605d99, api
error ValidationException: Model validation failed (#: #: only 1 subschema matches out of 2
#: #: 2 subschemas matched instead of one)
Steps to Reproduce
Define new awscc_cloudformation_stack_set resource using template_url parameter
terraform apply
Important Factoids
Updating Cloudformation Stackset fails also with the AWS CLI if I use same patch document that awscc provider generates in update event DEBUG:
Patch document based on DEBUG output (OrganizationUnitIds redacted)
aws cloudcontrol update-resource --type-name AWS::CloudFormation::StackSet \
--identifier teststackset \
--patch-document file://update-template-url.json
An error occurred (ValidationException) when calling the UpdateResource operation: Model validation failed (#: #: only 1 subschema matches out of 2
#: #: 2 subschemas matched instead of one)
According to AWS Support in order to update Cloudformation Stackset we also need to remove TemplateBody which seems to be generated each time stackset is updated. If I add following removal to patch document update succeeds.
{"op":"remove","path":"TemplateBody"}
AWSCC provider however does not add this operation when TemplateURL is being used. Looks like this should be added in order to fix this bug.
References
#0000
The text was updated successfully, but these errors were encountered:
Community Note
Terraform CLI and Terraform AWS Cloud Control Provider Version
Terraform v1.9.5
on darwin_arm64
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
https://gist.github.com/tabasku/5341445e3b197b5826003815f9986516
Panic Output
Expected Behavior
Running
terraform apply
would update resource when template_url parameter is setActual Behavior
Running any updated to awscc_cloudformation_stack_set resource which has template_url parameter set cannot be updated. Running
terraform apply
fails with following error:Steps to Reproduce
terraform apply
Important Factoids
Updating Cloudformation Stackset fails also with the AWS CLI if I use same patch document that awscc provider generates in update event DEBUG:
Patch document based on DEBUG output (OrganizationUnitIds redacted)
Running
According to AWS Support in order to update Cloudformation Stackset we also need to remove TemplateBody which seems to be generated each time stackset is updated. If I add following removal to patch document update succeeds.
AWSCC provider however does not add this operation when TemplateURL is being used. Looks like this should be added in order to fix this bug.
References
The text was updated successfully, but these errors were encountered: