Azure Blob Storage account key exposed in source control

Description: after configuring a Power Apps portal site (probably the same for Power Pages too) according to the instructions for how to Enable Azure storage, and then configuring Power Pages ALM per the Tutorial on how to use Power Platform CLI with Power Pages, we discovered that our Azure Blob Storage account connection string, which contains the account key, had been inadvertently checked into source control within the file `sitesetting.yml`.

What I've tried: I've added the `sitesetting.yml` to our `.gitignore`, but now this file won't get uploaded with the rest of the portal contents.

Where I'm stuck: It seems to me that I need to somehow download *just* the `sitesetting.yml` file from the source environment during the deployment pipeline run, but I'm not sure how I can do that. Alternatively, I've seen mention of using a `deployment-profiles` folder, containing a `[env].deployment.yml` file for environment-specific settings, but I'm not sure how I can utilize that during the pipeline run.

Categories:

Tips & Tricks

General

Quick Links

Leaderboard > Power Pages