Sharing Variables among Workspaces
My workspaces share many common variables. Having this feature really helps keep things organized and saves time copying and pasting between workspaces.
Windows2025.4.0
My workspaces share many common variables. Having this feature really helps keep things organized and saves time copying and pasting between workspaces.
This is interesting. What sorts of variables are you sharing? Something like a 3rd-party API key that multiple different services need access to?
My use case is almost as you guessed: an expiring token from a 1st party auth endpoint that is used by multiple different services:
When working on services A B or C I need to obtain a token from the central auth service. To obtain a token there are actually two requests that need to be made - 1st to get a token as my own dev user, then a 2nd request using that dev user token to impersonate another user. These two requests (with the 2nd using
response.body.pathto get the token from the 1st request) exist in the Auth workspace.In the workspaces for services A, B, C I want to be able to use that 2nd token, and refresh it as necessary based on the sending behaviour of
response.body.path.There currently exists a boundary between workspaces and I think that’s a good thing. I don’t think simply removing that boundary would be a good move. I therefore would like to see something like a setting to explicitly expose a variable to other workspaces, and ideally that setting would be a list of other workspaces to explicitly expose it to rather than just a boolean to expose it to all workspaces.
I could then create a variable in the Auth workspace that used
response.body.pathand expose that to the workspaces for services A, B and C.Similar requests have been merged into this one. A grouping level above workspaces is being considered, where a group could define variables shared by the workspaces inside it. That would address this without removing the boundary between workspaces.