Menu
Sign In Pricing Add Podcast

Ruby Rogues

Secrets Management Best Practices and Tools - RUBY 655

1435.691 - 1454.201 Brian Vallelunga

That way developers aren't working around the system and then recreating that risk you're trying to avoid. And it should be natively integrated with your production and staging infrastructure so that When it is time to roll out a secret, you don't have this race condition of the code arriving before the secrets do. The secrets have to arrive first if the code is going to rely on those secrets.

0
💬 0

Comments

There are no comments yet.

Log in to comment.