[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin
Title: Message Title Joseph Petersen closed an issue as Cannot Reproduce Jenkins / JENKINS-52889 new lines in secret is substituted by spaces when reading via Vault plugin Change By: Joseph Petersen Status: Open Closed Assignee: Peter Tierno Joseph Petersen Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192828.1533446727000.15467.1587529080673%40Atlassian.JIRA.
[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin
Title: Message Title Samuel Beaulieu commented on JENKINS-52889 Re: new lines in secret is substituted by spaces when reading via Vault plugin Hee Won Kim you should iclude the actual shell script lines you are running. I hit the same issue and debugged the plugin. Things are received from Vault with the "\n" preserved as far as I could see, so I looked into issues with the printing of it. The issue arises because of the command substitution in bash http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03 and you can fix that by setting IFS= as per https://unix.stackexchange.com/questions/164508/why-do-newline-characters-get-lost-when-using-command-substitution BUT its easier to just embed it in double quotes so that: if I do this it is replaced by spaces echo $FOO > .foo but if I do this instead it works echo "$FOO" > .foo then the newlines are preserved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192828.1533446727000.3637.1564442100299%40Atlassian.JIRA.
[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin
Title: Message Title
Samuel Beaulieu edited a comment on JENKINS-52889
Re: new lines in secret is substituted by spaces when reading via Vault plugin
[~saillinux] you should iclude include the actual shell script lines you are running. I hit the same issue and debugged the plugin. Things are received from Vault with the "\n" preserved as far as I could see, so I looked into issues with the printing of it. The issue arises because of the command substitution in bash [http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_03]and you can fix that by setting {{IFS=}} as per [https://unix.stackexchange.com/questions/164508/why-do-newline-characters-get-lost-when-using-command-substitution] BUT its easier to just embed it in double quotes so that:if I do this it is replaced by spaces{code:java} echo $FOO > .foo{code}but if I do this instead it works{code:java} echo "$FOO" > .foo{code}then the newlines are preserved
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192828.1533446727000.3641.1564442100372%40Atlassian.JIRA.
[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin
Title: Message Title fragpit fragpit commented on JENKINS-52889 Re: new lines in secret is substituted by spaces when reading via Vault plugin Same for me, looks like it's unable to work with certificates stored as secrets using this plugin without additional formatting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin
Title: Message Title
Hee Won Kim updated an issue
Jenkins / JENKINS-52889
new lines in secret is substituted by spaces when reading via Vault plugin
Change By:
Hee Won Kim
When I read secrets using Vault Plugin from both Freestyle and Pipeline jobs, if secrets contains new lines e.g. '\n'. it gets substituted to space characters. In actual contents in the secret:{quote}multi lines contentssecond lines{quote}In vault JSON: { quote}{ "key1": "multi lines contents\nsecond lines"} {quote} when it's been read from Vault plugin to a job, {quote} "multi lines contents second lines" {quote} Please let me know if you need further detail. Thanks in advanced.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin
Title: Message Title
Hee Won Kim created an issue
Jenkins / JENKINS-52889
new lines in secret is substituted by spaces when reading via Vault plugin
Issue Type:
Bug
Assignee:
Peter Tierno
Components:
hashicorp-vault-plugin
Created:
2018-08-05 05:25
Priority:
Minor
Reporter:
Hee Won Kim
When I read secrets using Vault Plugin from both Freestyle and Pipeline jobs, if secrets contains new lines e.g. '\n'. it gets substituted to space characters. In vault JSON: {"key1": "multi lines contents\nsecond lines"} when it's been read from Vault plugin to a job, "multi lines contents second lines" Please let me know if you need further detail. Thanks in advanced.
Add Comment
