summaryrefslogtreecommitdiff
path: root/tasks
Commit message (Collapse)AuthorAgeFilesLines
* Don't add a package warning for solaris_packageTim Smith2020-10-281-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Correctly generate docs yaml files to include package warningsTim Smith2020-10-281-5/+5
| | | | | | This data actually needed to be under resource_description_list and not at the top level. Signed-off-by: Tim Smith <tsmith@chef.io>
* Make sure we set both multipackage configs in the docsdocs_generation_updatesTim Smith2020-10-281-3/+4
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Improve the package docs generation + resolve rubocop warningsTim Smith2020-10-281-5/+5
| | | | | | Resolve a few valid warnings there and then add a few more resources where we should be showing package warnings. Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove the announcement rake task + minor task updatesTim Smith2020-10-204-87/+2
| | | | | | | | | - The rake task to generate the announcement no longer works because our release notes file contains all the release notes. We're going to need some automation in the future for this, but this isn't it. - Convert the docs task from .to_yml to YAML.dump - Improve the component rake task description - Nuke another copyright data range Signed-off-by: Tim Smith <tsmith@chef.io>
* Update docs generation task to handle Chef 16 required formatTim Smith2020-10-161-1/+1
| | | | | | | We need a boolean for the docs site here, but we get back an array now. For now let's just treat it like a boolean. Signed-off-by: Tim Smith <tsmith@chef.io>
* Avoid declaring arrays in loopsTim Smith2020-10-161-1/+3
| | | | | | There's still a few of these left over, but these are the easy wins with obvious wins. Signed-off-by: Tim Smith <tsmith@chef.io>
* Stop using the Ohai shortcodeTim Smith2020-09-151-7/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Update tasks/rspec.rbTim Smith2020-09-091-2/+0
| | | Co-authored-by: pete higgins <pete@peterhiggins.org>
* Use __dir__ instead of getting the dir of __FILE__Tim Smith2020-09-093-3/+3
| | | | | | This is a bit easier to read Signed-off-by: Tim Smith <tsmith@chef.io>
* Fix spellcheck task on Windows.fix-spellcheck-task-on-windowsPete Higgins2020-08-241-2/+7
| | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
* Don't depend on chef-utils when it might not be available.update-spellcheck-setupPete Higgins2020-08-051-2/+2
| | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
* Fix chefstyle violations.Pete Higgins2020-08-051-2/+2
| | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
* Update spellcheck config with nice stuff from other repos.Pete Higgins2020-08-051-6/+16
| | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
* Speed up our bundle installs by always running 3 jobsfaster_bundler_installsTim Smith2020-08-042-2/+2
| | | | | | | multi-job bundle install is the default in the next release, but for now we should make sure we set it everywhere. Signed-off-by: Tim Smith <tsmith@chef.io>
* Minor chefstyle fixes in the spellcheck taskTim Smith2020-07-101-4/+4
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Refer to specific rake file to avoid needing bundler to use rake in CI.Pete Higgins2020-07-101-3/+17
| | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
* Refactor spellcheck task and stick it in its own taskTim Smith2020-06-231-0/+34
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Fix cookstyle violations.Pete Higgins2020-06-221-3/+3
| | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
* Make the description parsing in docs rake task handle more stuff.Pete Higgins2020-06-221-20/+33
| | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
* Add more resource docs + improve yaml generationresource_docsTim Smith2020-06-051-1/+1
| | | | | | Skip defaults that are empty strings. There's a few of these floating around. Signed-off-by: Tim Smith <tsmith@chef.io>
* Improve auto-generated docsTim Smith2020-05-281-1/+1
| | | | | | | | Add more descriptions and examples Remove some smart quotes Make sure homebrew_package gets tagged as supporting multi-package Signed-off-by: Tim Smith <tsmith@chef.io>
* Fix a typo.Pete Higgins2020-05-181-1/+1
| | | | Signed-off-by: Pete Higgins <pete@peterhiggins.org>
* Pin chef-telementry to 1.0.3 to avoid ffi build breakageTim Smith2020-05-051-3/+1
| | | | | | | | | | The latest chef-telemetry gem brings in http 4 which brings in a pile off FFI gems that break the builds. Pin until the http dep is removed from the telemtry gem https://github.com/chef/chef-telemetry/issues/32. This also speeds up how to bundle our gems to match what the Workstation team did to speed up the job. Signed-off-by: Tim Smith <tsmith@chef.io>
* Split the descriptions and notes outTim Smith2020-05-011-8/+12
| | | | | | This fixes a few resources that included notes Signed-off-by: Tim Smith <tsmith@chef.io>
* We don't use the resource name bolding functionality anymoreTim Smith2020-05-011-14/+0
| | | | | | We just bold the text in the description ourselves. It's way more reliable. Signed-off-by: Tim Smith <tsmith@chef.io>
* Skip nil values in the type listTim Smith2020-05-011-4/+6
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump the ignored default length to 45Tim Smith2020-05-011-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Don't put very long descriptions in the block exampleTim Smith2020-05-011-1/+3
| | | | | | They'll wrap Signed-off-by: Tim Smith <tsmith@chef.io>
* Don't write out false values for configs in the resource yamlTim Smith2020-05-011-34/+30
| | | | | | The values default to false so only write out the true values, which makes it much easier to see what we're actually trying to set. This also means the yaml files won't wall change if we add a new config, which we will. Signed-off-by: Tim Smith <tsmith@chef.io>
* Skip syntax_shortcode entirely unless we're in a log resourceTim Smith2020-05-011-4/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove some nils that come for freeTim Smith2020-05-011-4/+0
| | | | | | Thanks Ruby! Signed-off-by: Tim Smith <tsmith@chef.io>
* Chefstyle fixesTim Smith2020-05-011-2/+2
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Handle the scenario where there are no properties betterTim Smith2020-05-011-3/+7
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove some special content for breakpointTim Smith2020-05-011-6/+1
| | | | | | We autogenerate better content that these snippets Signed-off-by: Tim Smith <tsmith@chef.io>
* Handle symbols in the equal_to valuesTim Smith2020-05-011-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Docs generation: Add examples & simplify actionsTim Smith2020-04-301-8/+3
| | | | | | Add the new docs field and skip the special casing of nothing since the hugo template actually handles that. Signed-off-by: Tim Smith <tsmith@chef.io>
* Sort the list of actions when generating docsTim Smith2020-04-291-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Add a skeleton values for actions / examplesTim Smith2020-04-291-0/+22
| | | | | | We need to extend the data we present via chef and also change the hugo template for the examples, but for now this makes the diff much easier. Signed-off-by: Tim Smith <tsmith@chef.io>
* Comment why we append --- in the docs generatorTim Smith2020-04-291-0/+2
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Make sure our yaml blocks end with ---Tim Smith2020-04-291-1/+1
| | | | | | The files aren't actually yaml. They're markdown with yaml blocks so we need to end them. Signed-off-by: Tim Smith <tsmith@chef.io>
* Tweak resource formattingTim Smith2020-04-291-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Updates to the code generation taskTim Smith2020-04-291-13/+13
| | | | | | | | | Don't generate the nil robots or syntax_code_block fields Skip empty fields in our properties Confirmed with Ian that Hugo is going to skip the empty fields anyways Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove some property deprecation logic from the generatorTim Smith2020-04-291-13/+9
| | | | | | We nuke these out of the list early on now Signed-off-by: Tim Smith <tsmith@chef.io>
* Skip documenting the deprecated propertiesTim Smith2020-04-291-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Skip the draft field in the docs generationTim Smith2020-04-291-1/+0
| | | | | | This defaults to false Signed-off-by: Tim Smith <tsmith@chef.io>
* Merge pull request #9751 from chef/lcg/chef-16-logging-fixedTim Smith2020-04-271-13/+5
|\ | | | | Rework logging to resolve STDOUT / log_location issues
| * Logging consistency fixes.lcg/chef-16-logging-fixedLamont Granquist2020-04-271-13/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - 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>
* | Don't add the weight to the yaml anymoreTim Smith2020-04-271-9/+0
| | | | | | | | | | | | It turns out if you don't add this they're just alphabetical which is what we were trying to do anyways. Signed-off-by: Tim Smith <tsmith@chef.io>
* | Chefstyle fixesTim Smith2020-04-271-31/+29
| | | | | | | | Signed-off-by: Tim Smith <tsmith@chef.io>
View Lorry Controller Status