-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
password skipping config substitution #2005
Comments
+1 on this, am currently working around this by generating the yaml file and interpolating in the password from the environment manually. |
+1 |
@EliPino @whatsrupp @martinheld This is indeed a case of a fix breaking something else. We will fix this in a more robust way and cut a release. |
@eugmandel Perfect!! While I'm here, just a bit of positive feedback: I have recently set up GE on a small data pipeline at work, it was invigorating how quick it was to scaffold out some meaningful tests that I needed to put together! So, thank you! |
Thank you all for your patience! In this branch anthony/bugfix/issue-2005-password-substitution I have a preliminary fix in place (revert the bugfix #1949 & add escaping for $ characters in actual passwords), and am currently writing / cleaning up tests and documentation. |
🥇 @anthonyburdi thanks a lot! |
Thanks again for your patience! GE v0.12.7 now:
I hope this fixes your issues, please let us know if it does not! |
Describe the bug
When using environment variables to provide datasource credentials in great_expectations.yml, example:
the password is reading "${GE_REDSHIFT_PASSWORD}" as the
password
value due to this bugfix.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Not to crash and also read the value of the environment variable (${GE_REDSHIFT_PASSWORD} in this case) as the
password
value for the datasource credentials.Environment (please complete the following information):
Additional context
@anthonyburdi
The text was updated successfully, but these errors were encountered: