Tech Debt (new prod reg): Support ignoreGroups in the scope of the new prod reg

[aalves08]

Is your feature request related to a problem? Please describe.

Currently DSL ignoreGroups logic is based on schema.attributes.group, which isn't really up-to-date with the direction of the new product registration.

Let's cover it in the scope of the new product registration, not only for groups but also for resource pages and custom pages, where we want to show them conditionally (can be either RBAC or custom condition)

Describe the solution you'd like

Describe alternatives you've considered

Additional context

[github-actions]

🎯 Agentic Issue Triage

This is a tech debt / enhancement issue requesting that the ignoreGroups logic be migrated and extended within the new product registration DSL (plugin-products.ts / TopLevelPluginProduct). Currently ignoreGroups relies on schema.attributes.group (in shell/store/type-map.js), which is legacy and not aligned with the new product registration approach. The ask also extends the concept to resource pages and custom pages with support for conditional visibility (RBAC or custom conditions).

📋 Issue Summary

• Type: Tech Debt / Enhancement
• Area: Extensions – new product registration DSL
• Milestone: v2.16.0
• Priority: 2 (normal)
• Current behaviour: ignoreGroup callback in type-map.js uses schema.attributes.group — not available / meaningful in new product registration context.
• Desired behaviour: New product registration supports conditional visibility (show/hide) for groups, resource pages, and custom pages — driven by RBAC checks or arbitrary custom conditions.

🗂️ Relevant Code Pointers

File	Notes
shell/store/type-map.js (line ~307, 1709)	Existing ignoreGroup implementation using schema.attributes.group
shell/core/plugin-types.ts	ifHave, ifHaveType, ifHaveVerb already exist as conditional visibility primitives — good foundation
shell/core/plugin-products-top-level.ts	Where new top-level products are built — likely where new DSL surface should live
shell/core/plugin-products-helpers.ts	Shared helpers — good place for condition evaluation utilities
shell/core/__tests__/plugin-products.test.ts	Existing unit tests to extend

🛠️ Suggested Approach / Sub-tasks

• Audit existing ignoreGroup usage across shell/config/product/*.js to understand all call patterns and what conditions are passed.
• Define the new DSL API on ProductChild / page config types in plugin-types.ts — e.g. a showIf / hideIf field that accepts an RBAC permission descriptor or a callback (context) => boolean.
• Implement evaluation logic in plugin-products-helpers.ts — evaluate RBAC (using store.getters['auth/...']) and custom condition callbacks.
• Wire into TopLevelPluginProduct.apply() so that groups, resource pages and custom pages respect the condition at registration time (and possibly reactively).
• Migrate / deprecate the old ignoreGroup DSL call from type-map.js in the context of new-product-reg products.
• Write/extend unit tests in shell/core/__tests__/plugin-products.test.ts.
• Update extension documentation to document the new conditional visibility API.

💡 Debugging / Investigation Strategies

• Trace how ignoreGroup result affects navigation rendering: shell/components/nav/ — look for where type-map getters are consumed to build the side-nav tree.
• Check how ifHave / ifHaveType are already evaluated in the existing product registration path — reuse the same evaluation pipeline.
• Consider whether conditions should be evaluated once at registration or reactively (e.g., if RBAC changes without page reload). The latter is more complex but more correct.

🔗 Useful Resources

• [Rancher UI Internal Docs – Extensions]((extensions.rancher.io/redacted)
• type-map.js ignoreGroup implementation
• plugin-types.ts — existing ifHave* conditional fields
• plugin-products-top-level.ts

Generated by Agentic Triage for issue #17732 · ● 307.2K · ◷