Better tooling experience for Quarkus project info and update

[ia3andy]

part of #29000

Allow to:

• Fetch recipes from "io.quarkus:quarkus-update-recipes:LATEST
• Filter to keep only recipes matching the current project version and target version
• Generate the project update recipe yaml file in a temp directory, it includes:
  • the applicable recipes from the update artifact
  • the Quarkus version update commands

Prepare the tooling update/info commands as discussed on Zulip:

quarkus info should:

• Display project information
• Verify versions health (platform and extensions)
• Hint on how to repair if needed (print command) => quarkus update -V [current-quarkus-version]
• Check for update (print command if needed)

quarkus update should: Suggest recommended project updates with the possibility to apply them.

quarkus -V --version: version of the CLI (not project related),
quarkus version: hide and forward to quarkus -V

I've added the recipe generation to the update command, we still need to:

• @aloubyansky: Change the info command implementation to do the above
• @aloubyansky: Fix the bits of code with TODO ALEXEY:
• @aloubyansky: Change the update command to print the instructions to update the project versions manually and say that the script also includes other stuff (packages migration, ...)
• @ia3andy: Print command to apply the recipe script

qss --help


Usage: quarkus [-ehv] [--verbose] [-D=<String=String>]... [COMMAND]
Options:
  -h, --help            Display this help message.
  -v, --version         Print Cli version information and exit.
  -e, --errors          Display error messages.
      --verbose         Verbose mode.
  -D=<String=String>    Java properties

Commands:
[...]
  info                    Display project information and verify versions
                            health (platform and extensions).
  update                  Suggest recommended project updates with the
                            possibility to apply them.
  completion              bash/zsh completion:  source <(quarkus completion)

[aloubyansky]

FYI @ebullient

[ia3andy]

@aloubyansky @maxandersen I need to print the open-rewrite command, but I am not sure what version to put? Maybe the version should be provided by the quarkus-update-recipe jar as metadata?

[maxandersen]

Version of what ? Openrewrite? Put a hardcoded version that cli knows about. The platform won't know which is better.

Users can change it when running the actual command if need be.

Ps. Would be great with just a little bit of context in the pr especially with this many changes what this pr is trying to do (and possibly what it doesn't cover yet if the #29000)

[ia3andy]

Version of what ? Openrewrite? Put a hardcoded version that cli knows about. The platform won't know which is better.

Users can change it when running the actual command if need be.

Ok 👍

Ps. Would be great with just a little bit of context in the pr especially with this many changes what this pr is trying to do (and possibly what it doesn't cover yet if the #29000)

@maxandersen this was still a draft, I pushed ASAP to allow Alexey to do his part. I've updated the description with everything.

[ia3andy]

Just a small thing we could change the quarkus update to have --latest, this way:

• quarkus update would keep the current platform version but update/fix the extensions
• quarkus update --latest would update to the latest quarkus

qss update --help

Suggest recommended project updates with the possibility to apply them.

Usage: quarkus update [-eh] [--per-module] [--refresh] [--[no-]registry-client]
                      [--verbose] [--config=CONFIG] [-D=<String=String>]...
                      [-S=targetStreamId | -P=targetPlatformVersion | -L]

Options:
[...]

Target Quarkus version:
  -S, --stream-id=targetStreamId
                        A target stream id, for example:
                          2.0
  -P, --platform-version=targetPlatformVersion
                        A specific target Quarkus platform version, for example:
                          2.2.0.Final

  -L, --latest          Use the latest Quarkus platform version

[aloubyansky]

I still don't like the --latest idea. IMO, what is proposed by --latest would be the primary use-case, not the other way around.

[maxandersen]

How about --stream to indicate stay within the stream you are in ?

[quarkus-bot]

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.