| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
We're on chef 12!
|
|\
| |
| | |
Lcg/array name deuglification
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- the constructor was bypassing the setter method and allowing random
objects to be set as names when the intent is to only accept strings.
- failing on non-string objects would be a backwards incompatible
change so the constructor was changed to coerce to a string (this has
come up before with the log resource being passed an object).
- a special case was added for arrays so that the name arg of
multipackage installs looks like:
apt_package[lsof, bc]
instead of:
apt_package[["lsof", "bc"]]
- the special case for the array likely only affects the OnePerson(tm) out
there who is passing an array to a resource (like log) already and using
notifies or subscribes against it. better to xkcd that person
now than to have people start to build notification against the new
multipackage syntax and then have to break a lot more people with
Chef-13.
- this doesn't affect the internals of the multipackge stuff because the
packge_name is set to the value the constructor gets (which is an
array) so that the coercsion to string does not affect provider behavior,
but will get notify/subscribe and other resource collection manipulation
and reporting correct.
|
|\
| |
| | |
fix warning output
|
|/
|
|
|
| |
When this got extracted into its own class `self` no longer outputs the
resource which is being built.
|
|\
| |
| | |
Fix error message in yum provider (related to multipackage refactor)
|
|/ |
|
|\
| |
| | |
Multipackge support
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
- fixes define_resource_requirements
- better idempotency (only packages that need updating are updated)
- better messaging (only packages that update are output)
- better comments
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit a88c852e7166c2d209d0670f668cf67feab19222.
We can't easily do this without changing a LOT of other assumptions. Since all
the consumer sites already call `as_array` functions, it's easier to keep those
safe.
|
| |
| |
| |
| | |
Also handle a lot more corner casses consistently and cleanup more code.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Allow the `package` provider to take an array of packages to handle in one
transaction.
This solves two large problems:
* There are times when you cannot install two packages in sequence, like when a
binary is moving between two packages - they *must* be done in the same
transaction.
* When using Chef to install the vast majority of your base system, it
can make imaging take a very, very long time because executing yum or apt once
for every single package is painfully slow.
This solves both. The scaffolding is all there in the Package HWRP, plus the
underlying implementation for both apt and yum, the two I have access to test.
|
|\ \
| | |
| | | |
Fixing Rspec 3.2 update. We were overriding private APIs which changed.
|
| | | |
|
| |/
|/|
| |
| |
| |
| | |
paludis_package and reboot resources.
Closes #2841.
|
|\ \
| | |
| | | |
Make chef-full bootstrap use chef.io URL.
|
| | | |
|
|\ \ \
| |_|/
|/| | |
fix LWRP constant lookups
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
* providers had the same bug as CHEF-4117 on resources
* removed the strict_const_defined method on Chef::Resource since
ruby 1.8.7 deprecation made that method entirely trivial
* added tests, verified the failure cases really work
* todo added since i think we're leaking state in-between tests
|
|\ \
| |/
|/| |
pin rspec to 3.1.x for now
|
|/
|
|
|
| |
rspec 3.2.0 release changed some private APIs in rspec that we were using for audit
mode and broke our master (kind of expected/understandable).
|
|\
| |
| | |
Add .mailmap for top contributors
|
| |
| |
| |
| |
| | |
Current chef employees who have been contributing with a Chef-related
email address now use chef.io as their primary email.
|
|/ |
|
|\
| |
| | |
Can I maintain things?
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Merging https://github.com/chef/chef/pull/2698
|