summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* creating a temp branch to work fromjfm/wingetJohn McCrae2021-05-149-8/+822
| | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
* Bump version to 17.1.23 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Fix a typo setting up cookbook_name value in templatesTim Smith2021-05-142-2/+1
| | | | | | There was an extra o in the logic in this setup Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 17.1.22 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Clarify username / pw is windows onlyTim Smith2021-05-142-3/+2
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Add introduced to the new hostname propertiesTim Smith2021-05-142-6/+4
| | | | | | Make sure the docs get generated correctly Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 17.1.21 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Use buffered i/o for yum and disable repos in testingLamont Granquist2021-05-143-16/+14
| | | | | | | This sync's the yum provider back up with the further work done on the dnf provider. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Bump version to 17.1.20 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* messed up a squash. correcting the codeJohn McCrae2021-05-142-11/+5
| | | | Signed-off-by: John McCrae <jmccrae@chef.io>
* Updated the Windows code to use Rename-Computer, added properties for a ↵John McCrae2021-05-141-1/+8
| | | | | | domain username and password. Signed-off-by: John McCrae <jmccrae@chef.io>
* Updated the Windows code to use Rename-Computer, added properties for a ↵John McCrae2021-05-141-2/+33
| | | | | | domain username and password. Signed-off-by: John McCrae <jmccrae@chef.io>
* Bump version to 17.1.19 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* DNF provider updateLamont Granquist2021-05-143-555/+877
| | | | | | | | | | | | | - stabilization fixes to the provider - we now no longer retry in specs and fail on any errors - we disable all the repos in the specs for speed - we only reap the daemon to flush the cache in the specs - we also only reap the daemon after having setup repos - all the func specs have been converted to inline resources - all the i/o is now blocking+flushing instead of nonblocking+confusing (how did it all ever work? why did i use nonblocking i/o?) Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Bump version to 17.1.18 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* updated a comment to force a rebuildJohn McCrae2021-05-141-0/+1
| | | | Signed-off-by: John McCrae <jmccrae@chef.io>
* 'LockoutThreshold' is actually implemented by Windows as LockoutBadCount. ↵John McCrae2021-05-141-0/+2
| | | | | | What shows up in an Account Lockout Policy is Account Lockout Threshold but what gets written to disk when you change it is LockoutBadCount. That item is available in the list of existing policy objects. I updated the code to add AuditPolicyChange; that was mssing. I also added ResetLockoutCount which pairs with the Lockout Threshold so users aren't permanently locked out. The last item, LockoutObservationWindow, does not appear in a Security Policy as exported by secedit but you can get to it via PowerShell. It is part of a customized fine grain password policy. Read more here: http://woshub.com/fine-grained-password-policy-in-windows-server-2012-r2/ Signed-off-by: John McCrae <jmccrae@chef.io>
* Bump version to 17.1.17 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump inspec-core-bin to 4.37.0Chef Expeditor2021-05-141-4/+4
| | | | | | This pull request was triggered automatically via Expeditor when inspec-core-bin 4.37.0 was promoted to Rubygems. This change falls under the obvious fix policy so no Developer Certificate of Origin (DCO) sign-off is required.
* Bump version to 17.1.16 by Chef ExpeditorChef Expeditor2021-05-147-17/+17
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Stop the endless File.exists? spam from chef/nodeLamont Granquist2021-05-141-1/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Bump version to 17.1.15 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Suppress unified mode deprecation warning for deprecated resourcesLamont Granquist2021-05-142-8/+22
| | | | | | | This suppressses the unified_mode warning for any resources that have been deprecated via the chef_version_for_provides mechanism. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Bump version to 17.1.14 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Fix edit_resource usage in unified_modeLamont Granquist2021-05-143-12/+83
| | | | | | | | This makes edit_resource "atomic" so that in unified_mode the block is played against the resource being built before it is added to the resource collection and unified_mode fires the resource. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* fix mangled commentLamont Granquist2021-05-141-1/+1
| | | | Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Fix yum specsLamont Granquist2021-05-142-0/+2
| | | | | | | | | Reset the singleton instance before starting the test, because singletons. Also better clears up some internal state when the daemon gets reaped Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
* Remove pipeline-specific logic from test scriptsTom Duffield2021-05-142-68/+9
| | | | | | | This logic has been moved into the Omnibus Buildkite Plugin. These scripts can now be used outside of the Buildkite pipelines. Signed-off-by: Tom Duffield <github@tomduffield.com>
* Bump version to 17.1.13 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Fix bug causing systemd units to always re-enable and re-startGene Wood2021-05-142-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In #10925 the method of fetching the current systemd unit status was changed. In this change a typo was introduced which caused the systemctl command which should look like this `/usr/bin/systemctl --system show -p UnitFileState -p ActiveState apache2.service` to instead look like this `/usr/bin/systemctl --system show -p UnitFileState -p ActiveState apache2.service {}` The result is that instead of a response like this ``` ActiveState=active UnitFileState=enabled ``` Chef gets ``` ActiveState=active UnitFileState=enabled ActiveState=inactive UnitFileState= ``` which is the status of the service followed by the status of a bogus service called "{}" This results in Chef always thinking that systemd unit's are not active and not enabled and every Chef run attempts to enable and start the already enabled and started services. This is the same type of issue that was fixed in #11497 which applied to the systemd provider. That bug was introduced in #10776. This fixes the bug by expanding the splat with a preceding `**` Signed-off-by: Gene Wood <gene_wood@cementhorizon.com>
* Bump version to 17.1.12 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Bump chef/ohai to 00e12a5deb261ae20c330cb72fc2909ad3d20372Chef Expeditor2021-05-141-2/+2
| | | | | | This pull request was triggered automatically via Expeditor when 00e12a5deb261ae20c330cb72fc2909ad3d20372 was merged. This change falls under the obvious fix policy so no Developer Certificate of Origin (DCO) sign-off is required.
* Bump version to 17.1.11 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Add back windows deps to omnibusTim Smith2021-05-141-3/+82
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 17.1.10 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Make sure knife gemfile actually installs knifeTim Smith2021-05-141-0/+7
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Improve rake loggingTim Smith2021-05-141-0/+2
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Remove knife deps from the chef gemspecTim Smith2021-05-143-48/+8
| | | | | | This should help us slim the size of the install down and it should also greatly speed up testing anything that deps directly on chef. Signed-off-by: Tim Smith <tsmith@chef.io>
* Bump version to 17.1.9 by Chef ExpeditorChef Expeditor2021-05-148-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Fix systemd service state detectionLance Albertson2021-05-142-3/+3
| | | | | | | | Resolves #11496 This adds a missing double splat which is required when using Ruby 3.0. Signed-off-by: Lance Albertson <lance@osuosl.org>
* correcting the array one more timeJohn McCrae2021-05-031-1/+1
| | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
* correcting the array one more timeJohn McCrae2021-05-031-1/+1
| | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
* correcting one more missing comma problemJohn McCrae2021-05-031-1/+1
| | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
* correcting linting and related errorsJohn McCrae2021-05-032-5/+7
| | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
* Adding a Winget resource plus functional tests. Note there is NO uninstall ↵John McCrae2021-05-032-0/+337
| | | | | | for Winget. MS says this is too highly dependent on the app being installed. Signed-off-by: John McCrae <john.mccrae@progress.com>
* Bump version to 17.1.8 by Chef Expeditorv17.1.8Chef Expeditor2021-05-038-20/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #11503 from ↵Tim Smith2021-05-021-5/+5
|\ | | | | | | | | chef/expeditor/chef/ohai_947a97d47daa1dce6aa7b91f2057b15451805b25 Signed-off-by: Tim Smith <tsmith@chef.io>
| * Bump chef/ohai to 947a97d47daa1dce6aa7b91f2057b15451805b25Chef Expeditor2021-05-021-5/+5
|/ | | | | | This pull request was triggered automatically via Expeditor when 947a97d47daa1dce6aa7b91f2057b15451805b25 was merged. This change falls under the obvious fix policy so no Developer Certificate of Origin (DCO) sign-off is required.
* Bump version to 17.1.7 by Chef Expeditorv17.1.7Chef Expeditor2021-05-028-21/+21
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #11502 from chef/file_exists_directoryTim Smith2021-05-022-7/+7
|\ | | | | Signed-off-by: Tim Smith <tsmith@chef.io>
View Lorry Controller Status