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

docs: remove 'BETA' references from Service Accounts

Browse Source
This commit is contained in:
Dustin Ruetz
2023-05-09 14:21:13 -04:00
parent 8fd274c5eb
commit a48d1fcd00
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -1,6 +1,6 @@
# Load Secrets from 1Password - GitHub Action # Load Secrets from 1Password - GitHub Action
This action loads secrets from 1Password into GitHub Actions using [1Password Connect](https://developer.1password.com/docs/connect) or a [Service Account <sup>[BETA]</sup>](https://developer.1password.com/docs/service-accounts). This action loads secrets from 1Password into GitHub Actions using [1Password Connect](https://developer.1password.com/docs/connect) or a [Service Account](https://developer.1password.com/docs/service-accounts).
Specify in your workflow YAML file 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 in your workflow YAML file which secrets from 1Password should be loaded into your job, and the action will make them available as environment variables for the next steps.
@@ -58,7 +58,7 @@ jobs:
``` ```
<details> <details>
<summary><b>Usage example with Service Accounts <sup>BETA</sup></b></summary> <summary><b>Usage example with Service Accounts</b></summary>
```yml ```yml
on: push on: push
@@ -131,7 +131,7 @@ jobs:
</details> </details>
<details> <details>
<summary><b>Longer usage example with Service Accounts <sup>BETA</sup></b></summary> <summary><b>Longer usage example with Service Accounts</b></summary>
```yml ```yml
on: push on: push
@@ -201,7 +201,7 @@ jobs:
``` ```
<details> <details>
<summary><b>Usage example with Service Accounts <sup>BETA</sup></b></summary> <summary><b>Usage example with Service Accounts</b></summary>
```yml ```yml
on: push on: push
@@ -295,7 +295,7 @@ jobs:
</details> </details>
<details> <details>
<summary><b>Longer usage example with Service Accounts <sup>BETA</sup></b></summary> <summary><b>Longer usage example with Service Accounts</b></summary>
```yml ```yml
on: push on: push
@@ -389,7 +389,7 @@ So if one of these values accidentally gets printed, it'll get replaced with `**
To use the action with Connect, you need to have a [1Password Connect](https://support.1password.com/secrets-automation/#step-1-set-up-a-secrets-automation-workflow) instance deployed somewhere. To use the action with Connect, you need to have a [1Password Connect](https://support.1password.com/secrets-automation/#step-1-set-up-a-secrets-automation-workflow) instance deployed somewhere.
To configure the action with your Connect host and token, set the `OP_CONNECT_HOST` and `OP_CONNECT_TOKEN` environment variables. To configure the action with your Connect host and token, set the `OP_CONNECT_HOST` and `OP_CONNECT_TOKEN` environment variables.
To configure the action with your service account token <sup>BETA</sup>, set the `OP_SERVICE_ACCOUNT_TOKEN` environment variable. To configure the action with your service account token, set the `OP_SERVICE_ACCOUNT_TOKEN` environment variable.
If you're using the `load-secrets` action more than once in a single job, you can use the `configure` action to avoid duplicate configuration: If you're using the `load-secrets` action more than once in a single job, you can use the `configure` action to avoid duplicate configuration: