search

microsoft / coe-starter-kit

Other
751 stars 221 forks source link

[CoE Starter Kit - QUESTION] QUESTION Creating a Backup CoE Starter Kit #9218

Open syou0224ondr176mocoksrg opened 1 day ago

syou0224ondr176mocoksrg commented 1 day ago

Does this question already exist in our backlog?

What is your question?

I am considering preparing a backup in case the upgrade of the CoE Starter Kit fails. This is to ensure that we can use the backup CoE Starter Kit if the upgrade does not succeed.

Here are the steps to create the backup:

  1. Create a sandbox environment.
  2. Copy the environment that contains the currently used CoE Starter Kit and paste it into the sandbox environment.
  3. Convert the sandbox environment into a production environment.
  4. Use the “CoE Setup and Upgrade Wizard” to set up the CoE Starter Kit in the converted production environment.

While setting up the CoE Starter Kit in the production environment, I encountered a situation where clicking “Refresh” at the “Run Setup flows” step did not trigger the flow. If this flow does not work as per the Wizard’s instructions, is it impossible to complete the setup?

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.22

What app or flow are you having the issue with?

CoE Setup and Upgrade Wizard

What method are you using to get inventory and telemetry?

None

syou0224ondr176mocoksrg commented 1 day ago

I wasn't able to attach the image, so I'm resending it. The flows that were not triggered during the setup flow execution are shown in the image.

Image

Jenefer-Monroe commented 19 hours ago

Unfortunately there was a recent change in the way environment variables are stored by the product team and so the kit had to be updated to conform to the new requirements. Setting env vars today using the kit's apps in older versions does not work as a result. After upgrade this will work again.

Turning flows on should work though once the env vars are filled, you will need to fill them via the product ux instead.

Here are the Env Vars in Core: All Env Vars You can copy most of them from your other environment, I've put a note for the few that you would want to or need to be different.

ProductionEnvironment

You'll want this one to be "No" in your backup environment

CoE System User ID

You can find this SYSTEM user in the Maker table, grab its GUID and putting it into the env var manually: image