Summarize IDL changes re Compatibility Notes API V1 (DOCS-14385)

[DOCS-14020] Investigate changes in SERVER-52544: Update IDL definition for listDatabases command Created: 25/Nov/20  Updated: 13/Nov/23  Resolved: 27/Apr/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.9.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Sub-task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Joseph Dougherty
Resolution: Fixed Votes: 0
Labels: docs-manual-idl
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-52544 Update IDL definition for listDatabas... Closed
Related
is related to DOCS-14385 Summarize IDL changes re Compatibilit... Closed
Participants:
Days since reply: 2 years, 41 weeks, 1 day ago

 Description   

Description

Downstream Change Summary

listDatabases now parses its parameters strictly, and mongod's reply now matches mongos's. See ticket comment for details.

Description of Linked Ticket

The listDatabases command already has IDL specifying its input. We should modify this to include updates we've made to IDL Command Syntax, like adding apiVersion and defining the replyType.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 27/Apr/21 ]

Author:

{'name': 'Joseph Dougherty', 'email': 'joseph.dougherty@mongodb.com', 'username': 'jmd-mongo'}

Message: DOCS-14020 documents listDatabase output changes for 5.0
Branch: v5.0
https://github.com/mongodb/docs/commit/772093172ea03987035494156bfec83efa3ef18b

Comment by Joseph Dougherty [ 27/Apr/21 ]

jeffrey.allen: Yes, I believe it can. Apologies for the delay – I'll put a PR together.

Comment by Joseph Dougherty [ 11/Feb/21 ]

Please note that this item is related to: https://jira.mongodb.org/browse/DOCSP-14008

Generated at Thu Feb 08 08:09:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.