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

Merge pull request #42 from 1Password/ruetz-service-accounts-exiting-beta

Browse Source 
Remove 'BETA' references from Service Accounts
This commit is contained in:
volodymyrZotov
2023-05-16 20:09:59 +03:00
committed by GitHub
parent 8fd274c5eb 15d95ae871
commit d8ac5d7286
2 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
.github/workflows/test.yml vendored
View File

@@ -5,8 +5,8 @@ jobs:
test-with-output-secrets:
strategy:
matrix:
os: [ ubuntu-latest, macos-latest ]
auth: [ connect, service-account ]
os: [ubuntu-latest, macos-latest]
auth: [connect, service-account]
exclude:
- os: macos-latest
auth: connect
@@ -49,8 +49,8 @@ jobs:
test-with-export-env:
strategy:
matrix:
os: [ ubuntu-latest, macos-latest ]
auth: [ connect, service-account ]
os: [ubuntu-latest, macos-latest]
auth: [connect, service-account]
exclude:
- os: macos-latest
auth: connect
@@ -93,8 +93,8 @@ jobs:
test-references-with-ids:
strategy:
matrix:
os: [ ubuntu-latest, macos-latest ]
auth: [ connect, service-account ]
os: [ubuntu-latest, macos-latest]
auth: [connect, service-account]
exclude:
- os: macos-latest
auth: connect

12
README.md
View File

@@ -1,6 +1,6 @@
# 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.
@@ -58,7 +58,7 @@ jobs:
```
<details>
<summary><b>Usage example with Service Accounts <sup>BETA</sup></b></summary>
<summary><b>Usage example with Service Accounts</b></summary>
```yml
on: push
@@ -131,7 +131,7 @@ jobs:
</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
on: push
@@ -201,7 +201,7 @@ jobs:
```
<details>
<summary><b>Usage example with Service Accounts <sup>BETA</sup></b></summary>
<summary><b>Usage example with Service Accounts</b></summary>
```yml
on: push
@@ -295,7 +295,7 @@ jobs:
</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
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 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: