Conversation
📝 WalkthroughWalkthroughThis PR updates version identifiers and Docker image tags across the entire codebase from release versions (5.16.0, 1.16.0) to "0.0.0-nightly" for all Helm charts, container images, package files, and related configuration files. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
mo-auto
added
area-CI
|
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docker-persistence-loader/Dockerfile (1)
7-7: UpdateFLEX_SOURCE_VERSIONto stay synchronized with nightly builds.The commit hash is pinned to
377359e8ce6ea5b650c7eb8e36a6faf739b2f282(from 2026-01-22), which is 4 days behind the latest commit. Since the base image uses0.0.0-nightly, theflex_schema.jsonfetched from this stale commit may not align with the schema expectations of the nightly base image. For consistency in nightly builds, updateFLEX_SOURCE_VERSIONto reference a more recent commit ormainto keep the schema in sync with base image updates.
🤖 Fix all issues with AI agents
In `@charts/gluu/charts/admin-ui/README.md`:
- Line 1: The README.md uses a top-level H1 ("# admin-ui"); change it to an H2
("## admin-ui") to follow the repository's documentation convention; update the
heading in charts/gluu/charts/admin-ui/README.md so the first line is "##
admin-ui" (ensure any table of contents or links that expect the H2 are
preserved).
In `@charts/gluu/charts/kc-scheduler/README.md`:
- Line 1: The README.md currently uses a top-level H1 heading ("#
kc-scheduler"); change it to an H2 by replacing "# kc-scheduler" with "##
kc-scheduler" so the document follows the repo’s convention of using H2 as the
first heading level for docs (update the README.md file where the heading string
"kc-scheduler" is defined).
In `@docs/reference/kubernetes/helm-chart.md`:
- Line 429: Update the chart documentation to reflect the correct Casa endpoint
path: change the description for the configuration key
global.casa.ingress.casaEnabled to indicate the endpoint is /jans-casa (not
/casa), so the documented path matches the values file and service paths.
| @@ -1,6 +1,6 @@ | |||
| # admin-ui | |||
There was a problem hiding this comment.
Use an H2 as the top-level heading.
This repo’s doc convention uses ## as the first heading level.
🔧 Suggested fix
-# admin-ui
+## admin-uiBased on learnings, please keep top-level headings at H2 in docs.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| # admin-ui | |
| ## admin-ui |
🤖 Prompt for AI Agents
In `@charts/gluu/charts/admin-ui/README.md` at line 1, The README.md uses a
top-level H1 ("# admin-ui"); change it to an H2 ("## admin-ui") to follow the
repository's documentation convention; update the heading in
charts/gluu/charts/admin-ui/README.md so the first line is "## admin-ui" (ensure
any table of contents or links that expect the H2 are preserved).
There was a problem hiding this comment.
auto generated with helm-docs
There was a problem hiding this comment.
@moabu, thank you for clarifying! Since the README is auto-generated by helm-docs, manual changes wouldn't persist.
If you wanted to align with the H2 convention noted in the learning, you could customize the helm-docs template by creating a README.md.gotmpl file in the chart directory and overriding the chart.header template to use ## instead of #. However, that's entirely optional—many auto-generated docs use their tool's defaults.
No action needed if you're comfortable with the current helm-docs output.
🧠 Learnings used
Learnt from: misba7
Repo: GluuFederation/flex PR: 2588
File: charts/gluu/values.yaml:1303-1306
Timestamp: 2026-01-16T21:30:14.483Z
Learning: In the GluuFederation/flex Helm charts (charts/gluu/values.yaml), the architectural pattern for all services and features is to place the `enabled` boolean flag under `global.<service>.enabled` while placing all other detailed configuration at the root level under `<service>.*`. This pattern applies to all services including admin-ui, auth-server, config-api, fido2, scim, casa, nginx-ingress, and gatewayApi.
Learnt from: iromli
Repo: GluuFederation/flex PR: 2579
File: docker-persistence-loader/README.md:1-12
Timestamp: 2026-01-14T18:44:47.701Z
Learning: In the GluuFederation/flex repository, documentation uses H2 (`##`) as the top-level heading convention instead of H1 (`#`).
| @@ -1,6 +1,6 @@ | |||
| # kc-scheduler | |||
There was a problem hiding this comment.
Use an H2 as the top-level heading.
This repo’s doc convention uses ## as the first heading level.
🔧 Suggested fix
-# kc-scheduler
+## kc-schedulerBased on learnings, please keep top-level headings at H2 in docs.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| # kc-scheduler | |
| ## kc-scheduler |
🤖 Prompt for AI Agents
In `@charts/gluu/charts/kc-scheduler/README.md` at line 1, The README.md currently
uses a top-level H1 heading ("# kc-scheduler"); change it to an H2 by replacing
"# kc-scheduler" with "## kc-scheduler" so the document follows the repo’s
convention of using H2 as the first heading level for docs (update the README.md
file where the heading string "kc-scheduler" is defined).
There was a problem hiding this comment.
auto generated with helm-docs
There was a problem hiding this comment.
@moabu, thank you for clarifying! I understand that this README is auto-generated by helm-docs and manual edits would be overwritten. I'll note this for future reference.
✏️ Learnings added
Learnt from: moabu
Repo: GluuFederation/flex PR: 2606
File: charts/gluu/charts/kc-scheduler/README.md:1-1
Timestamp: 2026-01-26T11:01:41.303Z
Learning: README.md files within Helm chart directories (e.g., charts/gluu/charts/*/README.md) in the GluuFederation/flex repository are auto-generated using the helm-docs tool and should not be manually edited. Any documentation corrections must be made in the source helm chart files (Chart.yaml, values.yaml comments, or templates) and then regenerated.
Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.
🧠 Learnings used
Learnt from: iromli
Repo: GluuFederation/flex PR: 2579
File: docker-persistence-loader/README.md:1-12
Timestamp: 2026-01-14T18:44:47.701Z
Learning: In the GluuFederation/flex repository, documentation uses H2 (`##`) as the top-level heading convention instead of H1 (`#`).
Learnt from: moabu
Repo: GluuFederation/flex PR: 2606
File: docs/reference/kubernetes/helm-chart.md:429-429
Timestamp: 2026-01-26T11:01:01.856Z
Learning: The file `docs/reference/kubernetes/helm-chart.md` in the GluuFederation/flex repository is auto-generated using the helm-docs tool and should not be manually edited. Any documentation corrections must be made in the source helm chart files (values.yaml comments or templates) and then regenerated.
| | global.casa.ingress | object | `{"casaAdditionalAnnotations":{},"casaEnabled":false,"casaLabels":{}}` | Enable endpoints in either istio or nginx ingress depending on users choice | | ||
| | global.casa.ingress.casaAdditionalAnnotations | object | `{}` | Casa ingress resource additional annotations. | | ||
| | global.casa.ingress.casaEnabled | bool | `false` | Enable casa endpoints /jans-casa | | ||
| | global.casa.ingress.casaEnabled | bool | `false` | Enable casa endpoints /casa | |
There was a problem hiding this comment.
Casa endpoint path should match /jans-casa.
The values file and service paths use /jans-casa; this line currently documents /casa.
Suggested fix
-| global.casa.ingress.casaEnabled | bool | `false` | Enable casa endpoints /casa |
+| global.casa.ingress.casaEnabled | bool | `false` | Enable casa endpoints /jans-casa |📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| | global.casa.ingress.casaEnabled | bool | `false` | Enable casa endpoints /casa | | |
| | global.casa.ingress.casaEnabled | bool | `false` | Enable casa endpoints /jans-casa | |
🤖 Prompt for AI Agents
In `@docs/reference/kubernetes/helm-chart.md` at line 429, Update the chart
documentation to reflect the correct Casa endpoint path: change the description
for the configuration key global.casa.ingress.casaEnabled to indicate the
endpoint is /jans-casa (not /casa), so the documented path matches the values
file and service paths.
There was a problem hiding this comment.
auto generated with helm-docs
There was a problem hiding this comment.
@moabu, understood! Since this file is auto-generated with helm-docs, any corrections would need to be made in the source helm chart values or templates rather than in this generated documentation file.
If the Casa endpoint path (/casa vs /jans-casa) needs to be corrected, it would require updating the source comments in the helm chart's values.yaml file, and then regenerating the documentation.
╰(◕‿◕)╯
✏️ Learnings added
Learnt from: moabu
Repo: GluuFederation/flex PR: 2606
File: docs/reference/kubernetes/helm-chart.md:429-429
Timestamp: 2026-01-26T11:01:01.856Z
Learning: The file `docs/reference/kubernetes/helm-chart.md` in the GluuFederation/flex repository is auto-generated using the helm-docs tool and should not be manually edited. Any documentation corrections must be made in the source helm chart files (values.yaml comments or templates) and then regenerated.
Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.
🧠 Learnings used
Learnt from: misba7
Repo: GluuFederation/flex PR: 2588
File: charts/gluu/values.yaml:1303-1306
Timestamp: 2026-01-16T21:30:14.483Z
Learning: In the GluuFederation/flex Helm charts (charts/gluu/values.yaml), the architectural pattern for all services and features is to place the `enabled` boolean flag under `global.<service>.enabled` while placing all other detailed configuration at the root level under `<service>.*`. This pattern applies to all services including admin-ui, auth-server, config-api, fido2, scim, casa, nginx-ingress, and gatewayApi.
Learnt from: misba7
Repo: GluuFederation/flex PR: 2588
File: docs/includes/cn-system-requirements.md:15-18
Timestamp: 2026-01-16T20:56:36.376Z
Learning: In the GluuFederation/flex project documentation (docs/includes/cn-system-requirements.md), the "Required" column in the system requirements table reflects whether a component is mandatory, not whether it's enabled by default. For example, nginx-ingress is enabled by default in the Helm charts but is documented as "No" (not required) because users can choose alternative ingress solutions like Gateway API, ALB, or Istio.
Learnt from: misba7
Repo: GluuFederation/flex PR: 2588
File: charts/gluu/templates/gateway-api.yaml:5-7
Timestamp: 2026-01-16T21:41:05.253Z
Learning: In the GluuFederation/flex Helm charts, service ports like fido2.service.port, scim.service.port, and casa.service.port are documented in values.yaml with the explicit comment "Please keep it as default." These ports are intentionally not parameterized in routing templates (ingress.yaml and gateway-api.yaml) and should remain hardcoded to maintain the established architectural pattern.
3 participants
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.