TemplateURL with Nested Stacks is not updated
See original GitHub issueI’m getting the following error TemplateURL must be an Amazon S3 URL.
whenever I’m using a nested stack.
My root stack looks like this
AWSTemplateFormatVersion: '2010-09-09'
Description: 'Root stack template'
Resources:
ObjectStorageStack:
Type: AWS::CloudFormation::Stack
Properties:
TemplateURL: 'object_storage_template.yml'
And nested stack is in file object_storage_template.yml
Resources:
ObjectBucket:
Type: AWS::S3::Bucket
I would expect that this deploy action performs packaging and therefore the TemplateURL
gets updated.
Is this behavior supported by this action?
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
AWS cloudformation nested stacks failed by template URL
TemplateURL should be written as the URL in S3, therefore https://... . In this doc, written as:
Read more >AWS::CloudFormation::Stack
An update never causes a nested stack to be replaced. ... Resources: myStackWithParams: Type: AWS::CloudFormation::Stack Properties: TemplateURL: ...
Read more >Nested stacks - AWS CloudFormation Workshop
The TemplateURL property is used to reference the CloudFormation template that you wish to nest. The Parameters property allows you to pass parameters...
Read more >Nesting an existing stack - Amazon CloudFormation
It's not necessary to run drift detection on the parent stack after this import operation because the AWS::CloudFormation::Stack resource was already managed by ......
Read more >Passing values and parameters to nested stacks - N47
In the nested stack, we define the Stage parameter, just like we did in the parent. If we do not define it here...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
closing this in favour of #33
Correct. I realized that. So far my solution works in a way that I have to run
aws cloudformation package
command. Would be nice to have it as part of this action.If this is not planned, feel free to close this issue.