Skip to main content

Slack Commands

Warning

These commands must be run from Chef Software Slack.

/expeditor promote

The /expeditor promote command will trigger a project_promoted workload for the project in question. Please check out promotion guide for full details on how to handle project promotion.

Note

This command is only available to members of the release-promoters Slack user group.
Parameters
The /expeditor promote Slack command requires the following ordered parameters:
  1. The agent ID or alias for the project being promoted. Click here to learn more about these terms.
  2. The version reference, either a semantic version or “head of channel” reference. See our promotion guide on which to use.
Sample Usage: Promote using agent ID and semantic version reference
Promote version 1.0.0 of the chef/example:main project 
/expeditor promote chef/example:main 1.0.0
Sample Usage: Promote using alias and “head of channel” version reference
Promote the head of the current channel for chef/example:main using it’s configured alias example 
/expeditor promote example current

/expeditor notifications

The /expeditor notifications sub-commands allow you to manage a Slack channel’s subscriptions to workloads that support the built_in:notify_chefio_slack_channel action. This is particularly useful for things like the incident_status_updated workload, which allows you to subscribe to incident notifications for all of the supported services.

list

Return a list of the Slack channel’s current subscriptions.

/expeditor notifications list

subscribe

Subscribe the current Slack channel to notifications for the given workload.

Parameters
The /expeditor notifications subscribe command requires the following ordered parameters:
  1. The workload subscription glob to be added (e.g. incident_status_updated:habitat:*)
Sample Usage
Subscribe the channel to all incident notifications for the habitat service. Click here to see a list of all the supported services for incident notifications. 
/expeditor notifications subscribe incident_status_updated:habitat:*

unsubscribe

Remove a subscription from the current Slack channel. You can use /expeditor notifications list to get a list of the Slack channel’s current subscriptions.

Parameters
The /expeditor notifications unsubscribe command requires the following ordered parameters:
  1. The workload subscription glob to be removed (e.g. incident_status_updated:habitat:*)
Sample Usage
Remove the subscription to all incident notifications for the habitat service from the channel. 
/expeditor notifications unsubscribe incident_status_updated:habitat:*

/expeditor package

The /expeditor package sub-commands allow you to inspect and query certain aspects of the Omnibus packages provided through mixlib-install.

has-dep

Determine whether or not the Omnibus packages have a certain Omnibus software dependency, and if so at what version.

Parameters
The /expeditor package has-dep command requires the following ordered parameters:
  1. The name of the Omnibus Software dependency.
Sample Usage
Determine which Omnibus packages have a dependency on ruby. 
/expeditor package has-dep ruby

deps

List all Omnibus software dependencies for a given Omnibus package.

Parameters
The /expeditor package deps command requires the following ordered parameters:
  1. The name of the mixlib-install](https://github.com/chef/mixlib-install) Omnibus package.
Sample Usage
Get a list of all the Omnibus software dependencies for the chef Omnibus package. 
/expeditor package deps chef

/expeditor staging-area

The /expeditor staging-area sub-commands allow you to control staging areas manually from a Slack channel.

lock

Manually lock a staging area for your project.

Parameters
The /expeditor staging-area lock command requires the following ordered parameters:
  1. The agent ID or alias for the project being promoted. Click here to learn more about these terms.
  2. The name of the staging area.
Sample Usage
Lock the post_merge staging area on the chef/example:main project using it’s alias example. 
/expeditor staging-area lock example post_merge

unlock

Manually unlock a staging area for your project.

Parameters
The /expeditor staging-area unlock command requires the following ordered parameters:
  1. The agent ID or alias for the project being promoted. Click here to learn more about these terms.
  2. The name of the staging area.
Sample Usage
Unlock the post_merge staging area on the chef/example:main. 
/expeditor staging-area lock chef/example:main post_merge