New question, looking through the `maintained-apps...
# fleet
m
New question, looking through the
maintained-apps
and wondering how it handles multi-versions, for example: https://github.com/fleetdm/fleet/blob/main/ee/maintained-apps/outputs/visual-studio-code/windows.json this has multiple versions and it appears as in theory the
versions
key can handle it...but the JSON isn't being appended it's being replaced...which makes me curious how FleetDM handles multiple versions of the same software. If anyone knows off the top of their head, that would be helpeful. If not, all good! I'll go find a random MSI to test 😛
👀 1
k
Essentially it will always write the latest version of the app, replacing anything older. At least that's my understanding of it.
m
yeah, I just happened to be testing as you responded. Testing with Notepad++. I grabbed 8.8.6 and 8.8.7 installer exe and when trying to add both, it errors on one. This feels like a miss because, for example, we use ProSeries and we have like 7 years of installers. We have to have the correct year for each one cause the IRS tax code for that year is bundled so when opening previous year tax returns.
for example, this is one of our workstations (sorry for the clashing background image). You can see we have software installed all the way back to 2015.
k
Oof.
m
Yup, I will need to test and see if the ExtractMetadata calls actually pull the generic name or versioned name.
k
It looks like we have an open feature request for this already https://github.com/fleetdm/fleet/issues/25407
I went ahead and added a link to this thread as well as some context in a comment.
m
Thank you. For QuickBooks, it looks like it pulls the the generic name so without any way to edit the title (https://github.com/fleetdm/fleet/issues/24802) it seems like 25407 will be a hard blocker unless I modify the title myself in the PE.
k
It looks like 24802 is at least planned, although it hasn't been assigned to a release yet.
m
Yeah it looks like its been flip flopping for the last year sadly as a part of the parent epic. I'll guess we'll have to wait (which is fine), I'll probably hack together a script when I need it to modify the
ProductName
value to trick the metadata extractor and allow multiple versions.