Extending Cloud Workspaces

[byoung]

I would like to extended one of my cloud workspaces from another in the same account, but was unable to find a raw https url to get the dsl from the primary workspace. Does the cloud offering have raw dsl https links to support workspace extensions? I tried to create a private link but that only gives me the html rendering of the workspace.

[simonbrowndotje]

The recommended approach for workspace extension is to have all of the DSL files locally on your computer (parent and extended workspace), and use the Structurizr CLI push command to push them to the cloud service.

[byoung]

That will work for technical members of our team as we're all running docker/git to edit and maintain files, but my hope was that less technical members of our team could use the cloud DSL Editor online to do process modeling in a "scratch" workspace that is an extension of our "core" models. Engineers could then integrate any finalized process diagrams into source code control enabling the non-technical team members to focus on the process modeling vs running docker and learning git.

Ideally, making a private link would create a link to the raw DSL in addition to the html page we get today. This would enable us to use !include and workspace extends for any other workspace that needs to include the "core" models. If this isn't something you want to add as part of the link sharing feature, we'll just have to pump a copy of the DSL into some file store as part of the GitHub action that publishes everything.

Thanks for making such an amazing set of tools and the C4 concept itself! Our non-technical teams members loved it so much they asked to get in on the C4 action too -- hence this request.