Disable a Trigger

In Atlas, go to the Triggers page.

1. If it's not already displayed, select the organization that contains your project from the Organizations menu in the navigation bar.

2. If it's not already displayed, select your project from the Projects menu in the navigation bar.

3. In the sidebar, click Triggers under the Streaming Data heading.

The Triggers page displays.

From the listed Triggers, find the Trigger that you want to disable.

Toggle the Enabled setting to disable it, then click Save.

Authenticate a MongoDB Atlas user:

Use your MongoDB Atlas Administration API Key to log in to the App Services CLI:

appservices login --api-key="<API KEY>" --private-api-key="<PRIVATE KEY>"

Pull your App's latest configuration files:

Run the following command to get a local copy of your configuration files:

appservices pull --remote=<App ID>

By default, the command pulls files into the current working directory. You can specify a directory path with the optional --local flag.

Verify the Trigger configuration file:

If you exported a new copy of your application, it should already include an up-to-date configuration file for the suspended Trigger. You can confirm that the configuration file exists by looking in the /triggers directory for a Trigger configuration file with the same name as the Trigger.

Disable the Trigger:

After you have verified that the Trigger configuration file exists, add a field named "disabled" with the value true to the top level of the Trigger json definition:

{
   "id": "6142146e2f052a39d38e1605",
   "name": "steve",
   "type": "SCHEDULED",
   "config": {
      "schedule": "*/1 * * * *"
   },
   "function_name": "myFunc",
   "disabled": true
}

Deploy your changes:

Run the following command to deploy your changes:

appservices push