Skip to content

(DOCSP-54845) Move include file from atlas to shared docs repo #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 4, 2025
Merged

(DOCSP-54845) Move include file from atlas to shared docs repo #138

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4f3a931
(DOCSP-54845) Move include file from atlas to shared docs repo
jromo-mdb Oct 22, 2025
ee51a49
Reword note to emphasize cluster type and add mention of mongosync.
jromo-mdb Oct 23, 2025
9692cce
Add link to mongosync and specify Atlas UI for LM
jromo-mdb Oct 28, 2025
296e546
Rename file to be more descriptive and add link to upgrade page.
jromo-mdb Oct 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions cet/atlas/mongosync-compatibility-restriction.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
.. important::

If you are using {+dedicated-clusters+} for your deployment and plan to use
Live Migration in the {+atlas-ui+} or standalone |mongosync|,
do NOT choose :guilabel:`Latest Version With Auto Upgrades`.
This option auto upgrades your {+cluster+} to the latest minor release.
Some minor releases, such as MongoDB version 8.2, may not be supported by Live
Copy link
Collaborator

@JuliaMongo JuliaMongo Oct 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may not support (instead of may not be supported)

Migration or Mongosync. Choose a major version instead to ensure compatibility
Copy link
Collaborator

@JuliaMongo JuliaMongo Oct 29, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When upgrading, choose a major version to upgrade to instead. This ensures compatibility with Live Migration and mongosync.

JM: upgrade -- this could be a link. I am not sure this link will work in either product if we use a shared include. Please check. If not possible, don't use a link.

upgrade link: 
https://www.mongodb.com/docs/atlas/tutorial/major-version-change/#upgrade-your-major-mongodb-version

Also: Live Migration and mongosync are not products and we should not call them such.

Also, we had a note already and could have used the text from that note. That text was clear and reviewed, and I don't see a reason for rewriting that note here, if it was me, I'd just expand the existing note.

Lastly, I would name the note file: mongosync-dont-use-mdb-minor-version.rst
This makes it easier to future writers who will maintain this content to know instantly what's inside the note from its title. But up to you!

Copy link
Collaborator Author

@jromo-mdb jromo-mdb Oct 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All these are good suggestions. The link should work because of intersphinx. Will still merge the shared-docs PR first and then rerun the monorepo PR to verify logs for any errors. Thanks.

with these products.