[Feature Request] Test the usage of GitHub new feature for configuration variables in workflows (POC)

[ahmadabdalla]

Description

Context

From the documentation:

Previously, you needed to store this configuration data as encrypted secrets in order to reuse values in workflows.
While extremely secure, this method did not allow for easy storage and retrieval of non-sensitive configuration data such as compiler flags, usernames, server names etc.

Configuration variables allows you to store your non sensitive data as plain text variables that can be reused across your workflows in your repository or organization.
You can define variables at Organization, Repository or Environment level based on your requirement.

Link: https://github.blog/changelog/2023-01-10-github-actions-support-for-configuration-variables-in-workflows/

Requirement

• Explore usage of this new feature whether it will add value to our workflow configurations. Example: moving away from secrets for strings that are not secrets

[rahalan]

Let's discuss how to adopt it.

[eriqua]

I'd suggest leveraging the feature for the target private bicep registry (globally unique) name (currently stored in the settings.yml file)

[AlexanderSehr]

Following a discussion, we opted to use this feature. However, what will remain up to debate is what values we want to move to a variable. Suggestions are:

• NamePrefix
• ACR name (to make PRs easier)
• Service connection name (to make PRs easier)
• ...

Note: Some variables may require a different handling for GitHub vs. ADO

[AlexanderSehr]

The idea is now to implement the suggestions / test the feature and then we can get to a final decision how many values we actually want to move around.

[ahmadabdalla]

Will work on a POC for this. Self-assigning.