Production and Development Environments in PowerShell Universal using Git

In this video, I walk through the steps to setup a production and development environment for PowerShell Universal using git for configuration file storage. We'll setup a GitHub repository and configure 2 instances of PowerShell Universal. One instance uses the main, or production, branch and one uses the dev branch. From there we'll make some changes in dev and promote them to prod through pull requests.

[@kristofstroobants3429]

Say I write a script that targets Exchange O365, I'll have a tenant for LAB and one for PROD.
The code of the script would then be identical across environments but the underlying configuration (the credential vaults for instance) would be unique to their environment.
I assume, as long as you build up those vaults the same way (variable names), your code should function correctly?
To add to your example of the Title. What if i would chose different colors per environment?
Since I would start out at the LAB env, it would automatically find itself into PROD.
So how do you go about that? Write if statements per domain in each of the settings files?
But what about schedules? The schedules in LAB will differ from PROD.
I guess what I'm asking is, how to go about these things best?

[@WindosNZ]

Apologies if I missed it in the video. Are there licensing implications of running multiple instances of PSU like this?

[@AdamDriscoll]

Yes. You will need a license for each instance of PSU.