RFE to deploy CFT v2 without external file hosting requirement

[depperson]

Is your feature request related to a problem?

As an end user, I expect the "launch stack" button to accept all required configuration as parameters.

The requirement to publicly host a modified runtime-init configuration adds a lot of overhead to the deployment process and reduces the convenience of the "launch stack" buttons.

Describe the solution you'd like

Deploying this v2 CFT should be (at least) as easy as deploying v1. I would like to pass all necessary configuration as parameters during CFT deployment, like the method used for v1 CFTs. I would like to eliminate the requirement of an external HTTP host.

Describe alternatives you've considered

I understand that it is possible to convert the runtime-init configuration from yaml to json, escape the quotes and pass that blob as a parameter. This method is error prone and painful to execute. The bare minimum configuration to deploy should be possible using parameters without editing the template or runtime-init files.

Additional context

Requiring users to edit files defeats the purpose of the "launch stack" buttons. If you cannot launch the stack without modifying it, then the "launch stack" button shouldn't be visible as an option since it won't work.

[shyawnkarim]

Thanks for this suggestion. We'll review this request with the team. It is now being tracked internally with ID ESECLDTPLT-3204.