Skip to content
Private Docker digest source: GraphQL promotion and runtime digest type
rogeriooxy
OP

a month ago

Hello Railway Support,

We reviewed these existing discussions before contacting you:

https://station.railway.com/questions/docker-image-digest-verification-48f24782

https://station.railway.com/questions/docker-image-digest-pinning-across-envir-b7bc22aa

The employee explanation that Deployment.meta.imageDigest comes from container-runtime metadata answers our main observation question. To integrate a release controller, could you clarify the remaining interface details?

  1. Which GraphQL mutation and exact input fields configure a private Docker Image source such as ghcr.io/OWNER/IMAGE@sha256:DIGEST? Which operation deploys that configuration and returns the corresponding deployment ID? Please distinguish configuration from deployment; placeholder examples without credential values are sufficient.

  2. For one Linux/amd64 replica and a reference to a single image manifest (not a multi-platform index), does Deployment.meta.imageDigest report that manifest digest or the image config digest?

We only need the current supported interface and implementation semantics. A fresh registry pull or a perpetual audit guarantee is not required. This is an information request only; please do not change resources, deploy anything, or access application data.

Thank you.

$20 Bounty

3 Replies

Railway
BOT

a month ago

We checked our documentation and it does not cover this yet, so the Railway community is the best place to get a real answer: people who have already worked this out on their own projects and can tell you what actually worked.

So we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who answers it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

  • Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
  • Keep it private and close the thread - Nothing becomes public and the thread closes.

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


Railway

We checked our documentation and it does not cover this yet, so the Railway community is the best place to get a real answer: people who have already worked this out on their own projects and can tell you what actually worked. So we'd like to open your thread as a community [bounty](https://docs.railway.com/community/bounties). Railway pays a bounty to the community member who answers it, and threads like this usually get picked up quickly. **Opening it makes this entire thread public**, including everything already posted. Nothing becomes public until you decide. Use the buttons below. - **Open to the community** - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away. - **Keep it private and close the thread** - Nothing becomes public and the thread closes.

rogeriooxy
OP

a month ago

Thank you. We still need clarification from a Railway staff member on the two specific API/implementation questions above. The existing discussion confirms Dashboard digest pinning but explicitly leaves CLI/API unspecified. Could staff provide the exact GraphQL configuration/deploy operations (a placeholder-only example is sufficient) and confirm whether imageDigest is the single-platform manifest digest or the config digest? We are not requesting independent fresh-pull provenance, a perpetual audit contract, or any account/resource changes. Please keep the technical request open for staff clarification.


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


Railway
BOT

a month ago

Our documentation still does not cover this, so the community remains the best place to get a real answer. The buttons below are still live: open the thread up as a public bounty after editing out anything sensitive, or keep it private and close it.


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


Railway
BOT

a month ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...