Skip to content

immutable-paths: walker should descend into oneOf/anyOf/allOf branch properties #3100

Closed as not planned

Description

What

findImmutablePaths (apps/console/src/lib/immutable-paths.ts) recognises a parent as immutable when any oneOf/anyOf/allOf branch carries the CEL rule itself, but does NOT descend into a branch's own properties to discover per-field immutability inside the branch.

Why it matters

CRDs that use allOf for property composition (less common than direct properties, but legal and present in some upstream CRDs) won't have their inner immutable fields flagged. The UI will render those fields as editable and the overlay won't protect them.

Pinned

Current behaviour is pinned by the FIXME test in apps/console/src/lib/immutable-paths.test.ts ("FIXME: does NOT walk into properties beneath oneOf/anyOf/allOf branches"). Flip the assertion when the walker is extended.

Activity

  1. lexfrei commented on Jul 1, 2026

    @lexfrei
    ContributorAuthor

    Duplicate of #3101 — identical title and body (same findImmutablePaths gap: the walker does not descend into a oneOf/anyOf/allOf branch's own properties). Consolidating on #3101, which already carries the triage labels. The behaviour is still pinned by the does NOT walk into properties beneath oneOf/anyOf/allOf branches (pinned current behaviour) test in packages/system/dashboard/images/console/apps/console/src/lib/immutable-paths.test.ts.

  2. github-actions commented on Aug 31, 2026

    @github-actions

    This issue has had no activity for 60 days and was marked lifecycle/stale.
    It will be closed in 14 days unless commented or labelled lifecycle/frozen.

  3. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Aug 31, 2026
  4. github-actions commented on Sep 14, 2026

    @github-actions

    Closed because no activity followed the lifecycle/stale warning.
    Reopen if the issue is still relevant.

  5. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed
    on Sep 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closedlifecycle/staleDenotes an issue or PR has remained open with no activity and has become staletriage/duplicateIndicates an issue is a duplicate of another issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions