-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
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
Support Environment Variables in Parameter.yml #160
Comments
If there is a session environment variable of ENV:SQLServerConnection, then replace that reference in the yml file when processing. If we did take this on, it would need to be behind a feature flag so that default behavior is off. It would be fairly straight forward to implement, list all environment variables. If there's any matches in the yml file, blindly replace.
|
The question is more so where this sits in the larger priorities. |
Would it be in the _refresh_parameter_file function? if so I could take a look at contributing the change. |
@richbenmintz yep that's correct! We have an ongoing refactor for parameterization so you would want to take a dependency on the output of Shira's work here. That we're targeting to ship this week. In terms of implementation, you would need to integrate a new feature flag, and then update the find_replace. Example of how to use feature_flag fabric-cicd/src/fabric_cicd/publish.py Lines 102 to 110 in 7d72130
|
Submitted a PR for this enhancement |
What is the feature?
Please allow Azure DevOps Pipeline and Release Variables to be used in the find_replace feature as key value pair:
replace with the value of the key defined in the yaml.
sorta like (sorry yaml not formatted 100%):
find_replace:
# SQL Connection Guid
"db52be81-c2b2-4261-84fa-840c67f4bbd0":
PPE: var_1
PROD: var_2
Additional context
No response
The text was updated successfully, but these errors were encountered: