Deploy app with latest license file when version is several releases behind

We have a customer who is very deliberate with their upgrade cycles. We reference the license fields at deploy time (not runtime via sdk.) We recently updated a license field for them and asked them to sync their license. They did that but it wasn’t immediately obvious how to redeploy the current version of the application using the latest license.

The currently deployed version is several releases behind the latest. When we redeploy the current version, the newly sync’d license is not used. When we make a config change in the current version and deploy, the newly sync’d license is not used. Should it be possible to redeploy a release that is several releases behind using the latest sync’d license file?

I haven’t found a CLI command to do it. Am I not seeing it? I would like to avoid the download+remove+install method described here: How can I replace the customer license on an application?

I just found this which seems to describe our same situation. Delete sequence in kots admin console

The author of the original post never responded but I can tell you making a config change did not help.

Hi @credo-nate,

I can see the workaround works fine for me. This is what I did:

  • Make a trivial config changes in current deployed version, deployed the app
  • Click Sync license and note that the latest license is based on current deployed app version.
  • Deploy the version with the new license

In below screenshot, you can see that I have old release with hash fe06bcf and newer release of 37442e7, after making config change, deploy and sync license again, it is now based on version fe06bcf instead of later release 37442e7

I am on KOTS v1.122.1, please let me know how it goes.