Add build-time properties to the catalog

Open
#564 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

No repository file or test is named in the issue. Start by locating the catalog and kit-building entry points, then compare their handling with the Quarkus all-config page linked in the report; done means build-time-only Quarkus properties are represented in the catalog and considered when building the kit.

Written by the indexing model from the issue text.

Description

I've faced issues when trying to configure things (like Quarkus security) that contain build-time-only properties.

E.g. quarkus.security.users.embedded.enabled=true is a property that is not processed at runtime, so it's ignored by the integration. In terms of Camel K, it needs to be taken into account when building the kit.

This information exists somewhere, since this page has been built: https://quarkus.io/guides/all-config#quarkus-elytron-security-properties-file_quarkus-elytron-security-properties-file-elytron-security-properties-file

Dominant language
Java
Stars
69
Forks
50
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from apache/camel-k-runtime

All issues in apache/camel-k-runtime

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.