| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Intel coming at a future date.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tom Duffield <github@tomduffield.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
We need to make sure we create pr release branches. Right now the
chef-16 one gets the branch and then the master one uses that same
branch and the PR is busted.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Collin McNeese <cmcneese@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Collin McNeese <cmcneese@chef.io>
|
| |
| |
| |
| |
| |
| | |
This doesn't work
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| |
| | |
Avoid the EL7 package name that causes issues with some security
scanners
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
It's a 5 meg gem on windows and it serves very little value.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |\
| | |
| | | |
Remove Chef Sugar from CI testing matrix
|
| | |
| | |
| | |
| | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |/
| |
| |
| |
| |
| | |
We don't have one anymore
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
This reverts commit bb6e6b530e6668fa5c689abbf49e2bcc4c372e90.
|
| |
| |
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
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>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Test this on GH Actions
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |/
| |
| |
| | |
Signed-off-by: Bryan McLellan <btm@loftninjas.org>
|
| |
| |
| |
| |
| |
| |
| | |
Ubuntu Pro has FIPS modules. We should enable FIPS builds here since
we're already held to legacy OpenSSL on Linux as is.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This moves knife into /knife, in the same way that chef-utils and
chef-config are separated.
NOTES:
== File History ==
If you see this message as the first message in the history of
an knife file, you can see the complete history by using
'git log --follow', 'git config log.follow true' to make it the default
behavior in this repository, or 'git config --globa log.follow true' to
make it the global default.
== API Changes ==
At the API level, there is one breaking change:
CookbookSiteStreamingUploader has been moved out of chef and into
knife/core.
There were a combination of reasons we chose this path:
- CookbookSiteStreamingUploader (CSSU) is only used within Knife.
- CookbookSiteStreamingUploader (CSSU) references the
command Chef::Knife::CookbookMetadata in order to generate
a metadata file for the cookbook to upload
- Chef::Knife::CookbookMetadata is no longer available to Chef:: because
Knife has been moved to its own gem. Knife gem depends on the Chef gem,
so Chef can't depend on something in Knife.
A search for usage in related projects (berks, chef-cli) and the
Internet at large shows that there are no known external consumers of CSSU.
For now, we'll move this class into Knife::Core, as it's going to be
faster than splitting off the metadata generation and time is a concern. If we
find that we need the metadata generation in chef/ proper, we should evaluate
decoupling that functionality from Knife::CookbookMetadata and exposing
it via something like `Chef::Cookbook::Metadata#from_cookbook_files`
== spec changes ==
The specs are kept in their existing locations, though we have
separated out a `knife_spec_helper` so that we can ensure knife is not
directly accessing chef requires; and chef is relying on knife's at all.
We also now clear gem paths with each test, to force gem state to reset.
This works around a problem where a combination of tests
is corrupting the internal Gem state, causing failures in
rubygems_spec. See branch `mp/broken-gems` for many more details around
findings so far.
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Mostly this is all fixes necessary for ruby 3.0
There's the addition of the appbundle hook which lets us better pull
git gems into appbundler
Note carefully how after adding the post-bundle-install.rb that
trying to pre appbundle-update ohai pulls in chef/chef as bundle
installed git gem which fails to install so we go back to only
using one appbundle-update on chef/chef and removing the chef/ohai
one (which may fix other bugs).
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The more I hacked on the previous script the more I realized they're not
doing the same thing. This script is not concerned with things that
happened via rubygems promotes. It's just running bundle update when a
new commit is available in the repo.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tom Duffield <tom@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| | |
Automate more of our boring dep bumps
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| |
| | |
We need to know the dep we're updating throughout this script and if
it's not a gem we don't know the name. Allow passing in the name via arg
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
Avoid needing to manually cut these PRs
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
Avoid the need to manually create PRs when a PR is merged to Ohai
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 support N-2 macOS releases so 10.13 can be dropped now that Big Sur
is out.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
RHEL 6 is EOL. Stop shipping these packages
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| |
| | |
Since the world deps on these we really need a longer Ruby lifecycle
here
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
Ohai requires Ruby 2.7+ now
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Christopher A. Snapp <csnapp@chef.io>
|
| |
| |
| |
| |
| |
| | |
Add another subscription
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
This should reduce the number of hand created PRs to update the Gemfile.lock.
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>
|
| |
| |
| |
| |
| |
| | |
This is already there. Don't waste time.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
It's an alias, but avoid the confusion
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|