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
The pac solution import supports passing the settings file to setup environment variables and connections (--settings-file).
Some tenants are configured to run with the Power Platform pipelines, and all deploys should be done using these pipelines, so we cannot use the pac solution import approach.
It seems that the pipeline deploy UI (and the pipelines framework) support the use of deploymentsettings. When entering the configuration in the UI upon deploy, the settings seem to be persisted in a deploymentsettings field of the pipeline run. Passing the deploymentsettings is not yet available in the CLI.
Can we expect this addition? Is there a workaround, while still using pac pipeline deploy?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The pac solution import supports passing the settings file to setup environment variables and connections (--settings-file).
Some tenants are configured to run with the Power Platform pipelines, and all deploys should be done using these pipelines, so we cannot use the pac solution import approach.
It seems that the pipeline deploy UI (and the pipelines framework) support the use of deploymentsettings. When entering the configuration in the UI upon deploy, the settings seem to be persisted in a deploymentsettings field of the pipeline run. Passing the deploymentsettings is not yet available in the CLI.
Can we expect this addition? Is there a workaround, while still using pac pipeline deploy?
Beta Was this translation helpful? Give feedback.
All reactions