We are currently splitting a big project into smaller pieces (modules). Each module project contains a few source files, lets call them X and Y for now, although there can be more. This module is not a standalone compilable project, but rather just the source for this piece of the full project.
A module can then be shared into one or more projects. So for example say we have the following two projects and module:
Code: Select all
Project 1 Project 2 Module
A E X
B F Y
C G
D X
X Y
Y
We want to instead deny everyone checkout access (or modification access) to XY, from within Project 1.
This will be the case for most projects, but we also have a project that tests the module, from which we would like to be able to allow modification to XY. The idea is that to the programmer there will be a very explicit division between "local" code (that they own) and "shared" code (that they must be very careful to ensure compatibility with).
So my question is: is there a way to set file-level access permissions with shared files in Vault? Or on the flipside, is there a better way to do what we're trying to do?
Thanks for reading!