3 ms·
Why does somebody pushes AWS Keys into a Git Repository? Why should somebody ever push some Authentications? Currently when I code an app I create a database wi
by merb 11y ago
Why does somebody pushes AWS Keys into a Git Repository? Why should somebody ever push some Authentications?
Currently when I code an app I create a database with name of the app and have new credentials with just name:name so that the only thing that I check into my config if the app needs a application.conf or resource.conf are default username:passwords for development, so that bootstrapping is easier. However EVERYTHING else gets read from the Environment Variables that even Works on Windows since Visual Studio has a Feature for that, but be aware the sln file we keep the values. So however never ever put anything into git / source code repo which shouldn't be read.
- zeveb 11y ago> Why does somebody pushes AWS Keys into a Git Repository? If one wants to use version control to track credentials, then this makes sense. Why would one want to do that? In order to track versions of one's production system. This enables things like one-shot rebuilds. Now, it's obvious that such a production repository should be separate from one's development repo(s). And one could make a decent argument that it should never be pushed someplace like GitHub anyway, even as a private repository.
- balls187 11y ago> Why does somebody pushes AWS Keys into a Git Repository? Wild speculation, but this is a side effect of "developer" centric operations. Everything is done via code, and developers are instinctively trained to check in code.