classicvalues / automate

Chef Automate provides a full suite of enterprise capabilities for maintaining continuous visibility into application, infrastructure, and security automation.

Automate

Automate provides a unified view into infrastructure managed by Chef, Inspec, and Habitat.

Key features include:

• Aggregation and analysis tools for Chef Client and Chef Server data,
• Compliance history and reporting, and
• Compliance scanning of both individual servers and cloud APIs.

For more information see:

• Documentation: https://docs.chef.io/automate/
• Release Notes: https://docs.chef.io/release_notes_automate/

Project State: Active

Issues Response Time Maximum: 5 business days

Pull Request Response Time Maximum: 5 business days

Components

Chef Automate is a collection of microservices. Each service is developed independently.

Core Applications

• Automate UI
• Automate Gateway
• Config Management Service
• Compliance Service
• Event Service
• Ingest Service
• Nodemanager Service
• Notifications Service

Authentication, Authorization, & Administration

• AuthN Service
• AuthZ Service
• Automate-Load-Balancer
• Dex (OpenID Connect)
• Local User Service
• Teams Service
• Session Service

Management and Backend Services

• Backup Gateway
• Data Lifecycle Service
• Deployment Service
• Elasticsearch Gateway
• Elasticsearch Sidecar
• License Control Service
• PostgreSQL Gateway
• PostgreSQL Sidecar
• Secrets Service
• Trial License Service

Optional Additional Components

These components allow you to deploy other Chef projects as part of Automate

• Chef Server
  • Bifrost
  • Bookshelf
  • Chef Server Gateway
  • Erchef

Getting Started

Please see Quickstart and Development Basics in the development document.

Architecture

The following picture illustrates the Automate 2.0 architecture

API Compatibility

At this stage in development, the Go libraries and other APIs found in this repository are not intended for use outside of Chef Automate. If you think part of this repository would help and would like to depend on it, please open a GitHub issue so we can discuss it.