Hola, Is there an easy way to get a comprehensive list of package changes between two CV versions or two Lifecycle Environment versions?
I'm looking into the hammer help now, and have found http://projects.theforeman.org/issues/20046 which suggests that a per CV package list is available. I could wrap up a couple of those in a bash script I guess? I presumed this would be a solved problem - being able to report on what packages will change should the LCE be promoted to the new CV version. That's the actual problem I'm trying to solve - am I doing it wrong again? Cheers L. ------ "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics is the insistence that we cannot ignore the truth, nor should we panic about it. It is a shared consciousness that our institutions have failed and our ecosystem is collapsing, yet we are still here — and we are creative agents who can shape our destinies. Apocalyptic civics is the conviction that the only way out is through, and the only way through is together. " *Greg Bloom* @greggish https://twitter.com/greggish/status/873177525903609857 -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
