Shared environments across workspaces

I have a problem trying to keep same environment values across every workspace I have. Hosts and ports of our test environments (dev, staging1, staging2, staging3, etc.), test account logins, a few common values for all these services.

Today those variables are copied into all 20 of my workspaces. When a test environment moves to a new host or some basic test parameters changes, I need to edit the same value in all those places

What I would like is one environment above the workspace level, visible from every workspace, which a workspace environment can still override. With directory sync it would be a file in the repo, next to the workspace folders:

api-collections/                 git repo, directory sync
|
|-- shared/                      what I am asking for
|   |-- yaak.shared.staging1.yaml       host, ports, test accounts
|   |-- yaak.shared.staging2.yaml
|   +-- yaak.shared.dev1.yaml
|
|-- orders-api/                  workspace, one service
|   |-- yaak.wk_a1b2c3d4e5.yaml
|   |-- yaak.ev_f6g7h8i9j0.yaml        only what is specific to this service
|   +-- yaak.rq_*.yaml
|
|-- payments-api/                workspace, one service
|   +-- ...
|
+-- pricing-service/             workspace, one service
    +-- ...

Resolution order would be shared environment, then workspace base environment, then sub-environment, so a service can still override a shared value when it has to. Like, I change a host in one file, commit, other developers pulls, all 20 workspaces are correct.

Other tools all have this level like postman, insomnia, hoopscotch bruno global envs sit in the workspace, above collections (because in yaak “workspace” is like a postman collection as I undestand) So any edit in that global envs applies to all nested collections.

(I don’t want to merge everything into one big workspace. That would prevent me from opening multiple instances of yaak for each of those workspaces (services). When I packed those workspaces into one, opening two instances of yaak on that workspace meant that every change made to a request or folder was visible on the other open yaak instance. By opening each service as a separate workspace, I avoid this behaviour)