| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
use this to inject the tempfile from
Chef::FileContentManagement::Tempfile
closes #2401
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\
| |
| | |
fix for data bag names partially matching search reserved words
|
| |
| |
| |
| | |
Signed-off-by: Sandra Tiffin <sandi.tiffin@gmail.com>
|
|\ \
| | |
| | | |
Slight improvements to validation failures
|
| | |
| | |
| | |
| | | |
Signed-off-by: Thom May <thom@chef.io>
|
| | |
| | |
| | |
| | |
| | | |
possible and doesn't show anything for sensitive resources to be safe.
Refs https://github.com/chef/chef/issues/4793 and ping @chef/client-core for review.
|
|\ \ \
| |/ /
|/| | |
Modernize cookbook_file resource and expand specs
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Don't hardcode the provider since the provider already has a provides line
Test the source logic default properly by creating the resource name as a absolute path, which is how the user would use it
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\ \ \
| |/ /
|/| | |
implement credential management
|
| | |
| | |
| | |
| | | |
Signed-off-by: Thom May <thom@chef.io>
|
| |/
| |
| |
| | |
Signed-off-by: Thom May <thom@chef.io>
|
|\ \
| | |
| | | |
Modernize reboot resource and add spec
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | |
| | |
| | | |
The path helper does exactly what we expect it to and that makes this only work on *nix
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The two issues fixed here:
1) cab_package did not require source, but didn't set it from the resource name so cab_package 'xyz.cab' would just fail since source was nil
2) msu_package would coerce the resource name and not package_name so if you overwrote the package name you would also have to set the source, although you wouldn't realize that until it failed oddly
So the solution here is to set the source value to package_name by default and that gets coerced into a path as was previously done. This adds tests for this behavior and the coerce behavior itself to both resources.
This fixes issue #6674
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
|
|
|
| |
Actions are arrays now
Since we properly set source as a name property name gets coerced into a source path as expected. This was a bug before. This also uncovered #6674 which I'll fix in another PR.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| |
| |
| | |
MsysTechnologiesllc/vasundhara/chef_windows_task_resource_not_idempotent_for_any_command
windows_task: Fix resource isn't fully idempotent due to command property
|
| |
| |
| |
| | |
Signed-off-by: Vasu1105 <vasundhara.jagdale@msystechnologies.com>
|
|\ \
| | |
| | | |
Invalid date error on windows_task with frequency :on_logon
|
| | |
| | |
| | |
| | | |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
| |/
|/|
| |
| | |
Signed-off-by: Thom May <thom@chef.io>
|
|\ \
| | |
| | | |
Ensure data bags names can contain reserved words
|
| | | |
|
|\ \ \
| |/ /
|/| | |
windows_task: Add additional input validation to properties
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | |
| | |
| | | |
RuntimeError
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Also set the default the right way with execution_time_limit
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |/
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\ \
| | |
| | | |
Solaris: Fix svcadm clear to only run in maintenance state
|
| |/
| |
| |
| |
| | |
Signed-off-by: Jaymala Sinha <jsinha@chef.io>
Signed-off-by: Patrick Wright <patrick@chef.io>
|
|/
|
|
|
|
| |
but we really shouldn't do this...
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
Specify exactly what we're checking for in the error. This needs to go into the docs site as well.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
speedup lwrp tests
|
| |
| |
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
reset the global resource and provider handler maps before each and
every test.
note that mutation through the top-level keys will get preserved so
this is not perfect, but deep-duping through every single test we run
becomes expensive.
this is sufficient to flush out the global state of all the test lwrp fixtures
that we setup.
it discovered several usage bugs where we either relied on this feature
or where we were testing different fixtures from the ones we thought we
were.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\ \
| | |
| | | |
Node attributes per-container lazy deep merge and deep merge performance improvements
|
| | |
| | |
| | |
| | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Replaces the one-big top level deep merge cache with individual deep
merge caches in every container. The Immutable container state becomes
the deep merge cache.
- Does not use a pure decorator style approach since that failed before
because of ruby internals breaking things like `===` and `=~` on
decorated objects, so we inherit (ultimately from Hash + Array).
- The state being the container state is useful in ruby since APIs on
Hash and Array poke around in internal state to make things fast. If
we inherit from Hash/Array but don't have the correct internal state
things go wonky.
- Throwing away the internal state is equivalent to flushing the cache.
- Since we throw away all linked objects when we do that, we flush at
every level below the level being flushed (which is correct semantics).
- If a user has a pointer to an old immutable object from a sub-level,
that isn't mutated so the old object still contains the old view of
the data (which I think is correct, although I have some doubts that
its necessary, but it came along free for the ride).
- When we reset the cache we do mutate the cache being reset, which
might change data in held references. If this becomes an issue the fix would
be to reset the cache at the level above by creating a new, "empty"
ImmutableHash/ImmutableArray object and inserting it into the
deep_merge_cache datastructure instead of clearing the internal state
of the child object. I don't know practically how anyone would hit
this, though, so would prefer to wait on doing that work until we see
an actual bug report.
- Because of the way ruby pokes around internally there's some
weirdnesses like the pre-generation of the cache for all the values of
a subarray when #each is called, which is due to the way that ruby
walks through array-serialized hashes when called like:
`Array#each { key, value| ... }` (which is an undocumented(?) thing
in ruby).
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|/
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
Knife SSH prefix option
|