Skip to content

chore(railway): keep AXIOM_TOKEN and AXIOM_DATASET on config apply - #95

Merged
Gintm merged 1 commit into
developfrom
chore/railway-keep-axiom-vars
Nov 12, 2026
Merged

Gintm merged 1 commit into
developfrom
chore/railway-keep-axiom-vars

Conversation

@Gintm

@Gintm Gintm commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Why

py#94 merged before this commit landed. .railway/railway.ts lists the production variables to preserve; without these two, a railway config apply could drop them and stop the MCP sending tool calls to Axiom without anyone noticing.

What

  • Adds AXIOM_DATASET and AXIOM_TOKEN to the preserved production variables.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Gintm

Gintm commented Nov 12, 2026

Copy link
Copy Markdown
Contributor Author

Review (code-review high --fix)

Finding Result
preserve() names AXIOM_DATASET and AXIOM_TOKEN before they exist on the Railway service; how railway config plan/apply treats a missing variable is not verified Skipped: merge after the two variables are set on Railway, then the question does not arise. Empty values would be harmless (the sink needs both non-empty)

QA

Check Result
Diff is only the two names in the production list Confirmed
Deploy behaviour Unchanged: Railway does not read this file at deploy, only railway config plan/apply

Metrics

Metric Before Expected after
Runtime No effect No effect; protects the two variables from being dropped on the next config apply

@Gintm
Gintm merged commit 043c819 into develop Nov 12, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant