CloudFormation support upgrade & syntax deprecation Notice

[shirabendor-quali]

What Is Changing?
CloudFormation grain is getting a major upgrade and will be now executed through Torque agent – more scalable, much more secure.
CloudFormation grain syntax deprecation and additions

Why did we make this change?
As part of our effort to improve scalability and data security, we have upgraded the CloudFormation grain so that it can run in Torque agents instead of directly from Torque itself. With this change, customers can ensure data never leaves their site, CloudFormation execution permissions can be managed using Kubernetes service accounts, and CloudFormation execution is much more scalable.

What Does This Mean for You?
If you’re already using CloudFormation grain in your blueprint, follow our documentation to modify them to get ready for the change. We've prepared detailed documentation to help you through this change. Autogeneration of blueprints with cloudformation templates already adheres to the new syntax.

When Will This Change Take Effect?
The deprecated fields will continue to be supported until Nov 30, 2023.

We're Here to Help – for any questions or concerns please contact us