Closed jrossstocholm closed 7 months ago
@jrossstocholm Can you try setting the OverwriteUnmanagedCustomizations parameter to true on your solution import task. I'm guessing you have an unmanaged layer on your Environment Variable component
@jrossstocholm Can you try setting the OverwriteUnmanagedCustomizations parameter to true on your solution import task. I'm guessing you have an unmanaged layer on your Environment Variable component
I do not have any unmanaged layers on my environment variables. However - I have have been able to fix the issue by clearing the environment variable before exporting the solution. This enables me to supply the correct value for my staging environment. I know that this is not a permanent fix - but it works for now 😊.
I will close this ticket now and revert to it when I have time to look into the real issue again.
Thank you.
We have a model-driven Power App that we move from DEV/TEST to STAGING to PROD using Azure pipelines.
The solution is exported as "managed" and this managed solution is then deployed to STAGING subsequently to PROD.
We have a single environment variable that needs to be updated when importing to STAGING/PROD. We have created a deployment settings file with this content:
We have configured the "Solution Import" task like this:
The Import task is finished successfully and we can see in the logs that the deployment settings file is loaded
'Calling pac cli inputs: solution import --path D:\\a\\1\\s\\app_managed.zip --async false --force-overwrite false --publish-changes false --skip-dependency-check false --convert-to-managed false --max-async-wait-time 60 --activate-plugins true --skip-lower-version false --settings-file D:\\A\\1\\app_managed\\s\\pipelines\\deployment-settings_staging.json --log-to-console'
But nothing happens - the environment variable is not updated with the new value.
I am kind of at a loss here - I cannot figure out why it is not updated as per the configuration.
What am I doing wrong here?
Thanks 😊