Commit Graph

7 Commits

Author SHA1 Message Date
Eduard Filip
0a7975f916 Ensure that the action is backwards-compatible (#25)
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.
2022-12-22 12:46:28 +02:00
volodymyrZotov
2f338e16af use node16 2022-08-15 14:33:11 +03:00
Eddy Filip
4baca64066 Enable using loaded secrets from step's output 2021-09-01 18:23:35 +02:00
Eddy Filip
ac12d2e3c4 Switch to node action
This is done to be able to pass loaded secrets as output. This is not available with a composite action, unless we hard-code the action's outputs, which is not a desired outcome.
2021-09-01 18:20:57 +02:00
Floris van der Grinten
bafb7c3e16 Fill out action metadata fields 2021-05-20 20:57:20 +02:00
Floris van der Grinten
6ee4db8bcd Rename to load-secrets-action 2021-05-20 20:49:22 +02:00
Floris van der Grinten
e25891308d Create env-export action 2021-05-20 11:27:09 +02:00