Summary
Currently .NET and Rust drivers (maybe other drivers as well) set topology description to Unknown and emit TopologyDescriptionChangedEvent on closing (before TopologyClosedEvent).
The SDAM logs tests account for that.
The question is whether when TopologyClosedEvent if emitted, should the topology be in up to date state, which Unknown state (all servers are removed by then).
Consider adding this behaviour to SDAM specification for a better topology state management.
For events consistency across all drivers, it would be useful to clarify the desired behaviour on topology close.
If decided that TopologyDescriptionChangedEvent should not be published on topology close, SDAM logging tests need to be updated accordingly.
Motivation
Who is the affected end user?
Drivers
How does this affect the end user?
No known affect
How likely is it that this problem or use case will occur?
Main path
If the problem does occur, what are the consequences and how severe are they?
Events consistency among drivers.
Is this issue urgent?
No
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
Yes, logging tests
Acceptance Criteria
What specific requirements must be met to consider the design phase complete?