syncing from original #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Obvious fix; these changes are the result of automation not creative thinking.
This pull request was triggered automatically via Expeditor when train-core 2.1.13 was promoted to Rubygems. This change falls under the obvious fix policy so no Developer Certificate of Origin (DCO) sign-off is required.
Bump train-core to 2.1.13
Obvious fix; these changes are the result of automation not creative thinking.
Add the release notes for Chef 15.1 Signed-off-by: Tim Smith <tsmith@chef.io>
The majority of this work actually happened in 15.0 Signed-off-by: Tim Smith <tsmith@chef.io>
Signed-off-by: Tim Smith <tsmith@chef.io> Co-Authored-By: mjingle <mjingle@users.noreply.github.com>
Signed-off-by: Tim Smith <tsmith@chef.io> Co-Authored-By: mjingle <mjingle@users.noreply.github.com>
Signed-off-by: Tim Smith <tsmith@chef.io> Co-Authored-By: mjingle <mjingle@users.noreply.github.com>
Signed-off-by: Tim Smith <tsmith@chef.io> Co-Authored-By: mjingle <mjingle@users.noreply.github.com>
Signed-off-by: Tim Smith <tsmith@chef.io> Co-Authored-By: mjingle <mjingle@users.noreply.github.com>
Signed-off-by: Tim Smith <tsmith@chef.io> Co-Authored-By: mjingle <mjingle@users.noreply.github.com>
Signed-off-by: Tim Smith <tsmith@chef.io> Co-Authored-By: mjingle <mjingle@users.noreply.github.com>
Signed-off-by: Tim Smith <tsmith@chef.io> Co-Authored-By: mjingle <mjingle@users.noreply.github.com>
Some of it was in 15.0 and some in 15.1 and it's tricky to call out the impact and the exact time that stuff landed so let's skip it Signed-off-by: Tim Smith <tsmith@chef.io>
Add Chef 15.1 release notes
…tom_repo Pass yum_package options to underlying python helper
Obvious fix; these changes are the result of automation not creative thinking.
** isn't what we wanted here Signed-off-by: Tim Smith <tsmith@chef.io>
Obvious fix; these changes are the result of automation not creative thinking.
This pull request was triggered automatically via Expeditor when inspec-core 4.6.9 was promoted to Rubygems. This change falls under the obvious fix policy so no Developer Certificate of Origin (DCO) sign-off is required.
Bump inspec-core to 4.6.9
Obvious fix; these changes are the result of automation not creative thinking.
This should fix package promotion from unstable->current in expeditor, too. Signed-off-by: Robb Kidd <robb@thekidds.org>
Obvious fix; these changes are the result of automation not creative thinking.
update bldr config with new hab package name
Obvious fix; these changes are the result of automation not creative thinking.
result of automation chef/chefstyle#72 Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
fixes for chefstyle bump
Obvious fix; these changes are the result of automation not creative thinking.
Don't link to a boneyard repo anymore Signed-off-by: Tim Smith <tsmith@chef.io>
Update the link to our release cadence information
Obvious fix; these changes are the result of automation not creative thinking.
This is inspired by "use_inline_resources". Setting `unified_mode false` in a resource would be the existing behavior with separate compile/converge phases. Setting `unified_mode true` in a resource will eliminate the converge phase. Reverse notifications and delayed notifications will still fire. The resource action will behave like all resources are executing at compile time. As a aside, notifications have never worked for resources firing at compile time. This implementation gets that behavior correct so that notifications will work. Of course forward immediate notifications to resources not yet declared will not be possible. Setting `resource_unified_mode_default true` in `Chef::Config` would turn off the split compile/converge mode for every custom resource. NOTE: This does not affect recipe mode at all. Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
Signed-off-by: Jeremiah Snapp <jeremiah@chef.io>
Stop building Chef Infra Client on FreeBSD 10
- Added file in banner Signed-off-by: Amol Shinde <amol.shinde@msystechnologies.com>
…data_from_file_fix Updated knife cookbook metadata from file command banner
Obvious fix; these changes are the result of automation not creative thinking.
Signed-off-by: Seth Chisamore <schisamo@chef.io>
Begin signing MSI's with renewed Windows Signing Cert
Obvious fix; these changes are the result of automation not creative thinking.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
Pull in the latest omnibus and omnibus-software updates. Signed-off-by: Tim Smith <tsmith@chef.io>
Update omnibus build deps to the latest
Obvious fix; these changes are the result of automation not creative thinking.
Add unified_mode for resources
Obvious fix; these changes are the result of automation not creative thinking.
Before:
/opt/chefdk/embedded/lib/ruby/gems/2.6.0/gems/chef-config-15.1.36/lib/chef-config/mixin/credentials.rb:92:in `load_credentials': undefined local variable or method `credentials_file' for #<ChefConfig::WorkstationConfigLoader:0x00007fe01c8321e8> (NameError)
After:
ERROR: CONFIGURATION ERROR:Profile xyz doesn't exist. Please add it to /Users/developer/.chef/credentials.
It looks like this was missed as part of the refactoring in
d730505.
Signed-off-by: Andrew Neitsch <andrew@neitsch.ca>
Signed-off-by: Jaymala Sinha <jsinha@chef.io>
Fix crash when showing error about missing profile
Obvious fix; these changes are the result of automation not creative thinking.
Add AIX 7.2 platform
Obvious fix; these changes are the result of automation not creative thinking.
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
We need to support the prefixed `EXPEDITOR_` build arguments in our Dockerfile. We are leaving the non-prefixed arguments in there for back-compat. Signed-off-by: Tom Duffield <tom@chef.io>
Fix the build arguments in the Dockerfile
…config_bridge_interface ifconfig: fix regex matching interface name with hyphen
Obvious fix; these changes are the result of automation not creative thinking.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
[Please describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussion that's relevant]
Check List