Updates an existing deployment configuration, such as the endpoint address or invocation headers.
By default, service schemas are not re-discovered. Set overwrite: true to trigger re-discovery.
Deployment identifier
Update HTTP deployment request
Additional headers added to the discover/invoke requests to the deployment. When provided, this will overwrite all the headers previously configured for this deployment.
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.
If true, the update will overwrite the schema information, including the exposed service and handlers and service configuration, allowing breaking changes too. Use with caution.
Uri to use to discover/invoke the http 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.
Deployment updated successfully. Address and invocation options are updated. Service schemas are only updated if overwrite was set to true.
Detailed information about Restate deployments
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.
Protocol type used to invoke this service deployment.
RequestResponse, BidiStream List of services exposed by this deployment.
URI used to invoke this service deployment.
Additional headers used to invoke this service deployment.
List of configuration/deprecation information related to this deployment.
Deployment metadata.
SDK library and version declared during registration.