Non-sorted Opensearch endpoints causing unnecessary relation-changed events every update-status for client applications.
Cause is because they are not sorted, resulting in random ordering each time, causing a 'change' that isn't necessary
Steps to reproduce
Relate a charm to opensearch:opensearch-client, log out relation-changed events and the endpoints in it
Expected behavior
Not getting relation-changed every update-status with the same content
Actual behavior
Getting relation-changed every update-status with the same content
Log output
(from a client application, printing out what it gets from the relation-changed event)
Issue
Non-sorted Opensearch endpoints causing unnecessary
relation-changed
events everyupdate-status
for client applications. Cause is because they are not sorted, resulting in random ordering each time, causing a 'change' that isn't necessarySteps to reproduce
Relate a charm to
opensearch:opensearch-client
, log outrelation-changed
events and theendpoints
in itExpected behavior
Not getting
relation-changed
everyupdate-status
with the same contentActual behavior
Getting
relation-changed
everyupdate-status
with the same contentLog output
(from a client application, printing out what it gets from the
relation-changed
event)