Comment 9 for bug 1750915

I think the bug could be generalised to "API service advertises endpoint before all units of service are ready" and it applies to most (all ?) of our api charms I expect. So, I think option 2 is probably the correct one but I would say option 1 is fine for this particular instance. I am not keen on option 3. I think the contract between charms should be such that if a charm advertises and endpoint it is declaring that that endpoint is ready to use.

As I say, option 2 probably needs to be done regardless of whether option 1 is implemented. thedac has already done a lot of work in various charms to delay endpoint advertising. I think that work needs to be applied here with the additional delay of "If ssl is enabled don't advertise
endpoint until certs/keys are configured and installed on all units".