Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List all the configuration properties onthe website #1350

Closed
lburgazzoli opened this issue Jun 15, 2020 · 3 comments · Fixed by #1389
Closed

List all the configuration properties onthe website #1350

lburgazzoli opened this issue Jun 15, 2020 · 3 comments · Fixed by #1389
Assignees
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@lburgazzoli
Copy link
Contributor

Similar to https://quarkus.io/guides/all-config

@lburgazzoli lburgazzoli added the documentation Improvements or additions to documentation label Jun 15, 2020
@davsclaus
Copy link
Contributor

Yeah we have this Camel JIRA that is related to this
https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-15190

@davsclaus
Copy link
Contributor

@ppalaga ppalaga self-assigned this Jun 19, 2020
ppalaga added a commit to ppalaga/camel-quarkus that referenced this issue Jun 19, 2020
oscerd added a commit that referenced this issue Jun 20, 2020
Fix #1350 List Quarkus configuration options on extension pages
@ppalaga
Copy link
Contributor

ppalaga commented Jun 22, 2020

The linked PR does not add an all-config style page, it rather lists the options relevant for the given extension on its page.

Here is an example: https://camel.apache.org/camel-quarkus/latest/extensions/core.html (There are some visual and procedural glitches there, for which I am going to file folow-ups)

Do we still want an all-config style page?

@ppalaga ppalaga added this to the 1.0.0-CR3 milestone Jul 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants