Update the Automation Configuration (Sensitive Information Ignored)

A project's automation configuration determines the goal state of its MongoDB processes and agents. The MongoDB Agent builds the deployment according to the goals specified.

An automation configuration might contain sensitive information, such as passwords and key values. This resource allows you to update a project's automation configuration without updating any fields that contain sensitive information.

PUT requests to the /groups/{PROJECT-ID}/automationConfig/noSecrets endpoint ignore any fields in the automation configuration in your request body that contain sensitive information, leaving their current values unchanged and updating all other fields. To update the complete automation configuration, including any sensitive information, use the /groups/{PROJECT-ID}/automationConfig endpoint.

To update the configuration:

1. Retrieve the current configuration.

   You can use either the /groups/{PROJECT-ID}/automationConfig endpoint to get the full configuration, or the /groups/{PROJECT-ID}/automationConfig/noSecrets endpoint to get the configuration with sensitive information redacted, such as passwords or key values.

2. Make changes to a copy of the current configuration, changing only those items you want modified.

3. Replace the entire configuration using PUT, with the updated configuration in the request body. You must use PUT. Do not use PATCH.

   When you submit updates, Cloud Manager makes internal modifications to the data and then saves your new configuration version.

To see a tutorial on how to update an automation configuration, see Update the Automation Configuration Resource Tutorial.

The MongoDB Agents continuously poll Cloud Manager for changes to the configuration and fetch configuration updates when they occur. The Agents then adjust the states of their live processes to match.

PUT /groups/{PROJECT-ID}/automationConfig/noSecrets

curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest \
     --header "Accept: application/json" \
     --header "Content-Type: application/json" \
     --include \
     --request PUT "https://cloud.mongodb.com/api/public/v1.0/groups/{PROJECT-ID}/automationConfig/noSecrets?pretty=true" \
     --data-binary "@/Users/admin/updated-conf.json"

HTTP/1.1 401 Unauthorized
Content-Type: application/json;charset=ISO-8859-1
Date: {dateInUnixFormat}
WWW-Authenticate: Digest realm="MMS Public API", domain="", nonce="{nonce}", algorithm=MD5, op="auth", stale=false
Content-Length: {requestLengthInBytes}
Connection: keep-alive

HTTP/1.1 200 OK
Vary: Accept-Encoding
Content-Type: application/json
Strict-Transport-Security: max-age=300
Date: {dateInUnixFormat}
Connection: keep-alive
Content-Length: {requestLengthInBytes}
X-MongoDB-Service-Version: gitHash={gitHash}; versionString={ApplicationVersion}