This file is used to list changes made in each version of the chef-ingredient cookbook.
- Added attribute to specify mixlib-install version, defaults to nil to install latest version - @stromweld
- Fixed automatev2 resource guard and made it idempotent - @stromweld
- Fixed automatev2 resource to work with debian and rhel family bin locations - @stromweld
- Updated testing and switched to Github actions for CI pipeline - @stromweld
- Enable
unified_mode
for Chef 17 compatibility - @detjensrobert - Add deprecations to the automate, chef_client and wf_builder resources - @tas50
- Add rubygems_url property to chef_ingredient - @ramereth
- Add rubygems_url property to ingredient_config - @ramereth
- Add rubygems_url property to omnibus_service - @ramereth
- Cookstyle Bot Auto Corrections with Cookstyle 6.15.9 - @cookstyle
- Cookstyle 7.0.0 Fixes - @xorimabot
- Change from testing ChefDK to Chef Workstation in dokken - @ramereth
- resolved cookstyle error: resources/client.rb:156:49 convention:
Style/RedundantParentheses
- adding a products property to the automatev2 resource - @srb3
- Ensure we have resource_name in addition to provides in resources - @tas50
- Added provides to resources to add Chef Infra Client 16 compatability - @Stromweld
- Remove unnecessary Foodcritic comments - @tas50
- Resolve ChefSpec deprecation warnings - @tas50
- Make Chef Infra Server honor license acceptance. Pulled this in from #241 - @bkonick
- correct automate path - @dheerajd-msys
- move reconfigure_command to a method in action_class - @bkonick
- Cookstyle 6.2.9 Fixes - @xorimabot
- Update platforms we test on - @tas50
- Cookstyle Fixes including Chef Infra Client 16 compatibility - @xorimabot
- resolved cookstyle error: resources/chef_ingredient.rb:19:1 warning:
ChefDeprecations/ResourceUsesOnlyResourceName
- resolved cookstyle error: resources/ingredient_config.rb:18:1 warning:
ChefDeprecations/ResourceUsesOnlyResourceName
- resolved cookstyle error: resources/omnibus_service.rb:18:1 warning:
ChefDeprecations/ResourceUsesOnlyResourceName
- resolved cookstyle error: resources/backend.rb:28:45 refactor:
ChefCorrectness/LazyEvalNodeAttributeDefaults
- resolved cookstyle error: resources/chef_org.rb:31:36 refactor:
ChefModernize/ShellOutHelper
- resolved cookstyle error: resources/chef_org.rb:32:35 refactor:
ChefModernize/ShellOutHelper
- resolved cookstyle error: resources/chef_user.rb:32:36 refactor:
ChefModernize/ShellOutHelper
- resolved cookstyle error: resources/wf_builder.rb:260:9 refactor:
ChefModernize/ShellOutHelper
- resolved cookstyle error: resources/wf_builder.rb:274:18 refactor:
ChefModernize/ShellOutHelper
- resolved cookstyle error: spec/unit/recipes/test_default_handler_spec.rb:20:7 warning:
ChefDeprecations/DeprecatedChefSpecPlatform
- resolved cookstyle error: libraries/helpers.rb:254:11 refactor:
ChefCorrectness/ChefApplicationFatal
- resolved cookstyle error: resources/automatev2.rb:48:5 refactor:
ChefCorrectness/ConditionalRubyShellout
- resolved cookstyle error: resources/wf_builder.rb:207:11 refactor:
ChefStyle/UsePlatformHelpers
- resolved cookstyle error: resources/wf_builder.rb:210:11 refactor:
ChefStyle/UsePlatformHelpers
- resolved cookstyle error: resources/chef_ingredient.rb:19:1 warning:
- Fix user idempotency (#238) - @Stromweld
- Add a new automatev2 resource (requires Chef 14+) (#237) - @Stromweld
- Require Chef 13+ and remove Ubuntu 14.04 testing
- Rrevert chef_org user/admin guards (PR#223) (#233)
- Remove default action, which isn't necessary in Chef 12.5+ (#232)
- Pass sensitive & add guard to chef_user ruby_block (#231)
- Create client.d directory for
chef_client
resource - Fix
chef_org
guards for adding users and admins
- Resolve multiple incompatibilities with Chef 14
- Multiple fixes for Automate and Workflow Builder resources.
- Fix permissions on chef-backend-secrets.json and provide new properties for modifying the permissions
- Remove Chefspec matchers that are no longer necessary
- Resolve chef_org full name truncation issue (#215)
- Resolve multiple issues with the custom resources in various Chef 12 releases by requiring Chef 12.7 or later and removing the usage of class_eval on the action_classes
- Restored compatibility with Amazon Linux on Chef 13 and added testing
- Removed unnecessary default_actions in the custom custom resources
- Resolved FC108 warnings by removing redundant :name name_properties from the custom resources
- Fixed pathing for etc and .chef directories for dbuild in wf_builder
- Required for chef_server cookbook (#202)
- Multiple fixes for Automate and Workflow Builder resources
- Honor sensitive property when set on high level resources
- Fix chef_server resource to run without configured addons
- Fix permissions on automate keys and license.
- Fix remove_users to use new_resource instead of current_resource.
- fix chef_org resource deprecation warnings
- RHEL 5 and 6 package manager support (RHEL 5 is not officially supported)
- Update the client resource to properly source the client.rb template
- Add a log warning if the default recipe is included on a run_list
- Added supported platforms to the metadata for Supermarket
- Use default package provider on RHEL instead of RPM; fixes #181
- Resolve CHEF-19 deprecation warnings (#184)
- Pin mixlib-install
~> 3.3
- Fix normalization of auto-detected and set architectures
- Revert platform remapping and platform version truncation changes.
chef_ingredient
propertiesplatform
,platform_version
,architecture
default to auto-detected value when not set.
- Add initial chef infrastructure resources and contributors from chef_stack project
- Add Ohai attributes as defaults to
chef_ingredient
resource propertiesplatform
,platform_version
, andarchitecture
- Add platform remapping and platform version truncation fixes to align with Chef Software Inc's software distribution systems
- #155 Workaround chef_ingredient timeout property on Windows (windows_package timeout property currently broken in Chef)
- #158 Remove #check_deprecated_properties logic (handled by mixlib-install)
- Allow chef_ingredient action :upgrade on Windows
- Ensure mixlib-install
~> 3.2
is installed
- Normalize architectures detected by ohai before mixlib-install validation
- Update resources to support Chef 12.5 and 12.6
- Update DefaultHandler and OmnitruckHandler to use a global constant lookup. In some environments, not doing so caused a naming conflict with the dynamically generated ChefIngredient DSL resource class.
- Remove
chef_server_ingredient
resource shim - Update mixlib-install to major version 3
platform_version_compatibility_mode
property no longer has a default value- If no matching artifacts are found a
Mixlib::Install::Backend::ArtifactsNotFound
exception is raised instead aRuntimeError
- All resources have been converted to custom resources
- Test with local delivery and not Rake
- Remove sensitive property for Chef 13 compatibility as this properly is provided by chef-client now for us by any resource and doesn't need to be defined
- Test in Travis CI with kitchen-dokken and convert tests to InSpec
- Testing cleanup for Chef 13 compatibility and testing on the latest platforms
- Require Chef 12.5+ and remove compat_resource dependency
- Use mixlib-install >= 2.1.12 - this brings in an important fix for the
delivery
->automate
package rename. See the Discourse announcement for details on the rename
- Add properties to override the platform details of a
chef_ingredient
product to install
- Add timeout to package resource created by configure_from_source_package
- Fix issue when failed package installs using OmnitruckHandler would not raise a converge error on subsequent runs
- Update SUSE platform to use DefaultHandler
- Update mixlib-install to version 2.0 (PackageRouter support)
- Remove extraneous converge_by that caused downloads to show as converged on every run
- Use compat_resource cookbook to add support for Chef 12.1-12.4
- Use apt_update resource vs. the apt cookbook in the test cookbook
- Update Travis CI testing to use our standard Rakefile and cookstyle for ruby linting.
- Fix chefspec / foodcritic / test kitchen failures
- Swap the Policyfile for a Berksfile
- Remove unnecessary action and default_action properties from the custom resources
- Remove delivery-cli examples and tests (we now shipit with ChefDK)
- Set version constraint to ~> 1.1 for installing mixlib-install from Rubygems
- Add
platform_version_compatibility_mode
property tochef_ingredient
which makes chef-ingredient select packages built for earlier version of a platform during install when a package does not exist for the current platform version.
- Add
accept_license
property tochef_ingredient
which can accept license for Chef products when applicable.
- Set version constraint to ~> 1.0 for installing mixlib-install from Rubygems
- Bump mixlib-install version to 1.0.6 so unstable channel artifacts won't include metadata.json files.
- #85 Ability to support unstable channel for all products / platforms.
- #90 Use packages from packages.chef.io instead of package cloud & remove packagecloud repository setup.
- #91 Deprecate chef-ha, chef-marketplace, chef-sync, push-client, push-server in favor of ha, marketplace, sync, push-jobs-client, push-jobs-server.
- #77 Enable installation of chef and chefdk from unstable
- #82 Set
--force-yes
for older Debian/Ubuntu
- #62 Do not assume connection to the internet, allow custom recipe for a local repository
- #75 omnitruck handler windows implementation
- #66 Fix push job client and server naming
- #68 Use mixlib-install while installing / upgrading packages from omnitruck
- #71 Convert
omnibus_service
andingredient_config
to "12.5 custom resources" - #73 Use PRODUCT_MATRIX from mixlib-install
- #58 Add Chef Compliance product
- #57 Content accumulator guard
- #56 Uncomment
use_inline_resources
, this is required for the providers to work properly - #55 Remove unit tests for specifically the custom resources
- #54 Clarify maintainer/support in the README
- #53 Relax version constraints
- Refactor
chef_ingredient
and prepare to handle install/upgrade from omnitruck - Add channel property to
chef_ingredient
- Removed installed state property
- Use
product_name
instead ofpackage_name
- Add not if to skip
ingredient_config
render ifconfig
property isn't used
- Remove
resource_name
from Provider because:facepalm:
- Add
repository
andmaster_token
properties tochef_server_ingredient
shim for compatibility
- #37 use
define_matchers
for ChefSpec
- #35 Add
fqdn_resolves?
method forchef-server
cookbook.
- Add
:add
action toingredient_config
- #30 Supermarket doesn't use supermarket.rb for configuration, it's supermarket.json
- #26 Remove mode, owner, and group properties from
ingredient_config
's resources to prevent resource updates after running ctl commands that manage those file permissions.
- Add sensitive property to
ingredient_config
- Use recipe DSL to set resource name
- Update PRODUCT_MATRIX.md with correct updated Chef Push product names (push-server, push-client). The code was updated but not the document.
- #7 Add
ingredient_config
resource - #10 Add upgrade action for
chef_ingredient
- Test cleanup, various rubocop fixes
- #3 Allow :latest as a version
- Removes the
package_name
property from thechef_ingredient
resource, long liveproduct_name
Breaking changes This version is backwards-incompatible with previous versions. We're still sub-1.0, but those who wish to use the chef_server_ingredient
resource really should pin to version 0.5.0.
- #1 Use product names instead of package names.
- Major refactor and rename. It's fine, this is a new cookbook!
- Add timeout attribute to
chef_server_ingredient
- Use
declare_resource
DSL method to select local package resource - Allow specifying the repository name for the packagecloud repo
- adding proxy support for packagecloud
- Various refactoring and cleanup
- Add ctl command for supermarket
- Add reconfigure property to ingredient resource
- Release this cookbook to Supermarket
- #4: define the installed attribute
- #1, #2, use packagecloud cookbook
- Initial release