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

Fix bug with vault cli when reading an individual field containing a Printf formatting verb #4005

Merged
merged 1 commit into from
Feb 19, 2018

Conversation

m4x1202
Copy link
Contributor

@m4x1202 m4x1202 commented Feb 19, 2018

This PR is closely related to this one: #2109

Printf formatting verbs are working as expected when calling the cli regularly, but when calling it from a subshell they are expanded and declared missing.

Steps to reproduce, if interested:

$ vault read -field=password secret/foo
bar%sbaz
$
$ echo $(vault read -field=password secret/foo) 
bar%!s(MISSING)baz

@jefferai
Copy link
Member

Thanks!

@jefferai jefferai added this to the 0.9.4 milestone Feb 19, 2018
@jefferai jefferai merged commit 1c9f173 into hashicorp:master Feb 19, 2018
chrishoffman pushed a commit that referenced this pull request Feb 21, 2018
* oss/master: (178 commits)
  Cut version 0.9.4
  Remove netbsd/arm as it won't compile
  Bump files for new version
  Update plugins
  Update go-plugin
  changelog++
  Handling nomad maxTokenNameLength = 64 (#4009)
  Remove unneeded looping since Go 1.10 cover it already (#4010)
  Fix test statement with formatting in fatal call
  Fix PKI tests by generating on-demand
  Sanitize pem encoding to Go default of a newline at the end rather than break backwards compat
  Remove now-unneeded PKCS8 code and update certutil tests for Go 1.10
  Kick Travis
  Bump Travis to Go 1.10
  Fix bug with vault cli when reading an individual field containing a Printf formatting verb (#4005)
  Adding path roles test coverage for storing PKIX fields (#4003)
  Add test coverage for recently-added PKIX fields. (#4002)
  Fix missing CommonName in subject generation
  changelog++
  Handle missed error case in seal status output format (#4001)
  ...
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.

2 participants