[Feature Request] BREAKING change: Add options to split validation and publication resources

[MariusStorhaug]

Description

Add options to have validation and testing separate from the subscription where modules are published.
Assuming that in a ALZ landing zone a sandbox might be required for validation and testing, while published modules/template specs need to go to a separate "Automation" subscription.

If this exists, we need to add guidance for how to set up using a dual subscription setup.

We probably need to consider changing the prefix of the ARM_* variables to split the two environments:

• GH: Create separate prefixes for validation and publication:
  • VALIDATION_
  • PUBLISHING_
• ADO: Add something like this for serviceConnections:
  • serviceConnectionValidation = 'your-servicecon-name'
  • serviceConnectionPublish = $(serviceConnectionValidation)

[AlexanderSehr]

I guess it will come down to adding another service connection and referencing it in the publishing. Good idea

[eriqua]

Did we ever discuss about that? I'd even say it should be a priority. It would also be consistent with our diagram. Good catch!

[SeSeicht]

I already did that and will create a PR for that the next days

[MariusStorhaug]

Looking to include approach with the wider changes to OIDC updates, as it requires environment or other known "properties". Will try to add this as separate environments.