/ /

Update the Version Manifest

Use this resource to upload the latest version manifest from MongoDB, Inc.

Important

The latest MongoDB version manifest introduces the isSpecialLTSVersion field. In Ops Manager 8.0 releases prior to 8.0.12, this field might impact response generation logic after a successful PUT request to the api/public/v1.0/versionManifest endpoint.

This issue is resolved in Ops Manager 8.0.12. If you are running an earlier 8.0 release, we recommend one of the following actions:

Upgrade to Ops Manager 8.0.12 or later to ensure compatibility.
If you cannot upgrade immediately, modify your API requests to filter out the isSpecialLTSVersion field.

Contact MongoDB Support for further assistance.

Warning

Don't change any values in the JSON file. The parameters and values in this file -- as well as how they are structured -- can change without notice.

Required Roles

You can successfully call this endpoint with any of the following assigned roles:

Tip

Upload the Latest Version Manifest to Ops Manager with the API.

Resource

Base URL: https://{OPSMANAGER-HOST}:{PORT}/api/public/v1.0

PUT /versionManifest

Request Path Parameters

This endpoint doesn't use HTTP request path parameters.

Request Query Parameters

The following query parameters are optional:

Name	Type	Description	Default
`pretty`	boolean	Indicates whether the response body should be in a prettyprint format.	`false`

Request Body Parameters

This endpoint doesn't use HTTP request body parameters.

Response

These values may change at any time without notice. They remain compatible with Ops Manager.

Example Request

1 curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest \
2      --header "Accept: application/json" \
3      --header "Content-Type: application/json" \
4      --include \
5      --request PUT "https://<OpsManagerHost>:<Port>/api/public/v1.0/versionManifest?pretty=true" \
6      --data @4.2.json

Example Response

Response Header

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}

Response Body

The JSON file includes all data that your Ops Manager instance needs. This covers all available versions and variants of MongoDB to download and deploy to Ops Manager-managed MongoDB hosts.

The parameters and values in this file -- as well as how they are structured -- can change without notice.

Back

Retrieve

Log Collection Jobs

1	curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest \
2	--header "Accept: application/json" \
3	--header "Content-Type: application/json" \
4	--include \
5	--request PUT "https://<OpsManagerHost>:<Port>/api/public/v1.0/versionManifest?pretty=true" \
6	--data @4.2.json