As a Project Admin, I should be able to:
- Mark repository as private/public. Only the repository marked as public will be "shareable".
- with specific project/s
- with all projects
- pattern-based by project prefix
- Attach public repository from the other project to my project and manage it the same way as any other "private" repository
- get list of "public" repos shared by other projects, including Environment
- attach the shared repo to my project
- Environments - need to validate that the environments are consistent across the projects (today it is not the issue, since we have 2 OOTB envs only, but in the future we need to propagate the environment as well if needed)
- The sharing means full ownership, include delete by Project Admin
Repo prefix: will remain the original one (not to break other automations), but needs to be associated with the other projects as well. E.g. the same repo can have multiple aliases: rtfact-docker-remote, xray-docker-remote, pipln-docker-remote, etc.
- Support for sub-path in the shared repository: not share the entire repository, but sub-path in the repo structure (e.g. namespace: repo docker-local, namespace jfrog can be translated to docker-local/jfrog/*, namespace: nil will be translated to docker-local)