The replicationRole of Postgresql Flexible Server should be None when the replicationRole is updated from AsyncReplica or GeoAsyncReplica to None

[neil-yechenwei]

Currently, the replicationRole of Postgresql Flexible Server is set to Primary when the replicationRole is updated from AsyncReplica or GeoAsyncReplica to None. Service team confirmed it should be set to None when the replicationRole is updated from AsyncReplica or GeoAsyncReplica to None and they will fix it. So filed this issue for tracking.

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sunilagarwal, @lfittl-msft, @sr-msft, @niklarin.

Issue Details

---

Currently, the replicationRole of Postgresql Flexible Server is set to Primary when the replicationRole is updated from AsyncReplica or GeoAsyncReplica to None. Service team confirmed it should be set to None when the replicationRole is updated from AsyncReplica or GeoAsyncReplica to None and they will fix it. So filed this issue for tracking.

Author:	neil-yechenwei
Assignees:	-
Labels:	PostgreSQL, Service Attention, needs-triage
Milestone:	-