Difference between revisions of "How to set Environment Variables value"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | |||
| − | |||
== Manually == | == 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. | 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. | ||
Revision as of 08:11, 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.