Chef Infra

Chef Infra Server with pull-based client agents converging nodes from cookbooks.

Provider
default
Category
Operations
Properties · 5 set by this component
propertytypevaluesrequiredkind defaultthis component
approvalRequiredboolean—no—▸ false
artifactSigningboolean—no—inherited
clientIntervalSeconds · component propertyinteger—no1800inherited
concurrencyinteger—no—inherited
managedboolean—nofalse▸ false
runMode · component propertyenumservice | cron | on-demand | local-modenoserviceinherited
secretsFromVaultboolean—no—▸ false
secretsStore · component propertyenumdata-bag | chef-vault | externalnodata-baginherited
selfHostedRunnersboolean—no—▸ true
triggerenummanual | commit | pull-request | scheduleno—▸ schedule
Rules that apply · 0

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

No rule reads this kind yet. That is a gap, not a guarantee.
Use it in a design
nodes:
  - { id: "chef", component: "chef" }
Other CI/CD pipeline products · 56
Alibaba Cloud DevOps Flowalibaba-devops-flowalibabacloudci-pipelineAWS CodeBuildaws-codebuildawsci-pipelineAmazon CodeCatalystaws-codecatalystawsci-pipelineAWS CodeDeployaws-codedeployawsci-pipelineAWS CodePipelineaws-codepipelineawsci-pipelineEC2 Image Builderaws-ec2-image-builderawsci-pipelineAWS Protonaws-protonawsci-pipelineAWS Telco Network Builder (TNB)aws-tnbawsci-pipelineAzure Deployment Environmentsazure-deployment-environmentsazureci-pipelineManaged DevOps Poolsazure-managed-devops-poolsazureci-pipelineAzure Operator Service Managerazure-operator-service-managerazureci-pipelineAzure Pipelinesazure-pipelinesazureci-pipelineAzure VM Image Builderazure-vm-image-builderazureci-pipelineArgo CDargo-cdci-pipelineAtlantisatlantisci-pipelineAutomation pipelineautomation-pipelineci-pipelineAnsible AWXawxci-pipelineAtlassian Bamboobambooci-pipelineBuildkitebuildkiteci-pipelineGeneric CI/CD pipelineci-pipelineci-pipelineCircleCIcirclecici-pipelineConcourseconcourseci-pipelineCrossplanecrossplaneci-pipelineDeepEvaldeepevalci-pipelineDronedroneci-pipelineFluxfluxci-pipelineGitHub Actionsgithub-actionsci-pipelineGitLab CI/CDgitlab-cici-pipelineHCP Terraformhcp-terraformci-pipelineJenkinsjenkinsci-pipelinePipeCDpipecdci-pipelinepromptfoopromptfooci-pipelinePuppet Enterprisepuppetci-pipelineSalt Projectsaltci-pipelineSpinnakerspinnakerci-pipelineJetBrains TeamCityteamcityci-pipelineTektontektonci-pipelineTravis CItravis-cici-pipelineWoodpecker CIwoodpeckerci-pipelineZuulzuul-cici-pipeline
and 16 more → CI/CD pipeline page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Chef Infra: self-hosted Chef Infra Server with Chef Infra Client agents on every node. The
# platform overview describes a pull model in which the agent, not the server, starts the run, and
# gives a 1800 second (30 minute) interval when the client runs as a background service; secrets
# are held in Chef Vault or in data bags rather than a vault the client reads at run time.
schemaVersion: "1"
type: "component"
id: "chef"
kind: "ci-pipeline"
provider: "default"
docs: "https://docs.chef.io/platform_overview/"
defaults:
  trigger: "schedule"
  approvalRequired: false
  selfHostedRunners: true
  secretsFromVault: false
  managed: false
properties:
  clientIntervalSeconds:
    type: "integer"
    default: 1800
  runMode:
    type: "enum"
    values: ["service", "cron", "on-demand", "local-mode"]
    default: "service"
  secretsStore:
    type: "enum"
    values: ["data-bag", "chef-vault", "external"]
    default: "data-bag"

The same page as markdown, for an agent: /catalogue/components/chef.md