In our organization, we aim to centralize the AZURE_CREDENTIALS secret rather than distributing it across numerous repositories.
To align with this goal, our internal administrator has created an organizational secret.
However, due to our internal naming conventions, this secret is named BC_SIGNING_AZURE_CREDENTIALS.
Upon reviewing the AL-Go documentation, it appears there isn't a current method to reference this uniquely named secret within the AL-Go configuration and settings.
Would it be possible to introduce a feature that allows for a custom secret name, similar to the existing licenseFileUrlSecretName setting?
An example could be a setting named azureCredentialsSecretName, which would provide the flexibility needed to accommodate different naming conventions.
In our organization, we aim to centralize the
AZURE_CREDENTIALSsecret rather than distributing it across numerous repositories. To align with this goal, our internal administrator has created an organizational secret. However, due to our internal naming conventions, this secret is namedBC_SIGNING_AZURE_CREDENTIALS.Upon reviewing the AL-Go documentation, it appears there isn't a current method to reference this uniquely named secret within the AL-Go configuration and settings. Would it be possible to introduce a feature that allows for a custom secret name, similar to the existing
licenseFileUrlSecretNamesetting? An example could be a setting namedazureCredentialsSecretName, which would provide the flexibility needed to accommodate different naming conventions.