Table Of Contents

Feedback

User Guide

First time using the AWS CLI? See the User Guide for help getting started.

Note: You are viewing the documentation for an older major version of the AWS CLI (version 1).

AWS CLI version 2, the latest major version of AWS CLI, is now stable and recommended for general use. To view this page for the AWS CLI version 2, click here. For more information see the AWS CLI version 2 installation instructions and migration guide.

[ aws . codecommit ]

put-repository-triggers

Description

Replaces all triggers for a repository. Used to create or delete triggers.

See also: AWS API Documentation

See 'aws help' for descriptions of global parameters.

Synopsis

  put-repository-triggers
--repository-name <value>
--triggers <value>
[--cli-input-json <value>]
[--generate-cli-skeleton <value>]

Options

--repository-name (string)

The name of the repository where you want to create or update the trigger.

--triggers (list)

The JSON block of configuration information for each trigger.

Shorthand Syntax:

name=string,destinationArn=string,customData=string,branches=string,string,events=string,string ...

JSON Syntax:

[
  {
    "name": "string",
    "destinationArn": "string",
    "customData": "string",
    "branches": ["string", ...],
    "events": ["all"|"updateReference"|"createReference"|"deleteReference", ...]
  }
  ...
]

--cli-input-json (string) Performs service operation based on the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally.

--generate-cli-skeleton (string) Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for --cli-input-json. If provided with the value output, it validates the command inputs and returns a sample output JSON for that command.

See 'aws help' for descriptions of global parameters.

Examples

To add or update a trigger in a repository

This example demonstrates how to update triggers named 'MyFirstTrigger' and 'MySecondTrigger' using an already-created JSON file (here named MyTriggers.json) that contains the structure of all the triggers for a repository named MyDemoRepo. To learn how to get the JSON for existing triggers, see the get-repository-triggers command.

Command:

aws codecommit put-repository-triggers --repository-name MyDemoRepo file://MyTriggers.json

JSON file sample contents:
{
  "repositoryName": "MyDemoRepo",
  "triggers": [
      {
          "destinationArn": "arn:aws:sns:us-east-1:80398EXAMPLE:MyCodeCommitTopic",
          "branches": [
              "master",
              "preprod"
          ],
          "name": "MyFirstTrigger",
          "customData": "",
          "events": [
              "all"
          ]
      },
              {
          "destinationArn": "arn:aws:lambda:us-east-1:111111111111:function:MyCodeCommitPythonFunction",
          "branches": [],
          "name": "MySecondTrigger",
          "customData": "EXAMPLE",
          "events": [
              "all"
          ]
      }
  ]
}

Output:

{
  "configurationId": "6fa51cd8-35c1-EXAMPLE"
}

Output

configurationId -> (string)

The system-generated unique ID for the create or update operation.