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

Non-null header value required for using chef-automate fetcher (#258) #259

merged 1 commit into from Jul 18, 2017


None yet
3 participants

ChefRycar commented Jul 6, 2017

Signed-off-by: Nick Rycar


While specifying a workflow enterprise is not required to fetch compliance profiles from Chef Automate, inspec's validations do require that the associated header have a non-null value. Have updated the associated fetcher to seed the arbitrary value "default" into the enterprise header, and confirmed this produces the expected results in my local testing environment.

Issues Resolved

Fixes #258

Check List

Non-null value required to address #258
Signed-off-by: Nick Rycar <>

This is a great catch, thank you both!!


Much appreciated Ryan!

@alexpop alexpop merged commit 41779ab into chef-cookbooks:master Jul 18, 2017

2 checks passed

DCO This commit has a DCO Signed-off-by
continuous-integration/travis-ci/pr The Travis CI build passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment