Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-notify-delete.html below:

Delete triggers from an AWS CodeCommit repository

You might want to delete triggers if they are no longer being used. You cannot undo the deletion of a trigger, but you can create one again.

If you configured one or more triggers for your repository, deleting the repository does not delete the Amazon SNS topics or Lambda functions you configured as the targets of those triggers. Be sure to delete those resources, too, if they are no longer needed.

1. Open the CodeCommit console at https://console.aws.amazon.com/codesuite/codecommit/home.

2. In Repositories, choose the repository where you want to delete triggers for repository events.

3. In the navigation pane for the repository, choose Settings. In Settings, choose Triggers.

4. Choose the trigger you want to delete from the list of triggers, and then choose Delete.

5. In the dialog box, type delete to confirm.

1. At a terminal (Linux, macOS, or Unix) or command prompt (Windows), run the get-repository-triggers command to create a JSON file with the structure of all of the triggers configured for your repository. For example, to create a JSON file named MyTriggers.json with the structure of all of the triggers configured for a repository named MyDemoRepo:

   aws codecommit get-repository-triggers --repository-name MyDemoRepo >MyTriggers.json

   This command creates a file named MyTriggers.json in the directory where you ran the command.

2. Edit the JSON file in a plain-text editor and remove the trigger block for the trigger you want to delete. Replace the configurationId pair with a repositoryName pair. Save the file.

   For example, if you want to remove a trigger named MyFirstTrigger from the repository named MyDemoRepo, you would replace configurationId with repositoryName, and remove the statement in red italic text:

   {
       "repositoryName": "MyDemoRepo", 
       "triggers": [
           {
               "destinationArn": "arn:aws:sns:us-east-2:111122223333:MyCodeCommitTopic", 
               "branches": [
                   "main", 
                   "preprod"
               ], 
               "name": "MyFirstTrigger", 
               "customData": "", 
               "events": [
                   "all"
               ]
           }, 
           {
               "destinationArn": "arn:aws:lambda:us-east-2:111122223333:function:MyCodeCommitJSFunction", 
               "branches": [], 
               "name": "MyLambdaTrigger", 
               "events": [
                   "all"
               ]
           }  
       ]
   }

3. At the terminal or command line, run the put-repository-triggers command. This updates the triggers for the repository and deletes the MyFirstTrigger trigger:

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

   This command returns a configuration ID, similar to the following:

   {
       "configurationId": "0123456-I-AM-AN-EXAMPLE"
   }

   Note

   To delete all triggers for a repository named MyDemoRepo, your JSON file would look similar to this:

   {
       "repositoryName": "MyDemoRepo",
       "triggers": []
   }

Test triggers for a repository

Associate or disassociate a repository with Amazon CodeGuru Reviewer

Did this page help you? - Yes

Thanks for letting us know we're doing a good job!

If you've got a moment, please tell us what we did right so we can do more of it.

Did this page help you? - No

Thanks for letting us know this page needs work. We're sorry we let you down.

If you've got a moment, please tell us how we can make the documentation better.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4