Time to publish new view
I'm currently working with our SOE and as part of it we are deploying a custom rpm as a Product.
So the iterations of the rpm are frequent.
And as I'm typing I'm coming up with a solution, but if I up the release version of the rpm, and add it to the repo I have to publish a new content view to incorporate it in a new build.
So the solution is to not reversion the rpm - simply delete the old and upload the revised but not reversioned rpm and that's probably OK, but my original question remains - and that is whether there is a method for adding a new version rpm to a published view or whether that breaks the logic.
Publishing a new version content view takes a fair bit of time.
Responses
Expert
1058 points
I don't get what you mean by "simply delete the old and upload the revised but not revisioned rpm" ... you are published new content to Library of your custom pulp managed repo in a lifecycle environment ... so long as you aren't needing to promote the content through various stages of a lifecycle environment ... if your content hosts are pointing to library, then you aren't doing anything wrong. If you are leveraging capsules you will still need to sync the environment to the capsules for hosts pointing to them for content delivery ... but if you just have a satellite and integrated capsule (management head) just uploading new RPMs to library is correct.
We often don't promote out of library for dev systems and point them to library rather than have to incur the overhead of promoting everything to a different stage.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.