“Continuous configuration automation tools (aka infrastructure as code) are foundational to DevOps initiatives.”
Recipe for faster app delivery:
BUILD AND MANAGE
Model common and customizable automated deployment patterns.
PACKAGE: Create reusable building blocks that can be used in multiple stacks
CONFIGURE: Automatically ensure the code you’ve written matches the state of the infrastructure you’re managing.
TEST: Automatically test that your systems remain in compliance.
Quickly test your production-bound change to applications and infrastructure.
LOCAL DEVELOPMENT: Developers can validate their code on non-critical systems with fast feedback loops to catch issues earlier.
INTEGRATION: Ensure changes are tested against downstream dependencies to prevent unforeseen failures in production.
APPROVE WITH WORKFLOW: A common workflow ensures all change is tested and approved with the same rigor and speed. Chef Automate ensures changes are only deployed once properly approved.
Automatically test, review, build, and deploy those changes on commit.
CHEF AUTOMATE: Build automated pipelines to enable continuous delivery
How to do it:
MANAGE AND AUDIT
Visibility is key. Audit systems to determine which specific systems are vulnerable.
SCAN: Routinely and automatically scan for known vulnerabilities.
MANAGE: Automatically ensure the exact configuration of your systems at any scale.
AUDIT: Detect and report versions of installed shells on systems--even when they are not actively being managed.
Automatically apply that remediations programmatically.
LOCAL DEVELOPMENT: Developers can test their code on non-critical systems with fast feedback loops
TEST AND BUILD: Write and bundle tests to ensure the remediation works as expected every time. Test dependencies automatically.
APPROVE WITH WORKFLOW: Chef Automate ensures changes are only deployed once properly approved. All change is tested and approved before being automatically deployed.
Once remediation procedure is verified, it can be released to patch all running systems
DEPLOY: Systems automatically pick up the change on their next run.