Registers a new deployment (HTTP or Lambda). Restate will invoke the endpoint to discover available services and handlers, and make them available for invocation. For more information, see the deployment documentation.
Register HTTP deployment request
Uri to use to discover/invoke the http deployment.
Additional headers added to every discover/invoke request to the deployment.
You typically want to include here API keys and other tokens required to send requests to deployments.
If true, it allows registering new service revisions with
schemas incompatible with previous service revisions, such as changing service type, removing a handler, etc.
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.
force and breaking will be respected.
If true, it overrides, if existing, any deployment using the same uri.
Beware that this can lead inflight invocations to an unrecoverable error state.
When set to true, it implies breaking = true.
See the versioning documentation for more information.
Deployment metadata.
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 already exists. No change if force = false, services overwritten if force = true
List of configuration/deprecation information related to this 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.
SDK library and version declared during registration.