Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #70419
| Newsgroups | comp.lang.python |
|---|---|
| Date | 2014-04-20 09:36 -0700 |
| Message-ID | <267e12d3-ea01-4886-bfa7-5c7270adbe92@googlegroups.com> (permalink) |
| Subject | [OT] Testing and credentials best practices? |
| From | Miki Tebeka <miki.tebeka@gmail.com> |
Greetings, How do you deal with tests (both on dev machine and Jenkins) that need credentials (such as AWS keys)?. I know of the following methods: 1. Test user with known (stored in source control) limited credentials 2. ~/.secrets (or any other known location) RC file which is not in source control 3. Credentials service (such as ZooKeeper) accessed only from VPN 4. Credentials pre user encrypted (gpg) and stored in source control What method are you using? Are there any best practices in the subject? Thanks, -- Miki
Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread
[OT] Testing and credentials best practices? Miki Tebeka <miki.tebeka@gmail.com> - 2014-04-20 09:36 -0700
Re: [OT] Testing and credentials best practices? Chris Angelico <rosuav@gmail.com> - 2014-04-21 02:45 +1000
Re: [OT] Testing and credentials best practices? Miki Tebeka <miki.tebeka@gmail.com> - 2014-04-21 12:03 -0700
Re: [OT] Testing and credentials best practices? Roy Smith <roy@panix.com> - 2014-04-20 14:32 -0700
csiph-web