Torsten Jaeschke
Torsten Jaeschke
From my side I also would say yes.
Just some thoughts. I think we still need one general Nexus user to use the proxy repos. This would be the developer user, but we should restructure the rights, so...
We will go for the repository target option. This seems to be the most mnimal invasive change according to the logic implemented.
https://help.sonatype.com/repomanager3/configuration/repository-management#RepositoryManagement-ContentSelectors
> I think devleoper used should not be used, > by default everyone that can login to nexus can read all artifacts, if project needs private access then block everyone...
We need to create content selectors, privileges and roles and specific nexus users. To do this, we need a user, that is only able to run a script located on...
After discussing with @michaelsauter there are some things that have to be clarified, before we are able to get this running. The current implementation would only capture Maven repositories. There...
Another point of evaluation is to take changes in the general repo structure in account. Questions we have to answer: * What happens, if there are repositories added? * What...
@michaelsauter There are also questions about the current repository usage. Would you please calrify the usage and provide informations about it, so I'm able to adopt it?
> Are we able to provide a specific user with all rights, the current developer user has? I would purpose, we add the OpenDevStack-Developer role to the specific user and...