Move all credentials to db and have pbot pull creds from there

[mhijazi1]

Currently all creds are pulled from env variables/files on the instance running pantherbot. This should be changed. Pantherbot should only need to pull one set of creds for the DB, connect to the db, and pull all creds needed from there.

• Create DB table
• Load Creds into DB (This needs to be done by an admin)
• Pull Necessary Creds from DB
• Have DB creds pulled from env variable
• Set DB cred env variable in aws (this needs to be done by @mhijazi1)

[ferrerluis]

Even better @mhijazi1! What if you keep a .env.enc file with all credentials committed in the repo, then a single env variable to decrypt the file. This "master key" can then be shared across maintainers and injected in the instances that run Pbot.

Thoughts?

[ferrerluis]

In fact, Rails 5.1 included this sort of behavior in the framework. I know this is not Rails, but we could do something similar!

http://weblog.rubyonrails.org/2017/2/23/Rails-5-1-beta1/