mikefactorial
commented
1 year ago @LukasSchauffele would you mind reposting this on https://github.com/microsoft/powerplatform-build-tools? In the meantime it should be easy enough to delete environment variable values in the downstream environment using the deploy-solution-import-pre-hook.yml hook. Some pseudo code below. NOTE: This hasn't been tested or validated writing from memory.
$config = Get-Content '$(DeploymentSettingsPath)' | ConvertFrom-Json
. "$env:POWERSHELLPATH/load-save-pipeline-parameters.ps1"
$parameters = Read-Pipeline-Parameters "$(Agent.BuildDirectory)\deploy-pipeline-parameters.json"
. "$env:POWERSHELLPATH/dataverse-webapi-functions.ps1"
$dataverseHost = Get-HostFromUrl "$parameters.serviceConnectionUrl"
foreach ($var in $config.EnvironmentVariables) {
$odataQuery = 'environmentvariablevalues?$filter=schemaname eq ''' + $var.LogicalName + '''&$select=environmentvariablevalueid'
$response = Invoke-DataverseHttpGet $(SpnToken) $dataverseHost $odataQuery
foreach ($varValue in $response ) {
#Call delete against the API for each $varValue.environmentvariablevalueid
#https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/update-delete-entities-using-web-api#basic-delete
}
}
RajeevPentyala
CoEStarterKitBot
LukasSchauffele
Is your feature request related to a problem? Please describe.
I will add my question/request for the ALM accelerator to start with even though the underlying issue is a bug with the platform.
Is it possible to remove the environment variable values in a downstream environment before importing a solution into an environment? Maybe using hooks?
The reason I want to do this is because I am sometimes getting an error on import when the environment variable in the deploymentSettings.json and the environment variable value in the downstream environment do not match.
I've actually already posted about this error before - #3101 - and raised a ticket with support (2207120030000937 and 2211160030000704) but haven't gotten anywhere. The response from support was to delete the value of the environment variable manually before importing a solution.
This screenshot shows the current value of the environment variable in the downstream environment I am importing in, the value is
8e197461-21d1-429b-9c53-e7792b2ce555:The value for this environment variable in my deploymentSettings-demo.json matches. The solution successfully imports.
Once I change the value in deploymentSettings-demo.json to something other than what's currently in the environment the import fails (I've added the full error message below).
If I remove the environment variable value manually and then re-run the import pipeline, everything works.
Describe the solution you'd like
Ideally, pac should be able to import into an environment with environment variables specified in the --settings-file without issues. Can you please pass this on to the pac team?
In the mean time, could someone please assist me in writing a hook to clear the environment variable values in the downstream environment? The current process is:
Describe alternatives you've considered
Continue to manually delete environment variables.
Additional context?
Error message: