Configry
Use Configry alongwith Your Favorite Secrets Manager and Keep Things Simple and Safe

Use Configry alongwith Your Favorite Secrets Manager and Keep Things Simple and Safe

Published: 5/7/2025

Image by Pexels from Pixabay

Being adaptive and flexible are best practices — and are noble traits too.

Do you want to continue with your favourite secrets server for storing sensitive data elements of your application configuration? Don't worry, we have your back. You may use Configry as an abstraction layer for such third-party integrations for a whole profile or for certain configuration variables.

PoCs

Consider a scenario where you are building a PoC which you may plan to use further while building the application if approved. You may start with storing configuration data with Configry. After you have develop a full grown app on top of that, you may set up your Configry tools to use environment variables from your favourite third-party secrets manager without changing anything in your main codebase.

MVPs

Consider again, you are building an MVP and you do not want to write code for integration with any secrets manager and also keep your application cross-cloud compatible as you have not yet decided the deployment platform. Same as above, go ahead and use Configry as you may alter the course later on.

Mixed Configuration Data

So you have lot of environment variables that affect runtime behaviour of your application and a couple of secrets too. You may use HashiCorp Vault or any other of your favourite secrets server to store the sensitive data. Rest of your environment variables can be stored directly in Configry. Use Configry layer to read whole configuration regardless of the source. Feel confident... none of the secretive data is routed through Configry layer. It comes to your application directly from source.

Dev, Stage, Prod

In love with your favourite secrets manager? Why, we do understand. You may store dev and stage configurations directly in Configry. Store Prod configuration (or only some of the variables from Prod) in your favourite secrets manager. Read all configuration and compile it in one store on your application through Configry layer. Rest assured, Configry does not pry on variables from other sources.