search

CloudSlang / cs-actions

CloudSlang Content Java Actions
Apache License 2.0
41 stars 55 forks source link

Enhancement request to support CloudFormation Template Deployments through an S3 URL #927

Open sandeep-kotagiri opened 2 years ago

sandeep-kotagiri commented 2 years ago

We have worked with the OO CloudFormation content pack for close to three months now. One of the biggest problems in using the content pack - it is not letting us developing our content much faster. It is slowing everyone on the team leading to so much of wasted time. It is not leading to agility on the team.

And the primary reason for slowness is as follows: We have been improving our CloudFormation templates almost every day. At the moment, CloudFormation operations accept CloudFormation content as a string. So every time we make a change into CloudFormation template, we will need to make changes to OO flows to embed the CloudFormation json string into the OO flow. Then we will need to create a content pack, promote it across environments and then do end to end testing. With the current way of development, engineers are stepping over one another and that is also leading to additional wasted time in triaging issues that shouldn’t have happened to start with.

To solve this problem, I would like to request the following changes to CloudFormation content pack: Allow users to specify CloudFormation template as an S3 object. This is natively supported by AWS. And all AWS clients allow to specify CloudFormation template to be used as an S3 object. If we get support for this, we do not have to touch OO flows that are stable on a day to day basis. Any changes to AWS content will go into CloudFormation templates. These templates can get updated on S3 directly keeping the designer and OO content consistent. Version updates for e.g. for RDS, Vertica etc. can also be easily accomplished through this methodology. And this will lead to greater agility on the team.

We will still need to touch OO flows when the CloudFormation parameters change. But most of the time, these parameters do not change at all. Given the support from AWS Java client, I am hoping that this is very small change to make.

lrevnic commented 2 years ago

Fair request. Started to look into it.