pulpcore provides “Master models” which provide fields common to all plugins, and then plugins subclass to create a “Detail model” which is the concrete model plugin users will interact with and can define content-specific fields there too. For example pulpcore provides
Remote which provides these fields. Then plugin writers can subclass to make a
RpmRemote or a
There is a general need to have UI components in front of Pulp APIs. For example the galaxy_ng team wants to have UI components talk to various Pulp APIs. They use React + Patternfly
What if we create generic React + Patternfly UI components representing pulpcore’s “Master models”, e.g. Remote, Repository, Content, Distribution, etc. Then these can be “customized” into detail components, e.g. RpmRemote or a CollectionRemote as derivative React + Patternfly components.
These components aren’t a UI themselves, but they are the building blocks of one, allowing others to use these base components to create various UIs on top of the Pulp APIs.
Please share your thoughts on this idea. Also please share if you would like to be involved maybe as a tester, contributor, end-user, etc.