[FEATURE REQ] Workspaces Support

[dannythomas13]

I must admit I don't know too much about them but I wonder what effect it will it have on this toolkit and whether there are changes needed within a roadmap to support them?

[waelkdouh]

Currently workspaces are not supported by apiops as it's still in preview. Once Workspaces is out of preview it will be part of apiops. We can't promise any timeline but rest assured it will come down the line. In the meantime if you have ideas on how you feel the best implementation would look like we would love to hear your opinion as we are still going through the planning phase.

[dannythomas13]

I actually don't see it as being too dissimilar, essentially we will of course want to extract and create workspaces within an instance and then for each workspace pretty much do what we do now i.e. extract products and api's but now will be scoped to a workspace rather than an instance

[waelkdouh]

And would you rather see all the workspaces artifacts extracted to the same repository or would you rather use multiple repositories?

[dannythomas13]

Excellent question - I didn't think of that but I guess keeping in spirit of supporting separate teams would mean having sperate repositories, one for the root and then additional ones for each workspace - that way it's much easier to isolate code and manage permissions on a granular level

[waelkdouh]

Thanks for the feedback. And please keep using this thread if you have any other ideas as we are actively planning for this feature.

[shawnmurtagh]

Seems to me like the work-space level resources (names values, backends, policy fragments) and workspace-scoped policies are the main value that workspaces could add to APIOps.

[waelkdouh]

Apis as well. But remember there are global level artifacts and other that are unique to the workspace. Also workspaces will be optional so the tool has to adapt to that as well. Once we figure out all the details we will share back the details here and update the docs.