Project id: bffee644-ec55-4122-9e19-fee98c401647

bump

This is the desired behavior, each service is representative on one another across environments, but the service instance can have different settings

Correct, different settings, except the name. Also, when moving services around on the canvas, let's say I move the frontend service, it moves it on all the environments, which can mess things up since on production environment I have more services, like replicas, so the canvas gets messed up

Yep service positions are also the same accrors all environments, that would also be the intended behaviour

The only way I can think of uncoupling them would be to clone the service in that environment and just delete the old one, is that right?

How do I link services from one environment to another then?

You can't, thats is how it has been designed, can you tell me why you need to?

I must be missing something, is this behavior in the docs and I missed it? I have backend and frontend across all 3 environments dev, staging, production. If I add another service on dev, let's call it queue service, how can I link that with the same service on staging and production? Or is this behavior only available for backend/frontend named services?

you would sync that service to your desired environment

ah ok, somehow I never used the Sync option

I'll have to go look at the docs

now it all makes sense, thanks 🙂