Use the git resource to manage source control resources that exist in a git repository. A git resource block manages source control resources that exist in a git repository:. The full syntax for all of the properties that are available to the git resource is:.
Do a one-time checkout from git or use when a branch in the upstream repository is named deploy. See revision. The number of past revisions to be included in the git shallow clone. Unless specified the default behavior will do a full clone. The location path to which the source is to be cloned, checked out, or exported. Default value: the name of the resource block. Check out a repo from master. These variables must exist for a command to be run successfully.
A branch, tag, or commit to be synchronized with git. This can be symbolic, like HEAD or it can be a source control management-specific revision identifier. The value of the revision attribute may change over time. From one branch to another, to a tag, to a specific SHA for a commit, and then back to a branch.
The revision attribute may even be changed in a way where history gets rewritten. Instead of tracking a specific branch or doing a headless checkout, Chef Infra Client maintains its own branch via the git resource that does not exist in the upstream repository. Chef Infra Client is then free to forcibly check out this branch to any commit without destroying the local history of an existing branch.
Use the git rev-parse and git ls-remote commands to verify that Chef Infra Client is synchronizing commits correctly. Could not load branches. Could not load tags. Latest commit. Bump version to Git stats 31, commits. Failed to load latest commit information. Aug 24, Sep 27, Oct 26, Mar 31, Nov 19, Nov 3, Add Yaml verifier.
Sep 13, Sep 15, Update the Effortless package for Windows to Ruby 3. Apr 27, Nov 16, Nov 17, Oct 27, May 17, Jul 27, Remove the manpages. Mar 11, Update linting and gitignore for knife rspec changes. Apr 30, Add mailmap entries for Tim Smith. Additional information is available in this announcement. Supported Versions.
Chef continues to provide releases to the application or version in response to customer needs and security vulnerabilities Chef welcomes customer feature requests for the product roadmap for the application Deprecated This stage indicates that an application or version is no longer in active development and will eventually move to end of life status.
Chef no longer provides scheduled releases Customers should use the GA alternative to these products; contact us for help with product selection and deployment Chef may provide a release for a critical defect or security vulnerability End of Life EOL This stage indicates that Chef has set a date after which the application or version will no longer be supported or recommended for use by customers. Note Chef Backend does not directly require acceptance of the Chef EULA, but it does have functionality that requires its acceptance in other products.
0コメント