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

Enable data collector w/o token for solo, but require explicit URL #5511

Merged
merged 1 commit into from
Nov 3, 2016

Conversation

danielsdeleo
Copy link
Contributor

@danielsdeleo danielsdeleo commented Nov 3, 2016

Description

Third-party data collector implementations are supported and may not
require a token for authentication. Therefore we must allow the case
where the token is nil in Chef Solo mode. To reduce the chance that the
data collector is accidentally enabled, only set the data collector URL
to a default value in Chef Client mode.

Issues Resolved

Acceptance is failing in the pipeline because it tests this exact case

Check List

Signed-off-by: Daniel DeLeo [email protected]

@danielsdeleo danielsdeleo force-pushed the allow-tokenless-chef-solo-data-collector branch 2 times, most recently from 0f92ed6 to 8db478a Compare November 3, 2016 20:12
@@ -89,7 +89,7 @@ def stop_tiny_server

it "should be able to node.save with bad utf8 characters in the node data" do
file "cookbooks/x/attributes/default.rb", 'default["badutf8"] = "Elan Ruusam\xE4e"'
result = shell_out("#{chef_client} -z -r 'x::default' --disable-config", :cwd => path_to(""))
result = shell_out("#{chef_client} -z -r 'x::default' --disable-config -ldebug", :cwd => path_to(""))
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want the logs to be in debug mode? or this was just for testing?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right, nice catch. Will fix.

@afiune
Copy link

afiune commented Nov 3, 2016

I have a little comment but code LGTM. Lets wait for travis to pass...

Third-party data collector implementations are supported and may not
require a token for authentication. Therefore we must allow the case
where the token is nil in Chef Solo mode. To reduce the chance that the
data collector is accidentally enabled, only set the data collector URL
to a default value in Chef Client mode.

Signed-off-by: Daniel DeLeo <[email protected]>
@danielsdeleo danielsdeleo force-pushed the allow-tokenless-chef-solo-data-collector branch from 8db478a to 49cc8b1 Compare November 3, 2016 20:53
Copy link

@afiune afiune left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once the test pass.

@danielsdeleo
Copy link
Contributor Author

@chef/client-core ready for review

@afiune afiune merged commit 9441dca into master Nov 3, 2016
@afiune afiune added the Bug label Nov 4, 2016
@thommay thommay added Type: Bug Does not work as expected. and removed Bug labels Jan 25, 2017
@chef chef locked and limited conversation to collaborators Nov 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Bug Does not work as expected.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants