Skip to content
Same-deployment artifact, captured-command and runtime provenance semantics
sahilchhabra89
OP

a month ago

We are assessing deployment-provenance semantics before collecting any account data. This is a capability/documentation question; no private deployment, command, credential, log or recovery material is supplied.

For a single Railway deployment D, which official fields or provider attestation bind its service/environment, actual produced/selected immutable OCI artifact and platform to the authoritative reviewed-source/build→artifact linkage? Please distinguish index, selected manifest and image-config digests; a source commit or mutable image tag alone is insufficient.

Which same-deployment record proves the effective captured launch command, or supplies a provider-generated digest of its exact bytes? Please define digest algorithm, byte encoding and canonicalization, default/inherited/null versus override handling, image ENTRYPOINT/CMD and file/dashboard precedence, and shell/argument expansion. How is that artifact/command/source-build record bound to an immutable captured configuration snapshot? How can a fresh bounded check establish D is active and identify pending, staged, applying or rolling-out work?

Is there a documented native server-side projection or provider attestation returning only necessary IDs, digests, digest kinds, platform and states, while excluding variable values, credentials, raw commands, logs, full snapshots and opaque metadata before collection? Please cite authoritative/versioned semantics and a value-free response shape, including nullable/missing/unsupported cases.

If execution equivalence is supported, which provider observations additionally bind the executing artifact/platform and runtime identity to D? Otherwise, please state which guarantees are unsupported and distinguish captured launch configuration from observed execution. A new controlled image could attest what we built, but would still need Railway's same-deployment selected-artifact/launch/runtime bridge; it cannot retroactively attest an older deployment.

Our inspected public CLI schema at 05ed159796ef6bf15de0dab388b1054c1af6f395 exposes opaque DeploymentMeta and a DeploymentSnapshot with IDs/timestamps/variables, which did not establish this complete route. We are asking for the authoritative supported route, not asserting global absence or requesting broader permissions.

Solved

1 Reply

Railway
BOT

a month ago

Most of the route you describe is not available on our public API today. A deployment's meta field is an untyped JSON object. When present, it can carry an imageDigest and Git details such as the repo, branch and commit hash. There is no versioned schema for those keys, no stated digest kind (index vs selected manifest vs image config), and no platform field. DeploymentSnapshot holds only variables and timestamps, not artifact or command data.

We do not record the effective launch command per deployment, and we do not produce a digest of it. That means there are no defined semantics for override vs image ENTRYPOINT/CMD precedence, canonicalization or expansion. We also do not produce signed provenance or attestations (SLSA, in-toto, cosign) for builds, and there is no value-free projection endpoint of the kind you describe.

For live state, Deployment.status (SUCCESS, DEPLOYING, CRASHED, REMOVED and so on) and a service instance's active deployments show what is running. environmentStagedChanges(environmentId) returns the environment's changeset with a status of STAGED, APPLYING, COMMITTED or FAILED.

Execution equivalence is not supported. Deployment instances are exposed only with an ID and status, with no observed runtime image digest or container identity. Anything you derive from meta is configuration captured for that deployment, not observed execution.


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


Railway
BOT

23 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...