We're trying to understand the intended Railway workflow for managing multi-environment projects.

Current setup:

• Multiple environments (Production, Development)
• Doppler manages environment variables
• Doppler syncs variables into Railway services
• No Railway Shared Variables are configured

The issue we're running into is when we want to add a new service to all environments.

Example:

1. We create a new service in Dev.
2. Doppler syncs the environment variables into that service.
3. We then use Railway Environment Sync to bring that service into Production.
4. Railway includes all service variables as part of the sync.

This means every time we sync the service, we also have to manually review and remove/discard the variable changes before deploying.

A few questions:

1. Is there currently a way to sync/copy services between environments without including service variables or manually needing to remove them?
2. Is there a recommended workflow for teams using Doppler (or another external secrets manager) across multiple Railway environments?
3. When adding a new service to an existing project with multiple environments, what is the recommended way to propagate that service to all environments while preserving each environment's own variable set?
4. Is Environment Sync intended to be used for this use case, or is there another Railway-native workflow that is preferred?

At the moment it feels like adding a service to an existing multi-environment project requires manually removing variable changes during every environment sync, and we're wondering if we're missing a better approach.