[DRIVERS-2498] Provide access to deprecated command messages from server Created: 08/Nov/22  Updated: 08/Nov/22  Resolved: 08/Nov/22

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Spec Change Priority: Unknown
Reporter: Martin Bajana Assignee: James Kovacs
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Summary

What is the problem or use case, what are we trying to achieve?
Provide access to deprecated command messages from server.

Motivation

Who is the affected end user?

Who are the stakeholders?

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?

How likely is it that this problem or use case will occur?

Main path? Edge case?

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

Is this issue urgent?

Does this ticket have a required timeline? What is it?

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?

Is this ticket only for tests?

Does this ticket have any functional impact, or is it just test improvements?



 Comments   
Comment by James Kovacs [ 08/Nov/22 ]

When a deprecated command is run, the deprecation message is written to the server logs and no indication of the deprecation is added to the command response. Thus there is no way for a driver to tell if the command is deprecated or not.

Even from a Stable API perspective (which is different than the command deprecation mentioned above), either the command fails (because it is not part of Stable API and we requested apiStrict) or fails (because it is deprecated and we requested apiDeprecationErrors). In either case, the command fails outright and the failure is surfaced as a command error. At no point will we receive a deprecation warning as part of a command response.

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