Chef Infra
CI/CD pipelinechef
Chef Infra Server with pull-based client agents converging nodes from cookbooks.
- Provider
- default
- Kind
- CI/CD pipeline
- Category
- Operations
- Official docs
- https://docs.chef.io/platform_overview/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| approvalRequired | boolean | — | no | — | ▸ false |
| artifactSigning | boolean | — | no | — | inherited |
| clientIntervalSeconds | integer | — | no | 1800 | inherited |
| concurrency | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ false |
| runMode | enum | service | cron | on-demand | local-mode | no | service | inherited |
| secretsFromVault | boolean | — | no | — | ▸ false |
| secretsStore | enum | data-bag | chef-vault | external | no | data-bag | inherited |
| selfHostedRunners | boolean | — | no | — | ▸ true |
| trigger | enum | manual | commit | pull-request | schedule | no | — | ▸ schedule |
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.
nodes:
- { id: "chef", component: "chef" }Alibaba Cloud DevOps Flowalibaba-devops-flowAWS CodeBuildaws-codebuildAmazon CodeCatalystaws-codecatalystAWS CodeDeployaws-codedeployAWS CodePipelineaws-codepipelineEC2 Image Builderaws-ec2-image-builderAWS Protonaws-protonAWS Telco Network Builder (TNB)aws-tnbAzure Deployment Environmentsazure-deployment-environmentsManaged DevOps Poolsazure-managed-devops-poolsAzure Operator Service Managerazure-operator-service-managerAzure Pipelinesazure-pipelinesAzure VM Image Builderazure-vm-image-builderArgo CDargo-cdAtlantisatlantisAutomation pipelineautomation-pipelineAnsible AWXawxAtlassian BamboobambooBuildkitebuildkiteGeneric CI/CD pipelineci-pipelineCircleCIcircleciConcourseconcourseCrossplanecrossplaneDeepEvaldeepevalDronedroneFluxfluxGitHub Actionsgithub-actionsGitLab CI/CDgitlab-ciHCP Terraformhcp-terraformJenkinsjenkinsPipeCDpipecdpromptfoopromptfooPuppet EnterprisepuppetSalt ProjectsaltSpinnakerspinnakerJetBrains TeamCityteamcityTektontektonTravis CItravis-ciWoodpecker CIwoodpeckerZuulzuul-ci
and 16 more → CI/CD pipeline page# 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"