-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Knife Bootstrap: Passing config_log_level and config_log_location from config.rb #5502
Knife Bootstrap: Passing config_log_level and config_log_location from config.rb #5502
Conversation
83a5661
to
31a168f
Compare
@dheerajd-msys you'll need to update the specs that have blown up travis, but otherwise this is good, thank you! |
…ed specs failure Signed-off-by: dheerajd-msys <[email protected]>
31a168f
to
6949868
Compare
@@ -69,7 +69,8 @@ def trusted_certs | |||
|
|||
def config_content | |||
client_rb = <<-CONFIG | |||
log_location STDOUT | |||
log_level :#{@chef_config[:config_log_level]} | |||
log_location "#{@chef_config[:config_log_location]}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are two possible issues that may require fix:
- What happens if
config_log_level
andconfig_log_location
are not passed? Are the values oflog_level
andlog_location
getting passed in that case? - Is
config_log_location STDOUT
getting passed successfully?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should make sure we keep the default log location of STDOUT.
Signed-off-by: dheerajd-msys <[email protected]>
1b04c52
to
c961abe
Compare
Signed-off-by: dheerajd-msys <[email protected]>
c961abe
to
63a6d5e
Compare
Description
Passing config_log_level and config_log_location from config.rb
Issues Resolved
#1452
Check List