We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Considering a blueprint "sample\env" with a "Select" parameter to generate an environment YAML file:
spec: - name: Environment type: Select options: - DEV - QA files: - path: environment.yaml.tmpl renameTo: dev-environment.yaml writeIf: !expr "Environment == 'DEV'" - path: environment.yaml.tmpl renameTo: qa-environment.yaml writeIf: !expr "Environment == 'QA'"
If I include this blueprint more than once in an other blueprint, the overidden parameter "Environment" is evaluated using last affectation only:
includeAfter: # Generate the DEV environment YAML file - blueprint: sample\env parameterOverrides: - name: Environment value: DEV # Generate the QA environment YAML file - blueprint: sample\env parameterOverrides: - name: Environment value: QA
Resulting in this generated file (dev env is missing):
[file] Blueprint output file 'qa-environment.yaml' generated successfully [file] Blueprint output file 'qa-environment.yaml' generated successfully
Is it an issue or a feature ?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Considering a blueprint "sample\env" with a "Select" parameter to generate an environment YAML file:
If I include this blueprint more than once in an other blueprint, the overidden parameter "Environment" is evaluated using last affectation only:
Resulting in this generated file (dev env is missing):
Is it an issue or a feature ?
The text was updated successfully, but these errors were encountered: