wesley/load-secrets-action
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Move note on masking into separate section

Browse Source
This commit is contained in:
Floris van der Grinten
2021-05-27 14:45:33 +02:00
committed by GitHub
parent 08f33d084a
commit 8df8b2ac7d
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -4,9 +4,6 @@ The action to load secrets from [1Password Connect](https://1password.com/secret
Specify right from your workflow YAML which secrets from 1Password should be loaded into your job, and the action will make them available as environment variables for the next steps. Specify right from your workflow YAML which secrets from 1Password should be loaded into your job, and the action will make them available as environment variables for the next steps.
Just like regular GitHub repository secrets, every secret from 1Password will automatically be masked from the GitHub Actions logs too.
So if they accidentally get printed, they'll get replaced with `***`.
## Usage ## Usage
```yml ```yml
@@ -108,6 +105,13 @@ So for example, the reference URI `op://app-cicd/aws/secret-access-key` would be
* **Section:** default section * **Section:** default section
* **Field:** `secret-access-key` * **Field:** `secret-access-key`
## Masking
Just like regular GitHub repository secrets, secrets loaded from 1Password will automatically be masked from the GitHub Actions logs too.
If they accidentally get printed, they'll get replaced with `***`.
To avoid unnecessary masks (like a username field), masks are only applied on fields marked as concealed (which show as `•••••` in the 1Password GUI) and on secure notes.
## Supported Runners ## Supported Runners
You can run the action on Linux and macOS runners. Windows is currently not supported. You can run the action on Linux and macOS runners. Windows is currently not supported.