The gpgenv from heroku

This project is the old Ruby CLI for Heroku. This is the current CLI.

gpgenv's People

Contributors

Stargazers

Watchers

gpgenv's Issues

better usability

Look at how sack implements profiles, as well as its installation process. gpgenv should have something similar:

Maybe: ability to "switch" profiles, rather than entering a profile to use on each command?
Definitely: ability to automatically set up config files linked from ~/*.rc files, to define commands in the shell (instead of only using executables).

Request more doc related to `pass`

I'm confused about the solution this gem brings that could be solved in a simpler way.

I particularly don't understand this section

I love pass, because it makes it easy to store passwords encrypted. But it doesn't make it easy to use them in any capacity other than copy-and-pasting them. I wrote gpgenv to bridge that gap:

Being drawn to pass my self, I'm looking around the net, to see what other people are doing. I was thinking of using this approach in my deploy scripts:

heroku config:set SECRET_VAR=$(pass show MyApp/serviceA)

And for locally managed scripts:

SECRET_VAR=$(pass show MyApp/serviceA)

Even this would suffice:

heroku config:set SECRET_VAR=$(gpg -d ~/.password-store/MyApp/ServiceA)

Could you please describe in more detail what advantages the gpgenv work flow brings?

As I feel i must be missing something here, thanks!

dotenv2gpg should delete .env file

Add gpgedit command

As long as we have to convert dotenv files, this won't get much traction. However, we could very likely do something like this:

Add an executable called gpgedit.
Implement it so that it reads all the .gpgenv vars and generates a temporary file in .env format containing these files, then opens $EDITOR to edit them. On close, write the files out to gpgenv again.

This way we don't need to bother with dotenv at all.