-
Notifications
You must be signed in to change notification settings - Fork 285
Add a dummy provider, remove 'defaultfor' from all other providers. #35
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
…esolves warning about multiple default providers for :vcsrepo.
Doing the following works:
Doing the following:
Gives the following error:
|
I think there's a way to have a "magic method" that will respond to any undefined method in the class. That method would log a warning rather than blowing up the puppet run. I'll get right on it! (There's no such magic in ruby, so I'll use |
Go for it - we're all hanging around the office and looking to merge in pull requests. Just register a comment here when/if you find something! :) |
Bunch of cleanups and junk to get tests running again and passing. Finally then, added an exception to the dummy provider, and a test to check for the exception. Here's what it looks like running, with a bogus resource:
This output is seen in a puppetized node:
|
Conflicts: lib/puppet/provider/vcsrepo/cvs.rb spec/support/fixture_helpers.rb spec/unit/puppet/provider/vcsrepo/cvs_spec.rb
Merged from master, ready to integrate. I reverted #27, it broke all of the git unit tests. |
Ping? Vcsrepo 0.1.0 is basically unusable until this is resolved, I'd love to see this merged and bumped to 0.1.1. Then we can tackle the default user issue and some of the other git inefficiencies. I have more code to submit pending this merge. |
I merged in the commit that broke vcsrepo, so I'll take this one. Let me pull your branch, run the tests, and see about getting this merged in tonight |
I've pulled in the changes, run the spec tests, and they're passing. Applying the test from before gets the following: info: Applying configuration version '1351643948' err: /Vcsrepo[/tmp/plist]: Could not evaluate: vcsrepo resource must have a provider, available: bzr, cvs, git, hg, svn info: Creating state file /Users/glarizza/.puppet/var/state/state.yaml notice: Finished catalog run in 0.02 seconds I'm satisfied with the changes - merging this in! |
Add a dummy provider, remove 'defaultfor' from all other providers.
Yay, thank you! |
A new release was cut for the Forge --> http://forge.puppetlabs.com/users/puppetlabs/modules/vcsrepo/releases/0.1.1 |
And all tests passing in TravisCI --> https://travis-ci.org/#!/sodabrew/puppetlabs-vcsrepo/builds/2962633 Ahhh yisssss |
This is very interesting because I'm still seeing this warning. I have verified that I do in fact have the latest code in my puppet master and that I'm only seeing the defaultfor for the dummy. Is it possible that the duplicate defaultfor settings are being cached on the master? FWIW, I'm using the latest gitlab module that uses vcsrepo. The module has this in one of the manifests:
Could this be the cause of my issue? |
I force git provider as well and I get the following Using vcsrepo 1.0.1 and puppet 3.6.2 |
I'm seeing the same thing. |
Same here, i get "Warning: Found multiple default providers for vcsrepo: dummy, git, p4; using dummy" with Puppet 3.6.2 and VCSRepo 1.0.2 |
Warning: Found multiple default providers for vcsrepo: git, p4, dummy; using git puppet 3.6.2 |
Yep, this definitely has become an open issue again with Puppet 3.6 :| |
Resolves warning about multiple default providers for :vcsrepo.
See:
http://projects.puppetlabs.com/issues/16958
http://projects.puppetlabs.com/issues/6403