Again similar to AWS:Include, I agree it may be handy for Sceptre to make sure nested templates are uploaded to S3 before.
What's actually this issue here? I'm not super familiar with nested stacks.
Just re-iterate the nested stacks are CloudFormation templates which have CloudFormation Stack resources. Those resources reference another CloudFormation within S3. So I guess to would be good to have Sceptre upload all the dependent templates to S3.
How hard would it be to add this functionality to Sceptre? We use nested stacks quite a bit in our environments, and it would be a valuable feature to have.
This is currently handled by aws cloudformation deploy, so it's implemented by https://github.com/cloudreach/sceptre/issues/324
I have a hook code to implement that, just going through internal review to decide if it should be in the sceptre repo or as a separate plugin. The issue with it, is that it depends on the awscli (the only place SAM is implemented, by AWS)
@JuanCanham would you be able to share your hook code for cloudformation deploy?
This is currently handled by
aws cloudformation deploy, so it's implemented by #324I have a hook code to implement that, just going through internal review to decide if it should be in the sceptre repo or as a separate plugin. The issue with it, is that it depends on the awscli (the only place SAM is implemented, by AWS)
Would you be able to share this? I could use this today even if it's not in a final form.
what is the current status of this?