Bug: `hideBulkActions` won't work on pages with custom list view where `table-actions` is set to `true` on `ResourceTable`

[aalves08]

Setup

• Rancher version: v2.14 / master (v2.15 development)
• Rancher UI Extensions: Product Registration API (experimental)
• Browser type & version: N/A (code-level issue)

Describe the bug

The DSL hideBulkActions method correctly sets state.hideBulkActions[type] = true in the type-map store, and the ResourceTable component's _showBulkActions computed correctly checks this via type-map/hideBulkActionsFor. However, some resource types have custom list components (under shell/list/) that render their own <ResourceTable> with a hardcoded :table-actions="true" prop. This prop takes precedence over the store-based check, making the hideBulkActions DSL method ineffective for those resource types.

To Reproduce

1. In an extension, register a resource page for provisioning.cattle.io.cluster with hideBulkActions: true (either via the new product registration API or the legacy DSL)
2. Navigate to the resource list page
3. Observe that bulk action checkboxes are still visible

Result

Bulk action checkboxes are still shown in the table despite hideBulkActions being set to true in the store.

The _showBulkActions computed in ResourceTable.vue exits early at the tableActions !== null check because the custom list component at shell/list/provisioning.cattle.io.cluster.vue (line 241) passes :table-actions="true" directly. This means the store-based hideBulkActionsFor getter is never consulted.

Expected Result

When hideBulkActions(type, true) is called via the DSL, bulk action checkboxes should be hidden for that resource type, regardless of whether the resource type has a custom list component.

Screenshots
N/A

Additional context

The affected file is shell/list/provisioning.cattle.io.cluster.vue, but this pattern likely exists in other custom list components as well. A quick search shows multiple custom list components using hardcoded :table-actions values.

Possible fixes:

• Option A: In custom list components that hardcode :table-actions="true", replace it with a computed that also checks type-map/hideBulkActionsFor — respecting the DSL override while preserving the default behavior
• Option B: In ResourceTable.vue, change _showBulkActions so that the store-based hideBulkActionsFor check takes precedence over the tableActions prop when the store explicitly sets it to hidden
• Option C: Document that hideBulkActions only works for resource types that do NOT have a custom list component in shell/list/

[github-actions]

🎯 Agentic Issue Triage

Summary: The hideBulkActions DSL method is ineffective for resource types that use custom list components (under shell/list/) which hardcode :table-actions="true" directly on <ResourceTable>. This prop short-circuits the store-based hideBulkActionsFor check in ResourceTable._showBulkActions, meaning the DSL override is silently ignored.

Currently, only shell/list/provisioning.cattle.io.cluster.vue (line 216) has been confirmed to hardcode :table-actions="true", but the pattern could exist in others.

📍 Root Cause Analysis

Data flow:

1. Extension calls hideBulkActions('provisioning.cattle.io.cluster', true) → commits to type-map store: state.hideBulkActions['provisioning.cattle.io.cluster'] = true
2. shell/list/provisioning.cattle.io.cluster.vue renders <ResourceTable :table-actions="true" ...>
3. In ResourceTable._showBulkActions:

   _showBulkActions() {
     if (this.tableActions !== null) {   // ← true !== null, exits here
       return this.tableActions;          // ← returns true, never checks store
     } else if (this.schema) {
       const hideTableActions = this.$store.getters['type-map/hideBulkActionsFor'](this.schema);
       return !hideTableActions;           // ← never reached
     }
     return false;
   }

4. Bulk action checkboxes remain visible despite DSL configuration.

Relevant files:

• shell/components/ResourceTable.vue — _showBulkActions computed (~line 296)
• shell/list/provisioning.cattle.io.cluster.vue — hardcoded :table-actions="true" (~line 216)
• shell/store/type-map.js — hideBulkActions mutation (~line 1694) and hideBulkActionsFor getter (~line 1130)

🔧 Fix Options (as identified in the issue)

Option B is likely the most robust fix — it centralises the logic so future custom list components and extension-provided overrides automatically respect the DSL without per-component changes.

Option B — ResourceTable.vue change:

_showBulkActions() {
  // Store-based override takes precedence when explicitly set
  if (this.schema) {
    const hideTableActions = this.$store.getters['type-map/hideBulkActionsFor'](this.schema);
    if (hideTableActions) return false;
  }
  if (this.tableActions !== null) {
    return this.tableActions;
  }
  return false;
}

Risk: Low — only changes behavior when hideBulkActionsFor explicitly returns true. The prop still controls default behavior.

Option A — Per-component computed in provisioning.cattle.io.cluster.vue:

showBulkActions() {
  const hide = this.$store.getters['type-map/hideBulkActionsFor'](this.schema);
  return hide ? false : true;
}

Then bind :table-actions="showBulkActions".
Risk: Requires a fix in every affected list component. Doesn't prevent regression if new custom components are added.

Option C (document only): Not ideal as it silently breaks an advertised extension capability.

🧪 Reproduction Steps

1. Create a Rancher UI extension and register a product configuration for provisioning.cattle.io.cluster with hideBulkActions: true:

   // Using legacy DSL
   product.hideBulkActions('provisioning.cattle.io.cluster', true);
   // OR using the new Product Registration API
   // (set hideBulkActions: true on the resource page metadata)

2. Install/load the extension in a running Rancher instance.
3. Navigate to Cluster Management → Clusters (the provisioning.cattle.io.cluster list page).
4. Observe: Bulk action checkboxes are still visible in the table header row.
5. Expected: No checkboxes / bulk action controls should be shown.

🐛 Debugging Strategy

• Add a breakpoint or console.log in ResourceTable._showBulkActions to confirm this.tableActions is true (not null) when rendering the cluster list — this confirms Option B's path is the right one.
• Verify this.$store.getters['type-map/hideBulkActionsFor'](schema) returns true in the same context to confirm the store is being correctly updated.
• Check if any other files in shell/list/ hardcode :table-actions:

  grep -rn ":table-actions=" shell/list/ --include="*.vue"

  (Currently only provisioning.cattle.io.cluster.vue was found.)

✅ Implementation Checklist

• Decide on Option A vs Option B (recommend B for robustness)
• If Option B: update _showBulkActions in shell/components/ResourceTable.vue to check store before the tableActions prop when store explicitly returns true
• If Option A: add computed property in shell/list/provisioning.cattle.io.cluster.vue to consult the store
• Audit all other files in shell/list/ for the same pattern (currently none found beyond the cluster list)
• Add/update unit tests in shell/components/__tests__/ (or wherever ResourceTable tests live) to cover the case where tableActions=true is passed but store has hideBulkActionsFor=true
• Manually verify the fix by reproducing with a test extension

📚 Relevant Resources

• shell/components/ResourceTable.vue — _showBulkActions computed
• shell/store/type-map.js — hideBulkActions mutation & getter
• shell/list/provisioning.cattle.io.cluster.vue — affected custom list component
• Rancher UI Extensions docs: [Product Registration API]((extensions.rancher.io/redacted)

Generated by Agentic Triage for issue #17426 · ● 336.4K · ◷

[aalves08]

Option C was the preferred option

though shouldn't it be that if a custom list exists AND it providers a bulk action prop? without that prop wouldn't it work as normal (type-map bulk setting used)? 🤔