3 ms·
Our product EnvKey[1] can also help to secure and simplify configuration of ephemeral environments—all you do is set a single ENVKEY environment variable, inclu
by danenania 8y ago
Our product EnvKey[1] can also help to secure and simplify configuration of ephemeral environments—all you do is set a single ENVKEY environment variable, include an envkey library, and then all the secrets/credentials/config you need will be made available and kept in sync on each load. You also get a nice ui for editing variables and managing access. Ah, and all this is done without trusting a central server through the magic of end-to-end encryption. I think it could potentially jive well with a tool like yours given that proper secrets management can be a tricky piece of this puzzle.
1 - https://www.envkey.com https://www.envkey.com
- andrethegiant 8y agoStumbled upon this the other day! Will take a look
- dvtrn 8y agoThis is really interesting. My team is currently solving the question of ephemeral env vars through a lot of wololo (for you Age of Empires players out there) in terraform and PUT-ing the results into a local consul cluster. Being able to instead write an env and have my application not particular care where it retrieves it from as long as a library is available is something I'm going to put in front of the rest of my team on Monday.
- koolba 8y agoThe primary problem with ephemeral environments isn’t distributing secrets, it’s provisioning the environment itself. It’s perfectly fine to generate an empty, self contained, with dummy “abcd1234” passwords or randomly generated credentials that are used only locally.
- danenania 8y agoThat works for services you control, but if you depend on external services, and these are relevant to what you’re attempting to test with a tool like FeaturePeek, then you still need to deal with credentials. Or am I missing something?