Closed MoritzWeber0 closed 1 year ago
Resolved with the implementation of general tool (and types) support.
Needs some testing
Check test models in py-capellambse
Hi,
I tried with the test models from py-capellambse, on a local k3d setup.
I configured 2 models, one for /tests/data/Library Project/Library Project.aird
(library) and one for /tests/data/Library Test/Library Test.aird
(model). A readonly session does not load. My readonly session image is k3d-myregistry.localhost:12345/capella/remote:$version-latest
.
@MoritzWeber0 Any idea what's going on?
Hi,
I tried with the test models from py-capellambse, on a local k3d setup. I configured 2 models, one for
/tests/data/Library Project/Library Project.aird
(library) and one for/tests/data/Library Test/Library Test.aird
(model). A readonly session does not load. My readonly session image isk3d-myregistry.localhost:12345/capella/remote:$version-latest
.@MoritzWeber0 Any idea what's going on?
readonly session logs
Hi @amolenaar,
sorry for the late reply. Can you try whether it works with this fix? https://github.com/DSD-DBS/capella-dockerimages/pull/73
It adds support for entrypoints with a starting /
character.
A library still shows as a model in Capella:
A library still shows as a model in Capella:
In general, this is ok (as long as the "real" project is able to reference the library project).
@MoritzWeber0
It required one small fix: https://github.com/DSD-DBS/capella-dockerimages/pull/97, then it "just works".
@MoritzWeber0
It required one small fix: DSD-DBS/capella-dockerimages#97, then it "just works".
Perfect, thanks for the update! :)
Capella offers a feature called "libraries". With libraries, you can reference and use objects from the library model.
While the library model can be developed independently in another workstream, this is not reflected in TeamForCapella. In TeamForCapella, a library model has to live in the same repository.
In general, there are two different options that are in use: 1) The library should reference a specific fixed version of the library model. This depends on the release management implementation (#231). The model with the represented version should be exported to the corresponding T4C repository. 2) The library should reference the latest version of the library model. In this case, there should be regular backup job that exports the latest Git version to the T4C repository.
Related work: In version 2, there will a flag to mark a model as library. However, there is not much functionality around it.