Difference between revisions of "How to set Environment Variables value"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
== In pipeline == | == In pipeline == | ||
| + | === Microsoft Resources === | ||
* [https://docs.microsoft.com/en-us/power-platform/alm/conn-ref-env-variables-build-tools Pre-populate connection references and environment variables for automated deployments] | * [https://docs.microsoft.com/en-us/power-platform/alm/conn-ref-env-variables-build-tools Pre-populate connection references and environment variables for automated deployments] | ||
| + | |||
| + | === Community Resources === | ||
| + | * [[https://benediktbergmann.eu/2021/12/02/set-connection-references-and-environment-variables-in-pipelines/ Set Connection References and Environment Variables in Pipelines] by Benedikt Bergmann 2021-12-02 | ||
| + | |||
| + | == Also see == | ||
| + | * [[ALM]] | ||
| + | * [[Pipelines]] | ||
Revision as of 08:17, 17 December 2021
Manually
Manual deployment of a solution requires environment variables to be set in the target environment after deployment. To be able to do that you need to either add a value to the environment variable from within the default solution or you need to create an own unmanaged solution in the target environment, add the environment variable and set the value. It is best practice NOT to make changes manually in the target environment. This will most likely change in the future.
Setting environment variable as part of pipelines is general available as of 15th of December 2021.
In pipeline
Microsoft Resources
Community Resources
- [Set Connection References and Environment Variables in Pipelines by Benedikt Bergmann 2021-12-02