Skip to content

docs(opencut): sync template standards updates#361

Open
mberlofa wants to merge 1 commit into
mainfrom
docs/opencut-template-standards-sync
Open

docs(opencut): sync template standards updates#361
mberlofa wants to merge 1 commit into
mainfrom
docs/opencut-template-standards-sync

Conversation

@mberlofa

@mberlofa mberlofa commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Document networkPolicy.extraEgress for OpenCut.
  • Add OpenCut playground controls for custom egress CIDR and port.
  • Register OpenCut in the playground sync allowlist.

Related

Validation

  • npm run lint
  • npm run format:check
  • npm run build
  • make site-sync-check CHART=opencut
  • make release-check REPO=site
  • make attribution-check REPO=site

@coderabbitai

coderabbitai Bot commented Jul 4, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

This PR adds a new extra egress playground section for the apache chart, documents networkPolicy.extraEgress for opencut, and registers opencut in the playground chart mapping.

Changes

Network Policy Egress Configuration

Layer / File(s) Summary
Apache playground network policy fields
src/data/playground-configs.ts
Adds a new "Extra Egress" field group gated by networkPolicy.enabled, with CIDR and port inputs under networkPolicy.extraEgress.
Opencut docs and playground registration
src/pages/docs/charts/opencut.mdx, src/pages/playground.astro
Adds networkPolicy.extraEgress: [] to the opencut example and values table, and adds opencut to siteSyncPlaygroundConfigs.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

  • helmforgedev/site#322: Both PRs extend src/pages/playground.astro with an additional chart slug in siteSyncPlaygroundConfigs.
  • helmforgedev/site#330: Both PRs modify the same playground chart slug mapping in src/pages/playground.astro.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title is concise and matches the main change: syncing OpenCut docs, playground config, and allowlist updates.
Description check ✅ Passed The description covers summary, related references, and validation steps, with only template headings and checkbox formatting differing.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/opencut-template-standards-sync

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
src/data/playground-configs.ts (2)

235-262: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Merge the duplicate Apache Network Policy section
Apache now declares Network Policy twice with the same gateField. buildControls() keys section state and DOM lookup by group.name, so the two blocks collide and the second one won’t update correctly. Fold the extra egress fields into the existing section, or give the new block a unique name.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/data/playground-configs.ts` around lines 235 - 262, The “Network Policy”
section is duplicated with the same gateField, which causes buildControls() to
collide on group.name and break section state/DOM updates. Update the
playground-configs.ts configuration so the existing Network Policy group
contains both ingress and egress fields, or rename the extra block to a unique
name. Use the Network Policy entries in the configs array and the
buildControls() grouping behavior as the guide when fixing this.

1485-1528: 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Add OpenCut Network Policy controls to the playground. src/pages/docs/charts/opencut.mdx documents networkPolicy.extraEgress, but opencut in src/data/playground-configs.ts only exposes General and Ingress, so the playground hides the documented option.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/data/playground-configs.ts` around lines 1485 - 1528, Add the missing
OpenCut Network Policy section to the opencut playground config in
playground-configs so the documented networkPolicy.extraEgress setting is
editable. Update the opencut entry alongside the existing General and Ingress
groups, using the same field shape and a clear label/key for
networkPolicy.extraEgress, so the playground exposes the option documented in
the opencut chart docs.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@src/data/playground-configs.ts`:
- Around line 235-262: The “Network Policy” section is duplicated with the same
gateField, which causes buildControls() to collide on group.name and break
section state/DOM updates. Update the playground-configs.ts configuration so the
existing Network Policy group contains both ingress and egress fields, or rename
the extra block to a unique name. Use the Network Policy entries in the configs
array and the buildControls() grouping behavior as the guide when fixing this.
- Around line 1485-1528: Add the missing OpenCut Network Policy section to the
opencut playground config in playground-configs so the documented
networkPolicy.extraEgress setting is editable. Update the opencut entry
alongside the existing General and Ingress groups, using the same field shape
and a clear label/key for networkPolicy.extraEgress, so the playground exposes
the option documented in the opencut chart docs.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7e9ef1d4-29c1-4040-8c25-e53dc74243c2

📥 Commits

Reviewing files that changed from the base of the PR and between 365449a and 2fa2824.

📒 Files selected for processing (3)
  • src/data/playground-configs.ts
  • src/pages/docs/charts/opencut.mdx
  • src/pages/playground.astro

@mberlofa mberlofa force-pushed the docs/opencut-template-standards-sync branch from 2fa2824 to 2e2f26e Compare July 4, 2026 05:45

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
src/data/playground-configs.ts (1)

236-262: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Merge "Extra Egress" into the existing "Network Policy" group.

Both groups use the identical gateField: 'networkPolicy.enabled'. Elsewhere in this file (e.g. memcached, discount-bandit, phpmyadmin) egress-related fields are consolidated into a single "Network Policy" section rather than split across two collapsible groups with the same gate.

♻️ Suggested consolidation
     {
       name: 'Network Policy',
       collapsible: true,
       gateField: 'networkPolicy.enabled',
       fields: [
         {
           label: 'Restrict Ingress',
           key: 'networkPolicy.ingress.enabled',
           type: 'toggle',
           default: 'false',
           description: 'Restrict inbound traffic only when selectors are configured',
         },
         {
           label: 'Allow DNS',
           key: 'networkPolicy.egress.allowDns',
           type: 'toggle',
           default: 'true',
           description: 'Allow DNS egress',
         },
         {
           label: 'Allow Internet',
           key: 'networkPolicy.egress.allowInternet',
           type: 'toggle',
           default: 'true',
           description: 'Allow general outbound traffic',
         },
+        {
+          label: 'Extra Egress CIDR',
+          key: 'networkPolicy.extraEgress[0].to[0].ipBlock.cidr',
+          type: 'text',
+          default: '10.80.0.0/16',
+          description: 'Additional egress destination',
+        },
+        {
+          label: 'Extra Egress Port',
+          key: 'networkPolicy.extraEgress[0].ports[0].port',
+          type: 'number',
+          default: '443',
+          description: 'Additional TCP egress port',
+        },
       ],
     },
-    {
-      name: 'Extra Egress',
-      collapsible: true,
-      gateField: 'networkPolicy.enabled',
-      fields: [
-        {
-          label: 'Extra Egress CIDR',
-          key: 'networkPolicy.extraEgress[0].to[0].ipBlock.cidr',
-          type: 'text',
-          default: '10.80.0.0/16',
-          description: 'Additional egress destination',
-        },
-        {
-          label: 'Extra Egress Port',
-          key: 'networkPolicy.extraEgress[0].ports[0].port',
-          type: 'number',
-          default: '443',
-          description: 'Additional TCP egress port',
-        },
-      ],
-    },

Also applies to: 285-305

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/data/playground-configs.ts` around lines 236 - 262, Merge the separate
“Extra Egress” section into the existing “Network Policy” group in
playground-configs, since both sections use the same networkPolicy.enabled gate.
Update the Network Policy entry in the config array so it includes the
egress-related fields currently defined in the Extra Egress group, and remove
the duplicate collapsible group. Use the existing Network Policy object and its
fields list as the single place for these settings, consistent with the
memcached, discount-bandit, and phpmyadmin patterns.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@src/data/playground-configs.ts`:
- Around line 236-262: Merge the separate “Extra Egress” section into the
existing “Network Policy” group in playground-configs, since both sections use
the same networkPolicy.enabled gate. Update the Network Policy entry in the
config array so it includes the egress-related fields currently defined in the
Extra Egress group, and remove the duplicate collapsible group. Use the existing
Network Policy object and its fields list as the single place for these
settings, consistent with the memcached, discount-bandit, and phpmyadmin
patterns.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f4f71f48-eecd-48dc-bd53-a1f1a0e4dbe1

📥 Commits

Reviewing files that changed from the base of the PR and between 2fa2824 and 2e2f26e.

📒 Files selected for processing (3)
  • src/data/playground-configs.ts
  • src/pages/docs/charts/opencut.mdx
  • src/pages/playground.astro
✅ Files skipped from review due to trivial changes (1)
  • src/pages/docs/charts/opencut.mdx
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/pages/playground.astro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant