-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Normalization ssh tunnel - replace '\\n' -> '\n' #9793
Normalization ssh tunnel - replace '\\n' -> '\n' #9793
Conversation
Signed-off-by: Sergey Chvalyuk <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/test connector=bases/base-normalization
|
/publish connector=bases/base-normalization
|
/publish connector=bases/base-normalization
|
Signed-off-by: Sergey Chvalyuk [email protected]
What
Users can provide SSH-TUNNEL key certificate in PEM format where newline characters
\n
replaced by\\n
.For example, this can happen if the user copy-paste the PEM certificate from the JSON file.
From the parser point of view, such PEM certificates are not correct
but because backslash symbols are not allowed in base64 encoding
we can improve user experience and safely replace back
\\n
->\n
Similar PR #8371 for Java connectors.
How
Describe the solution
Recommended reading order
x.java
y.python
🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user? If yes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.