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

Collect the env variables when you are ready to migrate to Vaultik #6

Open
tomiok opened this issue Dec 31, 2021 · 0 comments
Open

Comments

@tomiok
Copy link
Owner

tomiok commented Dec 31, 2021

Is your feature request related to a problem? Please describe.
You are not using Vaultik. You found it in Github. You are using env variables.
Now you want to migrate and start using Vaultik, that's good! so you can share all the env variables that you want to
migrate in 2 formats, passing a file in csv or via CLI, passing all the values.

The result should be with all the envvars now saved as a REAL secret.

Describe the solution you'd like

  • Introduce a new command with a flag to see if we are using a file or the values
  • parse de file | parse de values
  • Find all the env variables, ignore if something is empty
  • save as secrets
  • print a message with how many secrets are created

Describe alternatives you've considered
NONE (edit if necessary)

Additional context
NONE (edit if necessary)

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

No branches or pull requests

1 participant