Repository navigation
Getting application-inventory.json or similar without booting AMI #4829
Replies: 1 comment
|
Hi @sarahhodne, currently the application inventory is embedded in Bottlerocket AMIs. The team has discussed previously about publishing these as versioned artifacts publicly. If that would address your use case, we can reconsider doing this.
You could also consider using
We generate the inventory at AMI build time given that is when we have a source of truth for exactly what packages are being built into an AMI. If you're looking more so for advisory/CVE reporting, the source of truth there would be our updateinfo.xml at https://advisories.bottlerocket.aws/updateinfo.xml.gz |
Uh oh!
There was an error while loading. Please reload this page.
I'm working on updating our internal runbooks for upgrading our Bottlerocket-based EKS nodes, and as part of that I'm trying to find a way to find a full changelog of the differences.
While we can review the bottlerocket-os/bottlerocket changelog, together with the kernel kit and core kit changelogs, but a lot of changes don't apply to us since they're only for variants we do not use. Going through all the changes and figuring out if they are included in our variant or not is quite time consuming.
We could in theory grab the
/usr/share/bottlerocket/application-inventory.jsonfile from the old and new version, but it looks like to grab it from the new one we need to actually spin up an instance.Is this file (or a similar one) published anywhere else, so we can use that to figure out what packages have actually changes between the version/variant we're moving from/to?
(Alternatively, is it possible to generate it locally without building the whole AMI?)
All reactions