✨ Question of the day ✨: Do you have any other tips or best practice to handle secrets in GitHub? GET HELP ON DEVOPS: geni.us/cdconsult SUPPORT THE CHANNEL : Buy me a coffee: www.buymeacoffee.com/CoderDave PayPal me donation: paypal.me/dabenveg
Hi, Dave. Thank you for the video! Quite helpful. However, I don't quite understand practice 2, where you talked about things generated from a secret should also be registered as a secret. I thought you have to define secret before using them? Or it is possible to register a secret dynamically during the execution of a GitHub Action?
Ideally, if a secret is known you would register it as secret in the UI so you can reuse it. However, it is possible to register something as secret at runtime. This won't make it available to other runs of the workflow, of course, but will instruct GH Actions to use the same "redaction" as the normal secrets
✨ Question of the day ✨: Do you have any other tips or best practice to handle secrets in GitHub?
GET HELP ON DEVOPS: geni.us/cdconsult
SUPPORT THE CHANNEL :
Buy me a coffee: www.buymeacoffee.com/CoderDave
PayPal me donation: paypal.me/dabenveg
Hi, Dave. Thank you for the video! Quite helpful. However, I don't quite understand practice 2, where you talked about things generated from a secret should also be registered as a secret. I thought you have to define secret before using them? Or it is possible to register a secret dynamically during the execution of a GitHub Action?
Ideally, if a secret is known you would register it as secret in the UI so you can reuse it.
However, it is possible to register something as secret at runtime. This won't make it available to other runs of the workflow, of course, but will instruct GH Actions to use the same "redaction" as the normal secrets
making good content , kudos dave :)
Hey, thanks!