Closed stephenmahood closed 2 years ago
Hey @stephenmahood , In general, all secrets are sanitised by Github Actions when printing on the console. But you should still be able to use the output in a dependent step/job. Could you please clarify your question/requirement? Sharing a use case or an example will help as well.
@stephenmahood 👋🏽 Gentle reminder.
Hey @stephenmahood , Please re-open the issue if you want further help.
Closing this for now. Reopen if you are need further assistance.
When using the Azure Login GitHub action with the creds parameter:
secrets.AZURE_CREDENTIALS:
and then deploying an ARM template with the arm-deploy action that returns a resourceId as a template output, GitHub sanitizes the step output due to the subscriptionId within the resourceId being present within the AZURE_CREDENTIALS secret.