Securenv its a CLI for securenv API that stores and gets secure env files
npm install securenvThis is a CLI for securenv API where you can upload your env files to a vault and share you your team from a secure way.
You must be authenticated to get or set any data to secure vault.
``shell`
$ npx securenv login [username] [password] https://securenv.prod.k8s.inovacao.rdsl.adttemp.com.br
The session will be available for 1h and after the first login you can use an shortcut to login withou pass the api-host.
`shell`
$ npx securenv login [username] [password]
To GET, SET or LIST any information from the vault you have to be logged in and must have all the grants to to the job.
`shell`
$ npx securenv set [project-name] [environment]
So if you want to upload your .env.production file to the vault, you have to do:
`shell
$ npx securenv set my-project production
GET an ENV file
`shell
$ npx securenv get [project-name] [environment]
`So if you want to download your .env.production file from the vault, you have to do:
`shell
$ npx securenv get my-project productionthis will replace .env.production file with the content of the vault
``shell
$ npx securenv get my-project stagingthis will replace .env.staging file with the content of the vault
`GET an specific version
When you list list all avaiable projects and environments that you have grants, securenv will
show to you up 10 old versions of some environment.
If you want to get an specific version you have to get the versionId you want and do:
`shell
$ npx securenv get [project-name] [environment] [version-id]this will list all available environments that you have grant
`CAT an ENV file
If you only want to see some env file, you can do:
`shell
$ npx securenv cat [project-name] [environment]
`LIST environments
List all avaiable projects and environments that you have grants.
`shell
$ npx securenv list [project-name]this will list all available environments that you have grant
`SYNC securenv variables with bitbucket
This command will synchronize all variables stored in securenv with your bitbucket pipeline.
All variables will be sent to the bitbucket environment with the same name you sent as a parameter.
`shell
$ npx securenv@latest sync [environment] -p [project-name]
`If you dont send the project-name securenv will get it from you package.json
`shell
$ npx securenv@latest sync [environment]
``