| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- The doc formatter is now Chef::Config[:log_location]-aware
and will log to files as well
- There is now consistency where doc formatter output never
surprisingly changes to log formatter based on destination
- The "cli" log_location and the "config" log_location are now
treated separately, so a log_location in the client.rb will
always force output to a logfile, in addition to output
to STDOUT if necessary
- The logic around STDOUT is now simplified, if its open we
log to it, if its closed we don't, if you're daemonized we
assume you're capturing STDOUT via your process manager
- The log_location variables are now Arrays
Things not done:
- The cli can't specify an array, it would be nice to support
an accumulator pattern here. Would also need to support
disabling STDOUT logging though.
- Using the syslog or winevt logging devices requires the use
of the logger, which precludes using the formatter.
- Some people may want to have log-formatter style output
to the log file and doc formatter style output to STDOUT
which is not very possible right now. Right now we are
consistent in that you get either the logger both places
or the formatter both places. This use case is complicated
by the fact that they will want :info level logging for
the logger, but :warn level logging for the doc formatter
and that is another global.
- To do that latter thing right would probably require sending
log messages to the formatter, and supporting a different
log level in the formatter vs. the logger and then supporting
the STDOUT/cli loggging being the formatter, while the
log_location/config logging being the logger.
Those were way out of scope for what I could get done for Chef-16.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
| |
clean_env is now unbundled
Signed-off-by: Daniel Webb <dan.webb@damacus.io>
|
|
|
|
|
|
|
|
| |
Legally incredibly dubious, particularly since we don't follow it
strictly as policy, and we have git history instead, which does it right.
This is just a waste of time and a cargo cult.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
|
|
| |
+ I don't know how ---color was ever parsed to begin with.
+ -fd results in >23k lines of output that nobody reads.
+ This output obscures ~800 lines of output that everyone should
read and silence.
+ Turned off verbose in rspec rake task. It's huge and doesn't help anything.
Signed-off-by: Ryan Davis <zenspider@chef.io>
|
|
|
|
|
|
| |
Make sure the external tests continue to work.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Bring in a few more copy edits that were done on the website and improve the rake task so that it better creates docs that match the formatting we want.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the implementation of [RFC-087](https://github.com/chef-boneyard/chef-rfc/blob/master/rfc087-distro-sugar-helpers.md)
although some of the specifics have been iterated on and changed.
The documentation will be in the [README.md](https://github.com/chef/chef/tree/master/chef-utils/README.md) once this is merged.
While this PR mostly moves chef-sugar utilities into core-chef via this chef-utils gem, the scope of the chef-utils gem
should be considered larger than just that. As an example this PR moves the Mash class into this gem for reuse in ohai
as well.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
I'm also adding these same examples to the docs.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
It helps to not pass a nil in
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Formatting fixes and updates to the text to make the generated text match what's currently on the site.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Update some of our build docs to reflect the current process. Nuke the old Travis config. We're Buildkite + appveyor only at this point.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
| |
Add examples in markdown to the resources. We'll be using this on the
docs site in the future and if we need to display it we can use
tty-markdown which does a really nice job of displaying markdown in the
terminal
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
More Chefstyle updates
|
| |
| |
| |
| |
| |
| | |
since we use double quotes, be consistent everywhere.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| | |
start enforcing using %i{} instead of arrays of symbols
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| |
| | |
i like this one, gives visual priority to returns or raises that are
buried in the middle of things.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
Also prevent more extra spaces
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
|
|
|
|
|
| |
1) Fix the indentation
2) Avoid extra new lines
3) Show example data if we have it
4) Chef Infra Client vs. the Chef Infra Client
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Help out anyone stumbling upon this to know the backstory
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
| |
This adds a new feature to chef-client where users must accept the
EULA before using the product. Users can accept the license by
passing '--chef-license accept', setting ENV[CHEF_LICENSE]=accept or by
running 'chef-client' and following the interactive prompt.
Signed-off-by: tyler-ball <tball@chef.io>
|
|
|
|
|
|
| |
This process is being replaced with our new owners process as outlined in https://github.com/chef/chef-oss-practices
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
We don't do pre-releases anymore so there's no point in doing this.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
It's PowerShell not Powershell. Our docs site had already been updated.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
See also https://github.com/chef/chef-rfc/pull/322
Signed-off-by: Nathen Harvey <nharvey@chef.io>
|
|
|
|
|
|
|
|
| |
we're calling scripts to call rake tasks to call scripts to call rake
tasks to mostly execute shellcodes. this gets rid of at least 2 levels
of indirection.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
| |
mixlib-install has been out long enough at this point we don't need to
call it new or mention what version of DK originally shipped with it.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This was in DK before, but it made no sense there. This might convince some folks to test things when we cut a pre-release.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This cookbook is gone and this causes this job to fail
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
| |
absolutely hard requirement on the fixes that went into chef-config 2.2.11, so the
floor of that gem is bumped up.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
| |
We haven't used this framework for 2 major releases of Chef and as time goes on it's more and more likely we'll build something very different for testing.
We 100% do need acceptance testing, but between dokken testing in Travis and the potential for more complex integration testing with build-kite I think we should do the proper cleanup and remove this code now.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
goes red because we're really red here
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
This reverts commit 2865ca316e5b9512ffd8a7d784355e469a115717.
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
We're probably going to see some more failures with this change, but that's a good thing. If we have a bad kitchen change or a bad cookbook change we'll know now earlier. Less impact == better.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Add the chef-config unit tests to the unit testing group
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Thom May <thom@may.lt>
|
|\
| |
| | |
Update Expeditor config to use new Merge and Artifact Actions
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Chef Expeditor now supports built in merge and artifact actions which
allow us to reduce the burden of duplicating common processes across
all our repositories. This change introduces several of these built_in
functions, replacing functionality that was previously kept in our
Rakefile.
Signed-off-by: Tom Duffield <tom@chef.io>
|