Lack of ability to merge CLI param args with template config limits usability

[denisbr]

From the README:

does not and does not plan to support merging each commands existing parameter arguments with a template configuration file

I was thinking this tool combined with rain would make for a great replacement of the base cloudformation cli tool. We do however rely on combining configuration file parameters with CLI parameters in our CI/CD setup, so this limitation prevents us from adopting it.

I noticed your tool from your comments on the rain issue tracker, and I appreciate you have different goals. Just wanted to give a practical example of why this would have been useful :)

[mokele]

Hey Denis, nice to meet you! Yeah I can imagine that caveat from the readme may be a be terse. The reason for it was because this was written to primarily be a local development equivalent of AWS's native cloud formation support with CodePipeline which seems to be the only place the template configuration format is supported.

Once it starts adding features that diverge from aligning to CodePipelines the more it needs a new name :) so please do fork it for your own needs if wanted, it's only me with a few commits and I've hardly needed it in my current role so not needing to maintain it.

That being said CodePipelines now does support varying degrees of override variables alongside a configuration file, so something can be done I'm sure.

What use for this would you need though within your ci/cd and which ci/cd platform are you using? I'd definitely recommend a different mechanism than this cli tool and to instead use CodePipelines CloudFormation action directly. This tool was made for local dev really my

[denisbr]

Hey, thanks for quick reply!
Well, we run Cloudformation via the Jenkins plugin mostly, but I found rain which fixes a fair few annoyances with Cloudformation as compared to Terraform. (CLI UX, automating the changeset / diff stuff etc)
However we also rely on passing both parameter files and argument params in our setup, so rain fell just a bit short there.

Then noticed your comment on the rain issue tracker as mentioned, and found your tool.
I'll heed your advice though and either fork it for my own purposes, or just skip using rain for anything beside dev.

Cheers :)