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

Don't require empty output from augparse #12

Closed
wants to merge 5 commits into from

Conversation

mcallaway
Copy link
Contributor

Fixes #10
Fixes #13

@mcallaway mcallaway changed the title Don't require empty output from augparse. xref issue https://github.com/... Don't require empty output from augparse Apr 23, 2014
@domcleal
Copy link
Owner

domcleal commented Dec 4, 2014

Thanks for the patches. The rspec-puppet changes are required at the moment as it's incompatible with rspec-puppet 1.x, but this has been fixed for 2.0.0, which is about to be released.

Thanks for the coverage patch, merged it as 8175637 to the future branch (which contains 2.0.0 stuff).

I'm unsure about the #10 issue, so added a comment there and perhaps we can revisit it.

@domcleal domcleal closed this Dec 4, 2014
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.

rspec-puppet-augeas expects empty results from augparse Coverage reports don't see augeas resources
2 participants