-
Notifications
You must be signed in to change notification settings - Fork 10
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 env var configuration of updated transformation config #174
Milestone
Comments
colmsnowplow
added a commit
that referenced
this issue
Jul 21, 2022
colmsnowplow
added a commit
that referenced
this issue
Jul 21, 2022
colmsnowplow
added a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
added a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
added a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
added a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
added a commit
that referenced
this issue
Jul 22, 2022
colmsnowplow
added a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
added a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
added a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
added a commit
that referenced
this issue
Aug 12, 2022
colmsnowplow
added a commit
that referenced
this issue
Aug 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #169 we instrument a new, more sensible way of configuring transformations.
This change replaces our old hacky workaround transformation configuration with HCL - which supports arrays and allows us to be much more declarative in our config.
However, the downside is that it's not configurable via env var. This task is to introduce an env var which allows us to provide a base-64 encoded hcl configuration, which we will parse and use as the transformation config.
The text was updated successfully, but these errors were encountered: