chef / effortless

Automated best practices for Chef Infra and Chef InSpec
https://chef.io
Apache License 2.0
33 stars 38 forks source link

Effortless

Build status

Project State: Active

Issues Response Time Maximum: 14 days

Pull Request Response Time Maximum: 14 days

Effortless is pattern to better manage Chef and Chef InSpec workloads using Chef Habitat.

Quick Links

Existing Users

If you're already familiar with the Chef stack, here's a quick rundown of how Effortless works.

  1. Effortless uses a build process to pull down all your cookbooks or profiles. The build creates a single, deployable package. For Chef Infra, it contains your cookbooks, an up-to-date Chef Infra client, and the latest best practices. For Chef InSpec, it contains your profiles, an up-to-date Chef InSpec client, and the latest best practices.

  2. At runtime, Chef Infra works without Chef Infra Server. It uses Chef Solo mode.

  3. At runtime, Chef InSpec works without pulling profiles from Chef Automate. All profiles, including those from Chef Automate, are vendored at build time.

  4. Chef Habitat manages Chef Infra and Chef InSpec, and provides a pull-based update strategy for continuous delivery.

  5. This workflow is a replacement for the environment and role cookbook patterns or Berkshelf way.

Image of the Effortless pattern

Next Steps

If you are new to the Effortless pattern checkout some of the below examples and walk throughs that will help you understand what you can do with this pattern.

Examples

  1. Effortless Audit
  2. Effortless Config