| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
provides? on a provider was passed the full resource. provides? on
a resource class cannot be passed the resource and must be passed the
declared_type instead. i tried to make them the same, but that would
change the API on the provider.
|
|
|
|
| |
This reverts commit 57cdbe124f63e47cab960e714572539d3979b90f.
|
|
|
|
|
|
|
| |
provides? on a provider was passed the full resource. provides? on
a resource class cannot be passed the resource and must be passed the
declared_type instead. i tried to make them the same, but that would
change the API on the provider.
|
|
|
|
| |
also wire them up through the Chef class.
|
|
|
|
|
|
| |
move the sorting of the providers to after we make the first cut, still
keeps deterministic ordering, but avoids sorting providers we are just
going to throw away.
|
|
|
|
|
|
|
|
| |
* makes provides? more correct for linux services
* makes supports? more targetted for linux services
* remove provider_resolver from the run_context
* fix timestamped deploy spec
* add more specs
|
| |
|
|
|
|
|
| |
makes resource and provider class resolution more dynamic.
begins deprecation of Chef::Platform static mapping.
|
|
|