As a central infrastructure admin I would like to be able to configure default values for various inputs that are on the member DA level. Creating an environment entry in a project seems to be a natural choice for that - I can set the variables matching the DA input names with the default values to even override some of the stack pre-defined wiring. That would make it easier for the teams deploying the stacks while reusing the existing resources.
It seems that the stack level inputs can be set from the environment parameters without an issue. But if the input is at the member DA level and is already pre-set in the stack definition, the environment settings are not applicable. This may be a project framework issue in general.
Examples of predefined values I would like to use:
Account Infrastructure Base: MFA level - somehow that works from the environment parameter, probably because the stack does not set it, but there is a default in the member DA
Watson SaaS DA: plan values like watson_discovery_plan (e.g. set to Do not install)
ALM DA: sm_secret_group - to use pre-configured secrets in a specific group
ALM DA: repo_group - to use specific pre-configured org in GitLab
Sample App config DA: watson_assistant_instance_id - to re-use central Assistant instance
Sample App config DA: create_secrets - set to false to enable using pre-defined secrets for credentials
It may not make sense to expose all those parameters as separate input at the stack level - there could be others as well, especially in the ALM DA. Unless it would be something like override.json that will be passed to all member DAs and they can use it to override some of their individual inputs.
New or affected modules
By submitting this issue, you agree to follow our Code of Conduct
Description
As a central infrastructure admin I would like to be able to configure default values for various inputs that are on the member DA level. Creating an environment entry in a project seems to be a natural choice for that - I can set the variables matching the DA input names with the default values to even override some of the stack pre-defined wiring. That would make it easier for the teams deploying the stacks while reusing the existing resources.
It seems that the stack level inputs can be set from the environment parameters without an issue. But if the input is at the member DA level and is already pre-set in the stack definition, the environment settings are not applicable. This may be a project framework issue in general.
Examples of predefined values I would like to use:
watson_discovery_plan(e.g. set to Do not install)It may not make sense to expose all those parameters as separate input at the stack level - there could be others as well, especially in the ALM DA. Unless it would be something like override.json that will be passed to all member DAs and they can use it to override some of their individual inputs.
New or affected modules
By submitting this issue, you agree to follow our Code of Conduct