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

tls_disable attribute only accepts strings #40

todd-a-jacobs opened this Issue Mar 1, 2016 · 1 comment


None yet
2 participants

todd-a-jacobs commented Mar 1, 2016

When 'tls_disable' = true, the recipe blows up because it's expecting a String rather than a Boolean or Fixnum. The attribute parser really ought to be more flexible and accept:

  • true
  • false
  • 0
  • 1

and then coerce to String if necessary to fit Vault's expectations. Pull request to follow.


This comment has been minimized.


johnbellone commented Mar 4, 2016

This has been updated in latest master branch set of commits and will be released as 2.0.

@johnbellone johnbellone closed this Mar 4, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment