Per provider deployment parameters, instead of per provider inputs

[erikvdbergh]

Something we are running into right now is that deployment parameters are often provider specific, but inputs are not.

At the moment, we can specify per provider inputs, but not per provider deployments parameters, whereas the other way around would be more useful.

IMO, inputs are things that change with each deployment, meaning after you have set up your cloud provider. Deployment parameters are specific to providers, but not to individual deployments. This also follows out of the fact that they are tied in with a cloud provider through a configuration.

This is especially important now that deployment parameters are validated at deployment time, which means I am including a lot of dummy variables for separate providers.

Cheers

[jadianes]

Yes, we have an item in the backlog for that reported by @dvianello

"Each cloudProvider object in the manifest should support a cloud-dependent DeploymentParameters. This would help to reduce the clutter in each Deployment Parameter since:

• we need to put all the variables (including the cloud-dependent ones) in the generic DeploymentParameters
• we need to create Deployment Parameters in the UI that contain all the DeploymentParameters defined in the manifest, as the portal now is policing this."