You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating/updating sessions accepts both new style and old style payloads for back compat reasons, but guessing we should add something to the documentation around that also.
The text was updated successfully, but these errors were encountered:
Update output for /v1/session/ endpoints to match output post Consul
1.7.0.
Documents new `NodeChecks` and `ServiceChecks` parameters which were
added in that release.
Resolves#7341, resolves#10095
Update output for /v1/session/ endpoints to match output post Consul
1.7.0.
Documents new `NodeChecks` and `ServiceChecks` parameters which were
added in that release.
Resolves#7341, resolves#10095
Update output for /v1/session/ endpoints to match output post Consul
1.7.0.
Documents new `NodeChecks` and `ServiceChecks` parameters which were
added in that release.
Resolves#7341, resolves#10095
Update output for /v1/session/ endpoints to match output post Consul
1.7.0.
Documents new `NodeChecks` and `ServiceChecks` parameters which were
added in that release.
Resolves#7341, resolves#10095
The documentation for the read response for Session Locks uses the old pre-1.7 shape:
https://www.consul.io/api-docs/session#sample-response-2
This was changed in 1.7:
Creating/updating sessions accepts both new style and old style payloads for back compat reasons, but guessing we should add something to the documentation around that also.
The text was updated successfully, but these errors were encountered: