Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow using env vars in the driver config file #401

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

LiquidPL
Copy link

Resolves #400.

@LiquidPL
Copy link
Author

Okay, turns out this doesn't necessarily work as I expected, since with the current chart the env tag in the config file gets removed (presumably because Helm is trying to parse it and has no idea what it is).

This would probably require some fixes on the chart side, but I'll wait with that to get an opinion from the maintainers, since I'm not sure if I'm going in a right direction with this.

@LiquidPL LiquidPL marked this pull request as draft May 16, 2024 16:39
This commit makes it possible to use environment variables in the driver
configuration file, using the `{env:<environment variable name>}`
format.
@LiquidPL LiquidPL force-pushed the env-yaml-tag branch 2 times, most recently from 71af3e5 to 4f817c3 Compare May 16, 2024 21:18
@LiquidPL
Copy link
Author

I have changed this to not use YAML tags, since this approach proved problematic when applying the config using a Helm chart, now it is handled using a simple string substitution, for instance {env:TRUENAS_API_KEY}. Please let me know if you want this format to be different.

@LiquidPL LiquidPL marked this pull request as ready for review May 16, 2024 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow injecting environment variables into the driver config
1 participant