[Request]: Maintain multiple cloudformation templates for one pipeline infrastructure

[jiwenxin90]

Community Note

• 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 "me too" comments, 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

Tell us about your request For one pipeline infrastructure, can I maintain multiple cloudformation templates that would need to cross-reference each other? Is the manifest.yaml designed to support this? If so, how can I refer to resources defined in another cloudformation template? (I know CloudFormation allow us to refer to resources defined in another stack, but that would require to know the stack name ahead of time. Is there a way to specify the stack name in manifest.yaml?) Thanks!

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? I have a very long CloudFormation template for my pipeline infrastructure. And I would like to separate them into multiple pieces. I would need to cross-reference between these templates.

Are you currently working around this issue? I can only use one super long cloudformation template at this moment.

[rafavallina]

Hi @jiwenxin90 Yes! We want to support this, but we haven't fully defined this work yet. Is this blocking you from using Proton for your workloads? I'd love to discuss further and understand the details