Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gyro Vault #79

Open
wants to merge 30 commits into
base: master
Choose a base branch
from
Open

Gyro Vault #79

wants to merge 30 commits into from

Conversation

beetlebugorg
Copy link
Contributor

@beetlebugorg beetlebugorg commented Jul 18, 2019

Fixes #176

Implements Gyro Vault functionality. This includes a Vault plugin interface, a vault command to manipulate a vault, and a reference resolver for using vault secrets in Gyro configs.

Gyro Vault is intended to interface with existing secrets managers such as AWS Secrets Manager. It includes a basic file system based vault.

Gyro vault command syntax:

gyro vault put key value
gyro vault get key
gyro vault list [prefix]

Gyro vault resolver syntax:

$(vault-lookup secret [vault])

Jeremy Collins added 4 commits July 18, 2019 14:00
This is so we can use RootScope to load any Gyro file. This will be used by the new Vault system to load/store secrets using the Gyro language format.
Implements:

- Vault abstract class that custom vault implementations can subclass
- LocalVault implementation that stores encrypted secrets in .gyro directory
- VaultCommand for getting/setting and listing secrets
- VaultReferenceResolver to provide a method to lookup secrets within Gyro configs
- VaultDirectiveProcessor for configuring vault implementations in .gyro/init.gyro
@beetlebugorg beetlebugorg changed the title Feature/vault GYRO-275: Gyro Vault Jul 18, 2019
@beetlebugorg beetlebugorg changed the title GYRO-275: Gyro Vault Fixes #176: Gyro Vault Oct 9, 2019
@beetlebugorg beetlebugorg changed the title Fixes #176: Gyro Vault Gyro Vault Jan 29, 2020
Jeremy Collins added 3 commits February 3, 2020 13:26
This fixes an issue where all files were being evaluated when loading the local vault. This would fail because the vault itself is not defined in this use case.
This is just a temporary fix. Need to investigate why this fails when only a single instance of a vault is defined.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

GyroInstance methods may conflict with Cloud Specific Resources
2 participants