Triggers

Operations workflow page for Zendesk triggers

Creating a trigger

For these, you will need to create a corresponding trigger file in the sync repo.

You should also do this in a way that creates a MR. Said MR should always be peer reviewed before merging (the MR should enforce this).

The exact nature of what you need to put into the YAML file will vary based on the issue’s request.

Be sure to read Working with sync repo files for more information.

Editing a trigger

For these, you will need to locate the corresponding trigger file in the sync repo and make changes to it.

You should also do this in a way that creates a MR. Said MR should always be peer reviewed before merging (the MR should enforce this).

The exact nature of what you need to put into the YAML file will vary based on the issue’s request.

Be sure to read Working with sync repo files for more information.

Deactivating a trigger

To deactivate an trigger, you must make the following changes in the corresponding trigger file in the sync repo:

  1. Move the trigger from the active folder to the the corresponding location in the inactive folder (if it does not exist, create it)

  2. Change the value of the active attribute in the YAML file to false

  3. Change the conditions seciton to be:

    - field: 'brand_id' operator: 'is_not' value: 'GitLab Support'
  4. Change the actions section to be:

    - field: 'brand_id' value: 'GitLab Support'
  5. Change the value of the contains_managed_content attribute to false

You should also do this in a way that creates a MR. Said MR should always be peer reviewed before merging (the MR should enforce this).

Deleting a trigger

The process to delete a trigger is exactly as described in the triggers documentation page.

Exception deployment

To perform an exception deployment for triggers, navigate to the triggers project in question, go to the scheduled pipelines page, and click the play button. This will trigger a sync job for the triggers.