Summary
Ubipop should provide public method for getting expected unassociations and associations that should happen on pulp for ubi repos. Information returned will be used in pub (or other clients) which will run these un/associations and save all received items to push item list.
Input of new method should be content set labels or repository ids.
Output - expected actions on repositories for rpms, srpms, modulemds and modulemd_defaults.
Issue Type
Current behavior
There is no way how to get expected pulp actions out of ubipop now.
Desired behavior
- ubipop provides public method for getting expected actions on pulp
- ubi won't execute these actions but it'll leave them for caller
- public methods created are properly documented
Use case
Client application needs to know what unit should be un/associated, so it can execute proper actions on pulp.
Additional Information
In ubipop there are already methods for calculation of expected pulp actions but it's not exposed publicly and it's implemented inside ubi repos population process.
Summary
Ubipop should provide public method for getting expected unassociations and associations that should happen on pulp for ubi repos. Information returned will be used in pub (or other clients) which will run these un/associations and save all received items to push item list.
Input of new method should be content set labels or repository ids.
Output - expected actions on repositories for rpms, srpms, modulemds and modulemd_defaults.
Issue Type
Current behavior
There is no way how to get expected pulp actions out of ubipop now.
Desired behavior
Use case
Client application needs to know what unit should be un/associated, so it can execute proper actions on pulp.
Additional Information
In ubipop there are already methods for calculation of expected pulp actions but it's not exposed publicly and it's implemented inside ubi repos population process.