chef /chef
Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across any environment, at any scale
★ 8,268⑂ 2,520👁 347⑃ 12,646● 3,797▤ 4
8,268
stars
2,520
forks
347
watchers
12,646
prs
3,797
issues
4
releases
README
Chef Infra
Umbrella Project: Chef Infra
Project State: Active
Issues Response Time Maximum: 14 days
Pull Request Response Time Maximum: 14 days
Getting Started
Chef Infra is a configuration management tool designed to bring automation to your entire infrastructure.
Want to try Chef Infra?
For Chef Infra usage, please refer to Learn Chef, our self-paced, entirely free learning platform. Learn Chef also includes module-based training for Chef Infra, as well as Chef Automate, Chef Habitat, and Chef InSpec.
Other useful resources for Chef Infra users:
- Documentation:
- Source:
- Tickets/Issues:
- Slack: Chef Community Slack
- Mailing list/Forum:
Reporting Issues
Issues can be reported by using GitHub Issues.
Note that this repository is primarily for reporting issues in the chef-client itself. For reporting issues against other Chef projects, please look up the appropriate repository. If you're unsure where to submit an issue, please ask in the chef-dev channel in Chef Community Slack.
How We Build & Release Chef
For information on how a contribution goes from PR to released package, see How Chef Infra Is Built
To learn more about our monthly feature releases and yearly major releases, see Chef Infra Release and Support Schedule.
Getting Involved
We'd love to have your help developing Chef Infra. See our Contributing Document for more information on getting started.
Community PR Reviews
Want to raise, review, and help merge a PR with the community and the engineering staff? Please see: Community Pr Review
License
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Copyright
See COPYRIGHT.md.Top issues
#7765Powershell Add-AppxPackage not working for standard user (only admin)17 comments · 2018-10-23#9220Have dnf_package support modular/appstream installs13 comments · 2020-01-15#12993User resource user.rb crashes with `Segmentation fault` when using GCP VM with OSLogin Enabled.12 comments · 2022-06-14#14034Omnitruck artifact does not exist for Rocky Linux11 comments · 2023-10-19#10455`windows_user` resource requires plaintext passwords10 comments · 2020-09-22#10079Add new 'systemd_timesyncd' resource10 comments · 2020-06-29#9175Directory resource should remove files and replace with a directory9 comments · 2019-12-18#4599`file` resource's `inspect_existing_fs_entry` prevents managing permissions on char/dev files9 comments · 2016-02-18
Discussions
#15663`include_recipe` inside a custom resource0 comments · 2026-02-23#14878How to deal with concurrent tests?0 comments · 2025-03-05#14778Support environment specific attributes in Roles0 comments · 2025-01-03#14286Chef 17.10.3 RPM packages that supports RHEL7 and RHEL81 comments · 2024-03-15#13381Node Self-Tagging Deprecation1 comments · 2022-11-22#13189Is Chef still under Apache License 2.0?1 comments · 2022-09-16
Latest release
Chef Infra Client 15.8.23 v15.8.23 2020-02-20New notify\_group functionality Chef Infra Client now includes a new notify_group feature that can be used to extract multiple common notifies out of individual resources to reduce duplicate code in your cookbooks and custom resources. Previously cookbook authors would often use a log resource to achieve a similar outcome, but using the log resource results in unnecessary Chef Infra Client log output. The notify_group method produces no additional logging, but fires all defined notifications when the :run action is set. Example notify\_group that stops, sleeps, and then starts service when a