Using CLI for CI/CD to dynamically push new workspaces #168

johncyril · 2025-02-06T18:02:40Z

johncyril
Feb 6, 2025

I note the previously closed discussion around a similar theme.

There could be a way to ensure the workspace urls remained the same, by making the Id of the workspace a function of the folder that it is in, in source.
e.g. in a pipeline, some kind of numeric hash could be fathomed

 find $(Build.SourcesDirectory)/src -name 'workspace.json' -exec sh -c \
    'dir_name=$(basename $(dirname {})); \
    id=$(echo -n "$dir_name" | md5sum | awk '"'"'{print $1}'"'"' | tr -dc "0-9" | cut -c1-8); \
    docker run -v $(dirname {})/:/usr/local/structurizr structurizr/cli push \
    -url xxxxx -id $id \
    -key xxxxxx
    -secret xxxxxxx
    -workspace $(basename {})' \;

of course the challenge here is that every workspace has its own key and secret.

The answer has previously been "no" to the CLI being able to effectively "upsert" a workspace.
Is this beyond the intended scope of the CLI, or just not feasible?

Would the answer be to use the admin API? If so, would it be acceptable for the admin API to be given an identifier to create a workspace? I see this is not an option, at present. Could this operation be idempotent etc?
Would the recommendation be to use both the admin API and the CLI in such a a scenario?

The alternative option is to manually create every workspace and then place its id, url, key/secretidentifiers, in a file alongside each workspace

It would be really cool to be able to push multiple workspaces from within a pipeline without the need for those steps

Provide feedback

Saved searches

Use 10BC0 saved searches to filter your results more quickly

Using CLI for CI/CD to dynamically push new workspaces #168

Uh oh!

{{title}}

Uh oh!

Replies: 0 comments

Select a reply

Uh oh!

Using CLI for CI/CD to dynamically push new workspaces #168

Uh oh!

johncyril Feb 6, 2025

Replies: 0 comments

johncyril
Feb 6, 2025