-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat: implement ENV interceptor #56
Conversation
Signed-off-by: Ruihang Xia <[email protected]>
Signed-off-by: Ruihang Xia <[email protected]>
@waynexia Ping, do you have free time to push this further? If not, I will continue based on your branch. |
Sorry for the delay. I'm not available in these few days. Is it okay to deliver it 3~5 days later? |
Of course, take it easy. |
Signed-off-by: Ruihang Xia <[email protected]>
Signed-off-by: Ruihang Xia <[email protected]>
Signed-off-by: Ruihang Xia <[email protected]>
PTAL @jiacai2050 |
@waynexia I will review this week. |
Signed-off-by: Ruihang Xia <[email protected]>
Signed-off-by: Ruihang Xia <[email protected]>
Which issue does this PR close?
Closes #
Rationale for this change
In some cases, we may need to reference secret things in SQL, like the AWS token. This
ENV
interceptor provides a way to write sqlness cases with secret string.What changes are included in this PR?
Implement the
ENV
interceptorAre there any user-facing changes?
No
How does this change test
Unit test and integration test