configEtag meaning and a secure diagnostic route for Hobby users
pearlcount
HOBBYOP

6 days ago

Could Railway clarify what the configEtag field returned by its

GraphQL API represents?

Does a changed value necessarily indicate a change to effective

environment configuration, or can it also reflect provider-side

metadata or read behaviour? Please point to documented semantics

where available.

For an account-specific investigation requiring non-public

diagnostics, is there a staff-provided secure submission route

available to Hobby users without upgrading?

I am deliberately not including configuration, credentials or

account-specific diagnostics in this public question.

$10 Bounty

1 Replies

Status changed to Awaiting Railway Response Railway • 6 days ago


Railway
BOT

6 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 6 days ago


hilmi2004
HOBBY

6 days ago

Okay so i'm not too sure but after skimming through railways pub docs the configEtag is most likely used to find configuration movement or drifts

The railway config github action uses it to check whether the env cahnges across the plan and apply

whats not clearly stated is what actually affects the value. so i do not think a changed configetag should autonomously be treated as evidence that the effective runtime configuration changed. it would be beneficial to know whether they are some other factors that can come into play to affect this.

but it does clearly state that hobby users use central station while private threads are available to pro users only because i just tried creating a private thread as a hobby plan user and it did not let me(LOL)... so i guess the question is are there any secure ways for hobby userrs to submit private diagnostics without upgrading?

**however the only way to send a private message to them without upgrading is through their support email which i have used previously to address and issue and it worked for me **

I HOPE THIS HELPS


Welcome!

Sign in to your Railway account to join the conversation.

Loading...