Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-6953

Quarkus CLI output extension versions for non-existing offering

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      1. Create two yaml configs:
      experimental.config.yaml

      registries: 
      - testingregistry: 
          descriptor: 
            artifact: testingregistry:quarkus-registry-descriptor::json:1.0-SNAPSHOT
          maven: 
            repository: 
              url: https://registry-3-27-1-redhat-00003.apps.int.gpc.ocp-hub.prod.psi.redhat.com/maven
          offering: unknown-offering
      - registry.quarkus.redhat.com
      - registry.quarkus.io
      

      control.config.yaml

      registries: 
      - registry.quarkus.redhat.com
      - registry.quarkus.io
      

      2. Output extensions for experimental config. It contains version 3.27.1 from the registry, marked with "unknown-offering"

      $ quarkus extension list --support-scope --stream 3.27 --config=experimental.config.yaml -s=rest-jackson
      Looking for the newly published extensions in registry.quarkus.redhat.com
      Current Quarkus extensions available: 
      
      ✬ ArtifactId                                         Extension Name                                     Version                   Support scope
      ✬ quarkus-rest-jackson                               REST Jackson                                       3.27.1.redhat-00001       
      
      To get more information, append `--full` to your command line.
      
      To list only extensions from specific category, append `--category "categoryId"` to your command line.
      

      With the control config, cli outputs version 3.27.0:

      $ quarkus extension list --support-scope --stream 3.27 --config=control.config.yaml -s=rest-jackson
      Current Quarkus extensions available: 
      
      ✬ ArtifactId                                         Extension Name                                     Version                   Support scope
      ✬ quarkus-rest-jackson                               REST Jackson                                       3.27.0.redhat-00001       
      
      To get more information, append `--full` to your command line.
      
      To list only extensions from specific category, append `--category "categoryId"` to your command line.
      

      Cli version is 3.27.1

      Show
      1. Create two yaml configs: experimental.config.yaml registries: - testingregistry: descriptor: artifact: testingregistry:quarkus-registry-descriptor::json: 1 . 0 -SNAPSHOT maven: repository: url: https://registry- 3 - 27 - 1 -redhat- 00003 .apps.int.gpc.ocp-hub.prod.psi.redhat.com/maven offering: unknown-offering - registry.quarkus.redhat.com - registry.quarkus.io control.config.yaml registries: - registry.quarkus.redhat.com - registry.quarkus.io 2. Output extensions for experimental config. It contains version 3.27.1 from the registry, marked with "unknown-offering" $ quarkus extension list --support-scope --stream 3.27 --config=experimental.config.yaml -s=rest-jackson Looking for the newly published extensions in registry.quarkus.redhat.com Current Quarkus extensions available: ✬ ArtifactId Extension Name Version Support scope ✬ quarkus-rest-jackson REST Jackson 3.27.1.redhat-00001 To get more information, append `--full` to your command line. To list only extensions from specific category, append `--category "categoryId" ` to your command line. With the control config, cli outputs version 3.27.0: $ quarkus extension list --support-scope --stream 3.27 --config=control.config.yaml -s=rest-jackson Current Quarkus extensions available: ✬ ArtifactId Extension Name Version Support scope ✬ quarkus-rest-jackson REST Jackson 3.27.0.redhat-00001 To get more information, append `--full` to your command line. To list only extensions from specific category, append `--category "categoryId" ` to your command line. Cli version is 3.27.1
    • ---

      According to quarkus docs[1], when offering is provided for the registry, Quarkus CLI should output only extensions which belong to that offering. It is reasonable to assume, that for non-existing offering, not extensions are shown. This assumption doesn't work for Quarkus 3.27.1.CR3.

      [1] https://quarkus.io/guides/extension-registry-user#limiting-extension-catalog-to-an-offering

        1. settings.xml
          3 kB
          Fedor Dudinskii

              olubyans@redhat.com Alexey Loubyansky
              rhn-support-fdudinsk Fedor Dudinskii
              Fedor Dudinskii Fedor Dudinskii
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: