Skip to content
Authenticated OCI digest and complete serving-replica provenance
bradmaeder
OP

a month ago

We are assessing a release gate before deploying an isolated API service. Railway GraphQL exposes Deployment.meta.imageDigest, ServiceInstance.activeDeployments, and deployment instances { id status }. Please confirm the supported, documented contract:

  1. Does meta.imageDigest identify the pulled OCI index, the resolved platform manifest, the image config, or another object? Is that value immutable for the deployment, and where is its media type available?
  2. What authenticated Railway evidence binds the resolved linux/amd64 platform-manifest digest to each actual running replica after initial deployment, scaling, restart and replacement? Is a provider-signed attestation available?
  3. What API returns the complete set of replicas eligible to serve public traffic, including both deployments during rollout overlap? Is that read atomic, and does RUNNING mean traffic-serving?
  4. Are these guarantees available on Hobby or Pro? Please identify the exact API fields and documentation. We are not asking whether private-registry access alone is available.

The preview service is currently undeployed. We can provide project and service IDs through an appropriate non-public channel if needed. No credentials or application data are needed.

Solved

1 Reply

Railway
BOT

a month ago

We don't offer the contract your release gate needs, on Hobby or on Pro. Changing plans raises resource ceilings and doesn't change any of this.

meta.imageDigest is a single digest recorded for the whole deployment. We don't guarantee which OCI object it refers to: depending on how the image was pulled, it can be the index digest or the platform manifest digest. Its media type isn't stored or returned anywhere, and the value can be filled in after the deployment starts, so don't treat it as an immutable, typed identifier.

Nothing ties a digest to an individual replica. Deployment instances return only id and status, and there's no attestation signed by us for the image a replica is running.

No API returns the set of replicas currently eligible for public traffic. ServiceInstance.activeDeployments includes both deployments while a rollout overlaps, but it also includes deployments that are building, queued, crashed or sleeping. It isn't an atomic read of what's serving. An instance status of RUNNING means the container started, not that it's receiving traffic.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

24 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...