Visibility of profiles would certainly be one solution to the problem, in which the director only has access to repositories that are filtered based on needs for the particular user. What sort of API would you envision allowing a profile to have a restricted set of repositories?
This also raises another question. Is it possible the governer could restrict which repositories are allowed to be added / used in the provisioning system? In a governed model, you may well need to be able to restrict if users can add a specific repository into the provisioning system. And one more. Regarding the visibility of software, instead of orchestrating how repositories query for software, perhaps the governer can be used to filter out software that is not valid for a particular user. This seems to be a potentially more natural fit instead of requiring changing the repository API which is purposefully simple and would be nice to be able to leverage all kinds of repositories even in a model where restrictions may be placed on installed software. Tim On 8/17/07, Pascal Rapicault <[EMAIL PROTECTED]> wrote: > > Rather than passing random tokens to the repository, I would rather have > the repo object query the environment in which it is to pull the data it > needs. > The other thing that would be necessary is the ability to limit the > visibility of repositories to a given "profile", since currently > repositories are global. >
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
