Update deployment. Invokes the endpoint and replaces the existing deployment metadata with the discovered information. This is a dangerous operation that should be used only when there are failing invocations on the deployment that cannot be resolved any other way. Sense checks are applied to test that the new deployment is sufficiently similar to the old one.
Deployment identifier
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, discovery will run but the deployment will not be registered. This is useful to see the impact of a new deployment before registering it.
Detailed deployment response for HTTP deployments
URI used to invoke this service deployment.
Protocol type used to invoke this service deployment.
RequestResponse, BidiStream HTTP Version used to invoke this service deployment.
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.
List of services exposed by this deployment.
Additional headers used to invoke this service deployment.
SDK library and version declared during registration.