railway config partials adds IaC ownership commands

Introduced 2026-09-21 · score 0.98

HOW TO USE IT

When an authoring file is missing or you need to change named IaC ownership, inspect the linked environment’s partials, then release selected ownership or transfer it to another partial; clear all named ownership, update the authoring configuration, and run a fresh plan before whole-project planning. These commands change ownership metadata only.

WHY THIS HELPS

When managing named IaC partials whose authoring file is missing, inspect ownership, transfer selected resources, or release ownership before returning to whole-project planning.

BEFORE THIS CHANGE

The docs do not state a prior workflow for orphaned named ownership. They state that a fresh railway config plan is required after ownership changes; whole-project planning requires clearing all named ownership first.

REQUIREMENTS AND LIMITATIONS

• Version: v5.59.0
• FROM (required): Source partial; every selected address must currently belong to it.
• TO (required): Destination partial; can be new or existing.
• NAME (required): Partial whose ownership will be released.
• --resource ADDRESS: Repeat to select addresses. Omit all instances to affect the entire source partial (transfer) or all ownership held by the named partial (release). Transfer selections must belong to FROM.
• --dry-run: Preview affected addresses without executing the ownership change; with --json, provides a read-only JSON preview.
• --json: List outputs ownership details and etag; for mutations it proceeds without prompting and includes affectedResources, resulting iacPartials, and wholeProjectAvailable. Use --dry-run for a read-only JSON preview.
• --yes: Confirms mutation without prompting.
• --base-config-etag: Supplies the preview’s baseConfigEtag for a separate CI review and execution step; CLI example pairs it with --yes --json.
• Prerequisite: Commands use the linked Railway project and environment, including environment-scoped RAILWAY_TOKEN credentials.
• Prerequisite: Release and transfer require environment ADMIN access.
• Prerequisite: Commands work when the original authoring file no longer exists.
• Commands use the linked project and environment, including environment-scoped `RAILWAY_TOKEN` credentials.
• Release and transfer require environment ADMIN access.
• Every selected address must currently belong to the source partial.
• The commands work without the original authoring file.
• Release and transfer do not delete resources, change resource configuration, redeploy anything, or edit local files.
• All named ownership must be cleared before whole-project planning is available.
• The supplied guide excerpt is truncated; additional confirmation, JSON/CI usage, and re-planning guidance may apply.

FIRST-PARTY EVIDENCE

• https://github.com/railwayapp/cli/releases/tag/v5.59.0
• https://github.com/railwayapp/cli/pull/1226
• https://github.com/railwayapp/cli/blob/v5.59.0/assets/iac/README.md

Check the installed version and the source before using it. Entry JSON

Report a problem with this card