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

Environment variable resolution in HOCON config #1227

Closed
piankris opened this issue Mar 31, 2023 · 3 comments
Closed

Environment variable resolution in HOCON config #1227

piankris opened this issue Mar 31, 2023 · 3 comments

Comments

@piankris
Copy link

I saw that this feature is implemented in the collector, enricher and loader but not here. Is there a reason why the rdb module can't be configured the same way?

@istreeter
Copy link
Contributor

Hi @piankris thanks for pointing out it doesn't work -- I wasn't aware of this. I'll look into it, and hopefully get a fix into one of the next releases.

@istreeter
Copy link
Contributor

Hi @piankris we recently released RDB loader 5.5.0, and we improved how the hocon parsing works. It would be great if you can give it a try and let us know if it works for you.

You can now pass a the configuration files as arguments to the loader like this:

docker run \
  -v /path/to/config:/myconfig \
  snowplow/rdb-loader-redshift:5.5.0 \
  --config /myconfig/loader.hocon \
  --iglu-config /myconfig/resolver.json

...and your config hocon file and iglu resolver file can contain environment variables, e.g. ${API_KEY}

@istreeter
Copy link
Contributor

I'm going to close this, because as far as I know this was fixed by #1252 . Feel free to open if there is still something not working in the latest versions.

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

No branches or pull requests

2 participants