Login issue with OIDC #84
Description
We want to use OIDC auth method for Azure Login, and when we call the template, for example, register-environment.yml, we are expected to pass creds secret whereas the azure login step uses clientid, tenantid, subid. Since creds secret is the only one defined in the template and marked as mandatory, we are not able to pass the other secrets explicitly.
If we use the syntax, secrets: inherit in the caller workflow, it does not take creds secret into account (secrets defined in GH Repo turn into upper case, so if we define creds, client_id, tenant_id, subscription_id in GH Repo secrets, we get an error that creds was not passed). Could you please advise what should the caller workflow look like when we need to use OIDC auth method, or could you please remove the required flag on creds in the templates.
Thanks for your time.