Skip to content
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

Revert #347 #375

Closed
wants to merge 1 commit into from
Closed

Revert #347 #375

wants to merge 1 commit into from

Conversation

josqu4red
Copy link

Description

PR #347 introduced wrong behaviour by adding extra logic before JSON
parsing, which prevents some perfectly valid use cases such as multiline PEM-encoded data.
There are several issues related to this already, so it should be
removed.

Related Issue

Fixes #370, #372

Types of changes

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

@josqu4red josqu4red requested review from a team as code owners July 1, 2021 07:33
PR #347 introduced wrong behaviour by adding extra logic before JSON
parsing, which prevents some perfectly valid use cases such as multiline PEM-encoded data.
There are several issues related to this already, so it should be
removed.

Fixes #370, #372

Signed-off-by: Jonathan Amiez <jonathan.amiez@gmail.com>
@vkarve-chef
Copy link
Contributor

addressed through #367

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Impossible to store SSL/SSH private Key in vault
2 participants