-
Notifications
You must be signed in to change notification settings - Fork 3
chef server endpoint
Russell Seymour edited this page Nov 13, 2017
·
1 revision
An endpoint called 'Chef Server' is bundled with this extension. This allows multiple Chef servers to be configured and reused across tasks as required. Endpoints are a per-project configuration and can be accessed via Project Settings (cog) > Services
The following parameters are required for the endpoint.
Parameter | Description | Example |
---|---|---|
Connection Name | Name of the connection so it can be selected from the drop down list when used in a task | My Supermarket |
Chef Supermarket URL | URL for the supermarket | https://mysupermarket.example.com |
SSL Verification | Whether to perform SSL verification. Set to false if you do not have valid certificates on your supermarket. Default: True | True |
Username (Node name) | Name of the client to use to perform the upload | supermarket |
Client Key | Private key of the specified client |
On 13th November 2017 an updated version of the endpoint was released. This changes the location of the SSL Verification on the endpoint form.
Due to this change any existing Chef Server endpoints that have been setup will need to be recreated after upgrading. Old endpoints will not work properly.
Endpoints
Tasks
- Add Variables to Chef Environment
- Install ChefDK
- Execute Chef Client
- Install InSpec
- Execute Inspec
- Install Gem
- Execute Knife
- Linting
- Test Kitchen
- Release Cookbook Version to Environment
- Update Cookbook Version Number
- Upload Cookbook to Chef Server
- Publish Cookbook to Supermarket
Guides
Releases