Closed antoinesd closed 4 years ago
I think similarly to @Liveness
having /health/live
and @Readiness
having /health/ready
, @Wellness
should have /health/well
.
@Ladicek it might be, but well
as a word is quite overloaded :) I personally don't have a preference.
@antoinesd do we want to introduce this as experimental or wait for the spec (there are no comments in GG).
I think we can wait to have it in the spec. Wdyt?
We need to be validating ideas in the implementation before we bring them to the spec
@kenfinnigan do you mean that we shouldn't now add any new API in the spec if it hasn't been already for some time in SR?
That has been the understanding for a while and made as clear as I and others can over the last 4-5 months.
yeah, I know but given the timeline, we won't introduce any new features in Health 3.0 if we take this into account, unfortunately. While we still need a breaking release this seems a little harsh trade-off for users.
Maybe, but that's the approach we're taking.
If we haven't proven that a new API is usable, appropriate, and defined properly, it's premature to add it to a spec
We need to introduce the support for
/health/wellness
and@Wellness
qualifier