| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
| |
|
|
|
|
| |
Signed-off-by: Thom May <thom@may.lt>
|
| |
|
|\
| |
| | |
add back method_missing support to set_unless
|
| | |
|
| |
| |
| |
| | |
closes #5012
|
|\ \
| | |
| | | |
Warn if not installing an individual bff fileset
|
| |/ |
|
| |
| |
| |
| | |
its necessary to set the breadcrumb to something wrong first.
|
|/
|
|
|
|
| |
note that the node_spec test in this commit is not red on master
so it ain't testing the right thing yet, but this fixes the
issue in chef-shell...
|
|
|
|
|
|
|
| |
this allows us to be truely cross platform, and also to ignore unsafe
paths and permissions.
Signed-off-by: Thom May <thom@chef.io>
|
|\
| |
| | |
Data Collector server URL validation, and disable on host down
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a user configured data_collector.server_url in their Chef config
as an empty string, we blissfully passed it along to Chef::HTTP
which would eventually raise a TypeError when trying to dup the
URI's host. This change validates the server_url when setting up
the Data Collector and gives helpful error messages to the user.
We also count Errno::EHOSTDOWN as an error worthy of disabling
the Data Collector reporter for a given run if the user so chooses.
|
|/
|
|
|
|
|
|
| |
- clean up "ZenMaster" resource
- clean up 3694 detection to use properties
- unlazy the resource_name in the trivial resource check
- fixes an issue with resources-as-definitions pattern emitting
3694 errors for trivial resources
|
|\
| |
| | |
Adding node object to Data collector run_converge message
|
| |
| |
| |
| | |
gets serialized correctly
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Many use cases that involve consuming the run_converge messages and
displaying them to end users include needing additional data about
the node that generated the run_converge message. This change
consolidates the run_converge and node_update message into a single
message making it easier for users to filter run_converge messages
based on attributes and criteria of the node itself.
Additionally, the ignore_failure property on a resource is now
included for each resource in the resource list so end users can
decided whether the failure was a hard failure or a soft failure.
|
|/
|
|
|
|
|
|
|
|
|
| |
- fixes *_unless behavior and set_unless_value_present hack from Chef 12
- simplifies rm_* code
- introduces functional read/write/unlink/exist? API
- deprecates method_missing access to attributes for Chef 13
- deprecates set/set_unless aliases for Chef 14
- removes MultiMash mess that I wrote for Chef 13
https://github.com/chef/chef/pull/5029 for more details
|
|\
| |
| |
| |
| | |
chef/adamleff/IPO-196/add-unprocessed-resources-to-data-collector
Expand data_collector resource list to include all resources
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Historically when a Chef run fails, the event handlers only report
on resources that have been processed during the run. This change
allows the Data Collector to report those resources in the resource
collection that have not yet been processed so users can better
ascertain how much of their run was completed, and specifically
what resources were not processed as a result of the Chef failure.
Instead of building up a list of resources as they are processed,
this change instead creates a resource report for each resource+action
in the resource collection and then modifies each of those reports
once the resource is processed.
|
|/
|
|
|
|
|
|
|
| |
Solo has always defaulted to `/var/chef` but local-mode uses the user's
home directory, so we need to ensure that we set the correct path before
entering local-mode.
Fixes: #5051
Signed-off-by: Thom May <thom@may.lt>
|
| |
|
|\
| |
| | |
Deprecate knife-supermarket gem
|
| |
| |
| |
| |
| |
| |
| | |
Include all knife supermarket sub commands here, and allow all knife
cookbook site commands to have a configurable supermarket URL.
Signed-off-by: Thom May <thom@may.lt>
|
| |
| |
| |
| | |
Signed-off-by: Thom May <thom@chef.io>
|
|\ \
| | |
| | | |
Convert the 3694 warning to a deprecation so it will be subject to the usual deprecation formatting (collected at the bottom, can be made an error, etc).
|
| | |
| | |
| | |
| | | |
deprecation formatting (collected at the bottom, can be made an error, etc).
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When we changed the messages from class instances to a module, the
reading of metadata into an instance variable was removed and
introduced a bug when updating metadata. This bug causes the
metadata to be properly read from disk, updated, but then the
metadata from disk is simply re-written to disk without the
intended updates.
|
| |
| |
| |
| |
| |
| |
| |
| | |
After adding up-to-date and skipped resources to the DataCollector
resource list, the logic that computed the number of resources
updated needed to change accordingly. This change fixes that
bug and also eliminates an unnecessary counter that tracks
the total number of resources.
|
| | |
|
|\ \
| | |
| | | |
Skip `ps_credential` test for `dsc_script` until proper test cert
|
| | | |
|
| | |
| | |
| | | |
closes #4988
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The DataCollector reporter is a new method for exporting data about your
Chef run. The details of this new feature can be found in
[RFC 077](https://github.com/chef/chef-rfc/blob/master/rfc077-mode-agnostic-data-collection.md).
Using the existing `EventDispatch` mechanics, the DataCollector reporter
collects data about a Chef run (when it starts, when it ends, what
resources were modified, etc.) and then POSTs them to a Data Collector
server URL that can be specified in your Chef configuration.
While similar functionality exists using the `ResourceReporter` and Chef
Reporting, a new implementation was done to decouple the reporting of this
data from requiring the use of a Chef Server (in the case of Chef Reporting),
opening the door to users being able to implement their own webhook-style
receiver to receive these messages and analyze them accordingly.
|
|\ \ \
| | | |
| | | | |
Ensure recipe-url works right in solo
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Thom May <thom@chef.io>
|
|\ \ \
| | | |
| | | | |
add systemd_unit try-restart, reload-or-restart, reload-or-try-restart actions
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fix portage provider to support version with character
|
| | | | | |
|
| | | | | |
|
|/ / / / |
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* exit code functional specs
* audit exit codes
* reboot now/reboot failed/reboot pending exit codes
* Deal with forked and unforked process and get the right exit code
* Reboot Now should really be reboot scheduled
* pass exception rather than exit code
* updated with sigint and sigterm
* support legacy fatal!("", 2) behavior
* fixup all fatal! and exit! calls
|
|\ \ \
| | | |
| | | | |
Handle numeric id for the user value in the git resource
|
| | | | |
|
| | | | |
|
| | | | |
|