File tree Expand file tree Collapse file tree 2 files changed +7
-2
lines changed Expand file tree Collapse file tree 2 files changed +7
-2
lines changed Original file line number Diff line number Diff line change @@ -99,7 +99,7 @@ onprem-full = "MongoDB Ops Manager"
99
99
opsmgr-example-url = " <OpsManagerHost>:<Port>"
100
100
opsmgr-url = " <OpsManagerHost>:<Port>"
101
101
pkce = " :abbr:`PKCE (Proof Key of Code Exchange)`"
102
- version = " 8.0.2 "
102
+ version = " 8.0"
103
103
wif = " Workforce Identity Federation"
104
104
workload = " Workload Identity Federation"
105
105
Original file line number Diff line number Diff line change @@ -13,7 +13,12 @@ Update Version Manifest Manually
13
13
You can use Automation to install and upgrade MongoDB instances in your
14
14
deployment. You need to give |onprem| a list of which versions can be
15
15
installed. The complete list of all possible MongoDB editions and
16
- versions is called the :opsmgr:`version manifest </reference/glossary/#std-term-version-manifest>`.
16
+ versions is called the :opsmgr:`version manifest
17
+ </reference/glossary/#std-term-version-manifest>`. Ensure that the
18
+ MongoDB versions in the version manifest are :ref:`supported
19
+ <backup-compatibility>` by the |onprem| version that you are using. You
20
+ can't use a version manifest that has newer or older MongoDB versions
21
+ than what your |onprem| version supports.
17
22
18
23
If you configure the {+mdbagent+} to use remote or hybrid downloads,
19
24
|onprem| updates the version manifest automatically.
You can’t perform that action at this time.
0 commit comments