Hey everyone! :wave: I have a question about mana...
# best-practices
d
Hey everyone! 👋 I have a question about managing environments in meltano. Its straightforward to have different configurations per environment except when it comes to secrets. These get written to the .env file. What are the best practices for having multiple different version of secrets for each environment? I tried using environment variable expansion at the plug in level with:
Copy code
env:
  CLIENT_SECRET: $CLIENT_SECRET_SANDBOX
However, this doesn't actually inject the secret (also doesn't when I format with quotes or braces in all combinations. Any advice would be most welcome! 🙏
a
Hi @Derek Wayne are you talking about local development or deployment? For local development I use the env switcher extension in vscode https://marketplace.visualstudio.com/items?itemName=EcksDy.env-switcher you basically create separate .env files for your individual sets of secrets, and then overwrite the contents of your main .env when you 'switch'
👍 1
d
Thanks Andy! I think that would work fine 🙂 Appreciate it
👍 1