In this video, see how Actions can be configured to use secrets like passwords and API keys without exposing them.
- [Man] We've seen how we can add environment variables … to actions in a workflow, … but sometimes we need to store sensitive information, … like passwords or API keys. … To do that, we need to use a secret. … Secrets are stored just like environment variables. … Except they are encrypted as soon as they are entered. … After a secret is stored it can't be viewed or edited. … To change a secret you would have to … delete it and recreate it. … There are some limits to using secrets in a workflow. … Workflows are limited to 100 secrets, … and secrets are limited to 64 kilobytes in size. … If you need to store secrets … that are larger than 64 kilobytes, … you can encrypt them and store them in the repository, … and then store the decryption key … as a secret in the workflow. … Let's take a look at adding secrets to a workflow. … I'm editing a workflow with an action using … the GitHub Action for AWS. … I've already added some environment variables … that I don't mind being exposed. … The AWS default region and default output. …
- Creating an action
- Creating a workflow
- Adding actions to a workflow
- Using an action from a repository
- Using environment variables
- Building custom actions
- Use cases for actions and workflows
Skill Level Beginner
1. Your first Action
2. Connecting Actions with Workflows
3. Using Actions
4. Building Custom Actions
5. Use Cases
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.