Recent posts

#21
coArchi / Re: Model element RBACs
Last post by SMaric - January 31, 2025, 15:43:02 PM
Ok thanks for letting me know
#22
coArchi / Re: Model access controls
Last post by Phil Beauvoir - January 31, 2025, 15:42:40 PM
Quote from: SMaric on January 31, 2025, 15:40:01 PMOk thanks for your prompt response
Is this likely to be something that is on the coArchi Development Roadmap


No, this is not something that I will be implementing as it would require fundamental changes to how a model references objects.
#23
coArchi / Re: Model element RBACs
Last post by Phil Beauvoir - January 31, 2025, 15:41:11 PM
Hi, no this level of access is not supported in coArchi. I think some users manage this through agreeing best practice and using branches.
#24
coArchi / Re: Model access controls
Last post by SMaric - January 31, 2025, 15:40:01 PM
Ok thanks for your prompt response
Is this likely to be something that is on the coArchi Development Roadmap

#25
coArchi / Model element RBACs
Last post by SMaric - January 31, 2025, 15:38:08 PM
Hi
Is it possible to set RBACs on my model (or parts of it)
Am thinking along the lines of one team drawing up some application/service views which would be REAd-Only available to other teams

Thanks
#26
coArchi / Re: Model access controls
Last post by Phil Beauvoir - January 31, 2025, 15:33:27 PM
Hi, no this isn't possible either in coArchi or when accessing models locally. All Elements in a model are local to that model.

Phil
#27
coArchi / Model access controls
Last post by SMaric - January 31, 2025, 15:31:22 PM
Hi
Is it possible to reference elements from Model_A inside Model_B
where elements from Model_A would be READ-ONLY within Model_B

Model_A & Model_B would be in separate Bitbucket projects/Repos

Thanks
#28
coArchi / Re: CoArchi Model Import
Last post by Gemini - January 30, 2025, 20:51:58 PM
Thanks for your detailed replies.
I understand that each model is stored in its own Git repository with the model/ root structure. This works well for individual projects, but I'm looking for a way to organize multiple models efficiently while keeping each in its own repository.

Would it be possible to manage multiple model repositories under a parent repository—for example, by using Git submodules? That way, each model stays in its own Git repo, but everything is grouped together for easier access and management.

Would this approach work smoothly with coArchi, or are there any potential pitfalls I should be aware of? Are there other recommended ways to handle multiple repositories while keeping things structured and easy to work with?
#29
coArchi / Re: CoArchi Model Import
Last post by Jean-Baptiste Sarrodie - January 30, 2025, 20:04:24 PM
Hi,

Quote from: Gemini on January 30, 2025, 19:22:46 PMWhy?

Because in the context of coArchi, git technology should be considered a black box managed only by the plugin. The same way you wouldn't expect to be able to change the internal database schema of a commercial software, and you're aware that attempting to do so would brake the software, storing other files into the git repository assigned to the model or using manual git commands on it would most certainly lead to a model corruption.

In short, the fact that coArchi uses a known and open storage system doesn't allow you to do silly things with it (for your own "safety").

Regards,

JB
#30
coArchi / Re: CoArchi Model Import
Last post by Phil Beauvoir - January 30, 2025, 19:27:46 PM
Quote from: Gemini on January 30, 2025, 19:22:46 PMWhy?

It's internally coded that way, and it won't change. However, the good news is that coArchi is free and open source so you can fork the code and change it in your own fork, if you wish.