| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Ubuntu 16.04 goes EOL at the end of April. Stop producing packages for
this release.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\
| |
| | |
Fix users_manage usage in kitchen-tests
|
| |
| |
| |
| |
| |
| |
| | |
There seems to be an issue with the users cookbook on Windows that needs to be
addressed. Comment this test out for now until it can be fixed.
Signed-off-by: Lance Albertson <lance@osuosl.org>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is currently using `my_awesome_password` which is the same example used in
the users resource. This was made by running `mkpasswd -m sha-512` on a linux
system.
Signed-off-by: Lance Albertson <lance@osuosl.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The use of data bags in the users cookbook was removed in 6.0.0 [1]. This
applies the recommended workaround and allow the integration tests to pass.
[1] https://github.com/sous-chefs/users/blob/master/CHANGELOG.md#600---2021-03-12
Signed-off-by: Lance Albertson <lance@osuosl.org>
|
| |
| |
| |
| |
| |
| | |
Oracle 8 docker image no longer ships with yum
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
|
|
| |
Get the builds green again
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
| |
Recently, the Sous Chefs released a new resource driven resolver cookbook and
removed the default recipe, thus breaking tests. This should fix the tests
related to this.
Signed-off-by: Lance Albertson <lance@osuosl.org>
|
|
|
|
|
|
| |
used LocalMachine. Updated Gemlock to use win32-cerstore 0.5.3 (#10977)
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|/
|
|
|
|
| |
Also add a CI test for installing a small cask
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This release is not out yet, but we have containers for it now.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
| |
These containers are alpha/beta quality, but we should start testing on
this since it'll be out when Chef Infra 17 is released.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
| |
The version of ld on Amazon Linux 201x cannot handle the ffi gem so these tests are going to fail forever now. This is a RHEL 6 based distro that is EOL as of the end of 2020.
https://aws.amazon.com/blogs/aws/update-on-amazon-linux-ami-end-of-life/
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
These are the terrible things you get to do to support an EOL platform.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Point the new chef-16 branch at 16-stable ohai branch
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Get the correct format here
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This resource only works with the legacy redhat /etc/networks configuration format. That format was slapped onto NetworkManager when RHEL moved off legacy init scripts. Fedora 33 switches to the keyfile format so this resource no longer works on those systems. Stop testing it there and add a note to the resource description so we get that up on the docs site.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
| |
We can bump this up to the latest non-LTS release every 6 months to
determine if there's any resource updates we need to make in advance of
the LTS release.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This is in the dokken image now.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
We lacked an actual test of this resource. Let's see if it works.
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>
|
|
|
|
|
|
| |
2.0 is out with Ruby 2.7 support
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Initial stab at a chef_client_config resource that will allow people to easily write out a client.rb. This isn't meant to cover every single use case, but instead to provide a simple resource that works for 99% of users.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Davin Taddeo <davin@chef.io>
|
|
|
|
| |
Signed-off-by: Davin Taddeo <davin@chef.io>
|
|
|
|
|
|
| |
the windows end-to-end kitchen testing.
Signed-off-by: Davin Taddeo <davin@chef.io>
|
|
|
|
|
|
| |
sort through. And a chefstyle fix
Signed-off-by: Davin Taddeo <davin@chef.io>
|
|
|
|
| |
assist with issue #10420
|
|
|
|
|
|
| |
method out of the action_class. Also add some firewall tests to the kitchen tests to avoid this issue in the future.
Signed-off-by: Davin Taddeo <davin@chef.io>
|
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
Co-authored-by: pete higgins <pete@peterhiggins.org>
|
|
|
|
|
|
|
|
| |
chef-client unit
This allows us to set a quota like 50% on everything handled by the chef-client including all the sub-processes like ohai or inspec. I looked at using systemd's nice functionality since that would give us a unified property for all the *nix processes, but that only applies to the chef-client process itself. This is much more powerful and gives users what user's probably really want which is "chef and all its stuff should not consume all the CPU on my host".
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
| |
Added permalink for Regex.
Renamed the linux_mount recipe file to mount in kitechen-tests.
Signed-off-by: antima-gupta <agupta@msystechnologies.com>
|
|
|
|
|
|
|
|
| |
Added a separate linux mount provider.
Define 'mounted?' method and used 'findmnt -rn' command to list mount points along with device.
Added linux_mount recipe to kitchen-tests.
Signed-off-by: antima-gupta <agupta@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
| |
This is a pretty simple resource for something that users can certainly do on their own right now, but most people don't even realize is an option. Giving it a dedicated resource exposes the functionality better and just makes it that much easier to write a simple cross platform cookbook that involves configuring the client.
I'm not a huge fan of having to provide the certificate as a string, but I didn't want to add yet another place where we allow string values, or URI. They all have slightly different APIs and we need to just do it via a mixin or something. This can certainly move that direction in the future, but for this solves a real problem today.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This way we get a proper state change instead of just showing a converge. This also removes awk/grep in not_if statements and overall improves logging.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Make sure we can execute the resource in a Test Kitchen run.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Get the actual systemd action right. Add a kitchen test for this as well.
Signed-off-by: Tim Smith <tsmith@chef.io>
|