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

(#17522) Only print load errors to debug with non-specific context #1454

Conversation

domcleal
Copy link
Contributor

@domcleal domcleal commented Feb 6, 2013

Replaces GH-1280, rebased to master.

Fixes a variable assignment that landed in the wrong branch during a conflict
merge (a4451fb). Commit a8575f4 fixed a spec failure but the original code
wasn't restored.

This restores the original functionality in #14136 where a non-specific
context (i.e. /files/etc) would be optimised (only load lenses for files under
/etc) but since it was vague, would only log load errors to debug. Instead,
load errors were reported as warnings for non-specific contexts.

Load errors will continue to be reported as warnings for supplied contexts if
they're specific.

Fixes a variable assignment that landed in the wrong branch during a conflict
merge (a4451fb).  Commit a8575f4 fixed a spec failure but the original code
wasn't restored.

This restores the original functionality in #14136 where a non-specific
context (i.e. /files/etc) would be optimised (only load lenses for files under
/etc) but since it was vague, would only log load errors to debug.  Instead,
load errors were reported as warnings for non-specific contexts.

Load errors will continue to be reported as warnings for supplied contexts if
they're specific.
@domcleal
Copy link
Contributor Author

domcleal commented Feb 6, 2013

See 911e2d4 for the original code for #14136.

@jeffmccune
Copy link
Contributor

Thank you for contributing to Puppet!

Merged into master as cc267a8.

This should be released in puppet 3.2.

Thanks again for the contribution!

-Jeff

@jeffmccune jeffmccune closed this Feb 6, 2013
@jeffmccune
Copy link
Contributor

Err, that should have been "puppet 3.2" and not 3.3 in my previous comment. I've edited it.

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.

None yet

2 participants