-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Public interface for getting expected actions on pulp #119
Comments
negillett
added a commit
to negillett/ubi-population-tool
that referenced
this issue
Sep 6, 2019
This commit adds a new API which generates a list of the associations and unassociations expected to be performed by Pulp for each repo in each UBI configuration. Fixes release-engineering#119
negillett
added a commit
to negillett/ubi-population-tool
that referenced
this issue
Sep 12, 2019
This commit adds a new API which generates a list of the associations and unassociations expected to be performed by Pulp for the given configuration. Fixes release-engineering#119
negillett
added a commit
to negillett/ubi-population-tool
that referenced
this issue
Sep 23, 2019
This commit adds a new API which generates a list of the associations and unassociations expected to be performed by Pulp for the given configuration. Fixes release-engineering#119
negillett
added a commit
to negillett/ubi-population-tool
that referenced
this issue
Sep 23, 2019
This commit adds a new API which generates a list of the associations and unassociation expected to be performed by Pulp for the given configurations. Fixes release-engineering#119
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: