0a7975f916
Some checks failed
Run acceptance tests / use-connect-without-export-env (push) Has been cancelled
Run acceptance tests / use-connect-with-export-env (push) Has been cancelled
Run acceptance tests / use-connect-with-references-with-id (push) Has been cancelled
Run acceptance tests / use-service-account-without-export-env (push) Has been cancelled
Run acceptance tests / use-service-account-with-export-env (push) Has been cancelled
Run acceptance tests / use-service-account-with-references-with-id (push) Has been cancelled
Run acceptance tests / run-on-macos-12 (push) Has been cancelled
Bring 2 changes that ensure that the GitHub Action is backwards compatible: - Append `http://` if the prefix is not provided in the `OP_CONNECT_HOST` (this is caused by the fact that `curl` guesses the protocol if not provided (https://linux.die.net/man/1/curl), which we missed when switching to using the 1Password CLI as the backend of the action) - Set the default of export-env to true, since that was the default behavior of the action until we added the possibility to export secrets as step's output. Also, the documentation is adjusted to reflect these changes.
17 lines
478 B
YAML
17 lines
478 B
YAML
name: Load secrets from 1Password
|
|
description: Make secrets from 1Password Connect available as environment variables in the next steps.
|
|
author: 1Password
|
|
branding:
|
|
icon: lock
|
|
color: blue
|
|
inputs:
|
|
unset-previous:
|
|
description: Whether to unset environment variables populated by 1Password in earlier job steps
|
|
default: false
|
|
export-env:
|
|
description: Export the secrets as environment variables
|
|
default: true
|
|
runs:
|
|
using: 'node16'
|
|
main: 'dist/index.js'
|