redhat-developer / redhat-developer/vscode-quarkus

Wrapper extension leads to unknown properties

Open
#256 0 comments 0 reactions 1 assignee View on GitHub

@angelozerr is already working on this.

Since Aug 6, 2020.

bug
Dominant language
TypeScript
Stars
79
Forks
31
Avg merge
12h 51m
Merged PRs (30d)
6

Description

VSCode Quarkus Extension 1.5.0

I'm using the Quarkus wrapper extension quarkus-openshift inside my pom.xml which brings implicit the extensions quarkus-kubernetes and quarkus-container-image-s2i.

   ...
    <dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-openshift</artifactId>
    </dependency>
   ...

In my application.properties file the properties of those implicit extensions are marked as unknown (yellow underlined). My expected behavior would be that all properties of such implicit extensions are known properties too.

# marked as unknown
quarkus.s2i.base-jvm-image=registry.access.redhat.com/ubi8/openjdk-11
quarkus.s2i.base-native-image=quay.io/quarkus/ubi-quarkus-native-binary-s2i:20.0.0
quarkus.s2i.native-arguments=-Xms8M -Xmx8M -Xmn8M

# known
quarkus.kubernetes-client.trust-certs=true
# marked as unknown
quarkus.kubernetes.deployment-target=openshift

# marked as unknown
quarkus.openshift.expose=true
quarkus.openshift.labels.app=quarkus-demo

If I explicit add those extensions to the pom.xml everything work fine again.

   ...
    <dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-openshift</artifactId>
    </dependency>
    <dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-kubernetes</artifactId>
    </dependency>
    <dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-container-image-s2i</artifactId>
    </dependency>
   ...

Reproducable with my demo project:
https://github.com/haraldatbmw/quarkus-openshift-deployment

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.