You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current guidance given to users is that if any of the config values needs to reference environment variables, that they should not be added to the config, but should rather be specified at the command-line. There isn't any reason for this though. Resolve-PackageParameters can be updated to call [Environment]::ExpandEnvironmentVariables() to resolve any config value that has environment variables specified.
The text was updated successfully, but these errors were encountered:
danbelcher-MSFT
changed the title
Epand environment variables when resolving config values in PackageTool
Expand environment variables when resolving config values in PackageTool
Apr 25, 2017
Current guidance given to users is that if any of the config values needs to reference environment variables, that they should not be added to the config, but should rather be specified at the command-line. There isn't any reason for this though.
Resolve-PackageParameters
can be updated to call[Environment]::ExpandEnvironmentVariables()
to resolve any config value that has environment variables specified.The text was updated successfully, but these errors were encountered: