a year ago
We have a microservices setup where all applications are deployed within a single Railway project since they are tightly integrated.
Our workflow:
Staging and Production are stable environments.
Developers create/copy Staging when needed for their own development.
Only Admins/Team Leads should modify Production, while developers should have restricted access to it.
Current issue:
Access control is at the project level, meaning anyone with access can modify Production services and variables.
We need more granular access control to restrict developers from making changes to Production, while allowing them to work freely in their own environments.
Our Question:
Is there a way to restrict access to Production within the same project, while still allowing developers to create and modify their own environments? If not, what would be the best approach to achieve this in Railway?
0 Threads mention this feature
6 Replies
a year ago
!t
a year ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response brody • 11 months ago
a year ago
Thanks for escalation @brody, Really appreciate it. If you can share any ETA on when can I expect the answer for this query. Based on that we can plan to migrate our infra to Railway.
Status changed to Awaiting Railway Response brody • 11 months ago
a year ago
Sorry about the delay. I'm asking around - I'm not sure how to do this within our current constraints on RBAC inside a single project.
Status changed to Awaiting User Response Railway • 11 months ago
9 months ago
Do we have any updates on this? We’re planning to roll it out to all squads soon, and having a solution in place would make the transition much safer and more reliable.
9 months ago
Hello,
We don't currently have any projects on the board for RBAC so unfortunately, I cannot offer an ETA.