I'm trying to create a CI/CD pipeline for a Power Platform Solution in Azure DevOps. The pipeline is relatively simple with only a single stage which consists of three tasks:
- Power Platform Tool Installer
- Power Platform Export Solution
- Power Platform Import Solution
I also added an Azure Repo as a Build Artifact. Excluding the readme file from the initial commit, the only thing the repo stores is a Deployment Settings File which is used in the Import Solution task of my pipeline.
The solution itself only contains a single Power Automate flow with a Office 365 - Send an Email (V2) action and an SharePoint - Get items action. The solution also contains two connection references for both of these actions.
The first time I deployed the pipeline which exported my solution from my first environment and imported it in my second environment, it was missing connection references for both actions in the flow. After this I manually created connection references for both actions and saved the "LogicalName", "ConnectionId", and "ConnectorId" values in my Deployment Settings file on the Azure Repo so the connection references can be automatically populated on each subsequent deployment.
My issue is that after the initial deployment and after updating my deploymentSettings.json file, after every deployment displays a missing connection reference error for both actions in my flow even though the newly created connection references are still in my solution on my second environment.
How can I resolve this so that I don't have to manually set each connection reference on each deployment?
