Not sure if this is the right place for this but its the most appropriate place ive found .
Cloud formation has a linter.
Would be cool if "railway-formation" or whatever it will be called ( hopefully something train related and cool ) had the same.
https://github.com/aws-cloudformation/cfn-lint
( im assuming infra as code would be something along the lines as a json file )
Being able to define variables that get populated inside the "railway-formation" would also be nice i think could be usefull along with the ability to split the schema across multiple files. (but i may be barking up the wrong tree!)

Pulumi and Terraform please

Pulumi and Terraform please

Sean Knowles: You mean that you would want a Terraform adapter into Railway? Just want more clarification on what you expect to see.

This feature is now in beta! I encourage everyone to try it out and give us your feedback :)
https://docs.railway.app/deploy/config-as-code

Love the idea of the toml/json build spec, but unless I'm mistaken this doesn't really address the idea of the linked Railway cli github issue. Ideally I would be able to connect a new repo with a full IaC config and have it set up the db, api, frontend, perform database migrations and seed scripts across all defined environments. The config as it stands is just single-environment, single-service deploy details, right?

Pulumi and Terraform please

Angelo Saraceno: That would actually be very nice. Not sure how much sense it would make at the moment though… It would maybe make more sense once routes, databases, subnets, etc. could be configured.

I'd absolutely love a Terraform provider for Railway – we manage our infrastructure (AWS, GitHub resources, Vercel, etc) by writing terraform config files, and it would be nothing short of amazing to add a provider for Railway.

https://registry.terraform.io/browse/providers

Pulumi and Terraform please

Angelo Saraceno: +1 here on a Terraform provider for Railway – added a comment above in the same vein before I saw this comment here.

I have an initial implementation released at https://registry.terraform.io/providers/terraform-community-providers/railway/latest/docs.

Just waiting for more info from Railway people to implement support for variables.

For terraform please upvote https://railway.canny.io/feature-requests/p/terraform-provider

https://registry.terraform.io/providers/terraform-community-providers/railway is ready and I am using it in production for my use cases.

If you feel something is missing, PR contributions are welcome.

Leaving a comment here as the team is looking into a second pass in unifying our Infrastructure as Code feature set.

We support: https://docs.railway.app/deploy/config-as-code and https://nixpacks.com/docs/guides/configuring-builds but we are looking for more of your feedback!

Leaving a comment here as the team is looking into a second pass in unifying our Infrastructure as Code feature set.

We support: https://docs.railway.app/deploy/config-as-code and https://nixpacks.com/docs/guides/configuring-builds but we are looking for more of your feedback!

Angelo Saraceno: Having an official terraform provider would be awesome.

Leaving a comment here as the team is looking into a second pass in unifying our Infrastructure as Code feature set.

We support: https://docs.railway.app/deploy/config-as-code and https://nixpacks.com/docs/guides/configuring-builds but we are looking for more of your feedback!

Angelo Saraceno: The config-as-code does not support defining and attaching volume to services.

Just pitching in here to say that I'd really like full-project IaC for monorepos with microservices, as described in the original issue - this would also solve variables in new environments, as you could just spin up a new environment from a config file. In addition, you could even add new services in PRs and have that just work without breaking.

TL;DR: having code changes that depend on infrastructure changes is a point of failure that could be solved by this.

Also, this would simplify template creation significantly.

You have a api, create a pulumi provider - done.

Not having Pulumi provider is really a bummer.