🎸Provide a custom script to determine whether an application should be installed or updated

[Patagonia121]

As an admin, I want to provide a custom script to determine whether an application should be installed or updated, enabling the deployment of applications with complex requirements beyond a simple version comparison.

Customer note:

Partially solved for initial installation by pre-install query, but no native support for updating apps means this isn’t a full solution.

[noahtalerman]

@marko-lisica, I think this, and several other app management requests from the customer, are worth digging into w/ the customer on today's call.

I think let's ask the if pre-install condition (query) + edit software (#20404) solves this workflow.

[Patagonia121]

@noahtalerman just curious, but did y'all get to ask if pre-install condition (query)+ edit software will solve for their workflow?

[noahtalerman]

did y'all get to ask if pre-install condition (query)+ edit software will solve for their workflow?

Hey @Patagonia121, we haven't confirmed this yet.

I think let's ask on our next call w/ customer-reedtimmer

[noahtalerman]

From design review on 2024-08-14:

We think this customer-reedtimmer feature request is to address the specific problem of installing a new version of a custom, in-house package.

We think this package (.pkg) is a "component" package. Here's docs on types of .pkgs.

Today, Fleet can extract the version from "product" packages. Not "component" packages.

Possible solutions:

• Improve version extraction to get version from component packages
• Customer repackages their package as a product package
• Make the version field an editable field in Fleet

Noah: Why are they using a component package instead of a product package?

@marko-lisica please let me know if anything in this summary looks wrong. Thanks!

[noahtalerman]

We think this customer-reedtimmer feature request is to address the specific problem of installing a new version of a custom, in-house package.

Noah and Marko: This can be address w/ #19551: Policy to check if the in-house package is installed and if it's an older version (based on checksum) + upload in-house package to Fleet.

Marko: Version isn't visible in Fleet today because of the problem described here.

Noah: Also we have the problem of not being able to edit a package (upload a new version). Adding that in this story: #20404

• Today you'd have to delete and re-upload the new package.

[noahtalerman]

As an admin, I want to provide a custom script to determine whether an application should be installed or updated, enabling the deployment of applications with complex requirements beyond a simple version comparison.

Heads up @Patagonia121 I think we can close this issue because the above workflow will be feasible when we ship #19551

That said, I think we should get customer-reedtimmer's feedback on the #19551 to get their thoughts on future improvements.

[fleet-release]

Script dances, discerns,
App's life cycle in its hands,
Cloud city's heart learns.