From the course: GitHub Actions Cert Prep by Microsoft Press

Unlock this course with a free trial

Join today to access over 25,500 courses taught by industry experts.

Use encrypted secrets to store sensitive information

Use encrypted secrets to store sensitive information - GitHub Tutorial

From the course: GitHub Actions Cert Prep by Microsoft Press

Start my 1-month free trial Buy for my team

Use encrypted secrets to store sensitive information

“

- [Presenter] The bottom line is you're not going to be working with GitHub actions too long before you come across the requirement to supply secret data, whether that's an API key or a password, something of the sort, access tokens, APS. So it's absolutely a crucial task that we're never going to place any sensitive data in plain text because data breaches are going to be a bad day for everybody, no matter what size company you work for. As you would expect, and you'll certainly need to know for your certification exam that GitHub actions does have built in capability to handle secure data. First of all, we have encrypted secrets. As you'll see in our upcoming demo, you can, at the repository level, create secrets that are stored encrypted by GitHub, and you can call them using the secrets context in your workflow files. The secrets are going to be accessible by workflows in the same repository, and the setup can be done, if you're not going to use the GitHub CLI or command line…

Contents