Railway

Move variables to and from a Railway environment.

The connection

What	This provider
Vendor	Railway
Key	`railway-vars`
Availability	`available`. You can connect it today.
Credential penv holds	`railway-token`
Values read back	yes
Activation	`on-request`

Direction	What it does
`import`	Reads names and values out of the store into penv.
`export`	Writes names and values from penv into the store.

on-request. A new value waits there. penv can deploy to activate it, and the sync form asks you first.

Direction	Policies you can pick
`import`	`skip_existing`, `new_version`, `fail`
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

You paste a credential you already hold. penv seals it and never shows it again.

Field	Label	Kind	Required	What it is
`token`	Token	secret, masked here and sealed	yes

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`projectId`	Project	text	yes	no	The project's id, from its URL in the Railway dashboard.
`environmentId`	Environment	text	yes	no	Railway's own environment id. Production and staging are different ids.
`serviceId`	Service	text	no	yes	Leave empty to write the environment's shared variables instead of one service's.
`deployAfterSync`	Redeploy after each sync	yes or no	yes	yes	Off, values wait for your next deploy. On, Railway redeploys this service immediately. Starts at `false`.

penv probes for these when it verifies the connection.

Permission	Directions	Blocking	Without it
`me:read`	every direction	yes	We cannot confirm which Railway account this token belongs to.
`variables:read`	`import`	yes	Import cannot read variable values.
`variables:write`	`export`	yes	Export cannot write anything.