Body
Register HTTP deployment request
Uri to use to discover/invoke the http deployment.
Additional headers added to the discover/invoke requests to the deployment.
If true
, discovery will be attempted using a client that defaults to HTTP1.1 instead of a prior-knowledge HTTP2 client. HTTP2 may still be used for TLS servers that advertise HTTP2 support via ALPN. HTTP1.1 deployments will only work in request-response mode.
If true
, it will override, if existing, any deployment using the same uri
. Beware that this can lead in-flight invocations to an unrecoverable error state.
By default, this is true
but it might change in future to false
.
See the versioning documentation for more information.
If true
, discovery will run but the deployment will not be registered. This is useful to see the impact of a new deployment before registering it.
Response
Created
During registration, the SDKs declare a range from minimum (included) to maximum (included) Service Protocol supported version.
During registration, the SDKs declare a range from minimum (included) to maximum (included) Service Protocol supported version.
SDK library and version declared during registration.