a year ago
Hi,
It would be great if I could permanently exclude specific services from syncing between environments.
My use case is a backup service that I only want in the production environment. Currently, I have to manually discard the service removal every time I sync the production environment with the QA environment.
Additionally, it would be very useful if some sort of exclusion filter could be set at the variable level. For example, there are certain variables I want to exist in all environments, but I do not want them to be synced. Now I have to manually discard the sync, which can easily lead to errors.
2 Replies
a year ago
I agree on both wishes (to exclude services and variables from sync).
I have a project with prod and DEV env. And a specific service i only need in DEV. So whenever i have to sync i have to discard that service.
But bigger issue for me, and i think others, is variables.
The mentioned project rely heavily on external APIs, and i need to be able to switch between if the DEV env/services use prod or DEV/TEST data via the external API. I therefore have that as a variable.
But then whenever i sync i have to make sure i don't accidentally overwrite prod variable to use the external APIs DEV data.
I know you could argue that i could handle that in code by looking at the built in railway variables, but i think its not optional to have much logic based on a platform/vendor variable like that.
a month ago
I agree that we need some sort of control to prevent accidentally overwriting environment variable values across environments. I thought using shared variables would prevent this because they use the refs, but noticed that it still overwrote my prod values with dev values when I was syncing other services.