We utilize a very specific git branching strategy within our application development and engineering org that allows development engineers to code to the equivalent of a 'develop' branch to validate "pre-Pull Request" changes to IaC. We need to contain the risk of drift in that related iacm workspace over time by including the 'dev' workspace content be still deployed using 'main' in the standard SDLC. Since the IACM stage itself has the branch configuration, we want to be able to temporarily override that value in the occasion that we need to utilize the 'develop' branch. This is not a long-lived branch but rather a "sandbox" rendering of the IaC codebase, similar to AWS's trunk-based guidelines: https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/implement-a-trunk-branching-strategy-for-multi-account-devops-environments.html