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
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. "
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?
"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. "
There is no easy way to do this. We have the same issue and I'd think its a
pretty basic use case!
From memory, there is a compare API endpoint but that will only report on
errata differences between two content view versions.
We do this by grabbing all packages / puppet modules (as that's the two
bits we're interested in) in the two content view versions and diff'ing.
Its slow. Really slow - like 15 minutes or so slow.
···
On Tuesday, August 1, 2017 at 12:59:02 AM UTC-4, Lachlan Musicman wrote:
>
> On 1 August 2017 at 14:14, Lachlan Musicman > wrote:
>
>> 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?
>>
>
>
> After some banging away, I found this:
>
> hammer package list --organization-id 1 --content-view-id 25
> --content-view-version 25 --repository-id 2
>
> returned a list, but only after I'd tried
>
> hammer package list --organization-id 1 --content-view-id 25
>
> then
>
> hammer package list --organization-id 1 --content-view-id 25
> --content-view-version 25
>
> It would be great to be able to iterate over the included repo versions
> without necessarily needing to know what they were - so that
>
> hammer package list --organization-id 1 --content-view-id 25
> --content-view-version 25
>
> returned a list of packages of all the repos in it? Am I missing something
> simple?
>
> 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
>
>
Yeah - even just that command I found took a long time to process, and that
CV has 4 Products in it, so it might be quite long.
I woke up at 3am wondering if I should teach myself ruby and build a module
that interrogates the database directly, but then I remembered my todo list.
On the "I wish" pile.
Thanks for the feedback.
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. "
There is no easy way to do this. We have the same issue and I’d think its
a pretty basic use case!
From memory, there is a compare API endpoint but that will only report on
errata differences between two content view versions.
We do this by grabbing all packages / puppet modules (as that’s the two
bits we’re interested in) in the two content view versions and diff’ing.
Its slow. Really slow - like 15 minutes or so slow.
On Tuesday, August 1, 2017 at 12:59:02 AM UTC-4, Lachlan Musicman wrote:
On 1 August 2017 at 14:14, Lachlan Musicman dat...@gmail.com wrote:
Hola,
Is there an easy way to get a comprehensive list of package changes
between two CV versions or two Lifecycle Environment versions?
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?
hammer package list --organization-id 1 --content-view-id 25
then
hammer package list --organization-id 1 --content-view-id 25
–content-view-version 25
It would be great to be able to iterate over the included repo versions
without necessarily needing to know what they were - so that
hammer package list --organization-id 1 --content-view-id 25
–content-view-version 25
returned a list of packages of all the repos in it? Am I missing
something simple?
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. "
"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. "
"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. "
I'll take a look at the RFC/etc - but if you have some scripts I could look
at that would be appreciated too.
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. "
"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. "
