Generate full Polaris configuration reference docs#3838
Conversation
|
Note to reviewers: all files in the |
8d2b927 to
48b4553
Compare
|
|
||
| {{% include-config-section "flags-polaris_features" %}} | ||
|
|
||
| ### ``polaris.behavior-changes`` |
There was a problem hiding this comment.
FYI there is debate about whether or not this section should be exposed to users:
But for now, I'm including everything.
4e61c72 to
8f0ed02
Compare
| * polaris.service-identity.aws-iam.access-key-id=<access-key-id> | ||
| * polaris.service-identity.aws-iam.secret-access-key=<secret-access-key> | ||
| * polaris.service-identity.aws-iam.session-token=<optional-session-token> | ||
| * |
There was a problem hiding this comment.
This extra line messes up the rendered content – I gave up on investigating why 😅
d1dd7ba to
b79acf7
Compare
snazy
left a comment
There was a problem hiding this comment.
This is great!
Just a few comments, the code changes and site changes LGTM!
|
|
||
| ## Quarkus Configuration Options | ||
|
|
||
| There are many Quarkus configuration properties that can be useful, for example: |
There was a problem hiding this comment.
| There are many Quarkus configuration properties that can be useful, for example: | |
| Some often useful Quarkus configuration properties are listed below. | |
| Please refer to the [Quarkus documentation](https://quarkus.io/guides/) for more details. |
| | `GC_METASPACE_SIZE` | The initial metaspace size. There is no default (example: "20"). | | ||
| | `GC_MAX_METASPACE_SIZE` | The maximum metaspace size. There is no default (example: "100"). | | ||
| | `GC_CONTAINER_OPTIONS` | Specify Java GC to use. The value of this variable should contain the necessary JRE command-line options to specify the required GC, which will override the default of `-XX:+UseParallelGC` (example: `-XX:+UseG1GC`). | | ||
| Here are some examples: |
There was a problem hiding this comment.
| Here are some examples: | |
| Here are some examples: |
(newline to separate the paragraph from the table above)
|
|
||
| dependencies { | ||
| implementation(project(":polaris-config-docs-annotations")) | ||
| implementation(project(":polaris-core")) |
There was a problem hiding this comment.
A bit sad that this is needed as an implementation dependency.
| implementation(project(":polaris-core")) | |
| implementation(project(":polaris-core")) { | |
| isTransitive = false | |
| } |
76bebf5 to
e263b9c
Compare
flyingImer
left a comment
There was a problem hiding this comment.
this is cool! I wonder if we can have folders for auto gen docs and manually curated docs by straightforward names? This can help avoid accidentally changing doc files supposed to be auto generated, also making it obvious for new comers rather than an untold knowledge by the community
There was a problem hiding this comment.
[main Helm chart documentation](../../helm/) needs to be updated to [main Helm chart documentation](../configuration/helm/)
There was a problem hiding this comment.
You were right that the link is broken, but it seems the right link is [main Helm chart documentation](../../../helm).
FYI this page will go away with #3812.
There was a problem hiding this comment.
| The [Polaris Evolution](../configuration/evolution) page discusses backward compatibility and |
There was a problem hiding this comment.
I don't agree with your suggestion: this link is correct.
There was a problem hiding this comment.
Oh sorry, you were right, I was looking at my other PR #3812
Thanks for the suggestion! Do you have an example of the layout you have in mind? |
11d4c11 to
12f631c
Compare
…hensive configuration reference documentation for the Polaris site. This extends the existing `config-docs` generator to support two types of configuration sources: 1. SmallRye Config properties (from `@ConfigMapping` annotated interfaces) 2. `PolarisConfiguration` static fields (both `FeatureConfiguration` and `BehaviorChangeConfiguration`) Key changes: - Modified `DocGenDoclet` to extract configuration metadata from `FeatureConfiguration` and `BehaviorChangeConfiguration` static fields using reflection and javadoc processing. - Add new Gradle task to copy generated docs to the site content directory with proper Hugo front matter - Reorganize site configuration documentation into a dedicated section with separate pages for configuration overview and reference - Add CI workflow step to verify generated configuration docs are up-to-date The generated documentation includes property names, descriptions, default values, types, and catalog config mappings where applicable.
12f631c to
bf55e0f
Compare
|
FYI: rebased on top of #3812 |



This PR leverages the existing docs generator tool to expose a comprehensive configuration reference documentation for the Polaris site including feature flags.
This extends the existing
config-docsgenerator to support two types of configuration sources:@ConfigMappingannotated interfaces)PolarisConfigurationstatic fields (bothFeatureConfigurationandBehaviorChangeConfiguration)Key changes:
DocGenDocletto extract configuration metadata fromFeatureConfigurationandBehaviorChangeConfigurationstatic fields using reflection and javadoc processing.The generated documentation includes property names, descriptions, default values, types, and catalog config mappings where applicable.
Checklist
CHANGELOG.md(if needed)site/content/in-dev/unreleased(if needed)