CAPA extension provisioning card is not hidden when the aws capi provider is not installed

[mantis-toboggan-md]

Setup

• Rancher version: v2.15-bcfacbd81af07c89117639b07fdb2076a56d58b9-head
• Rancher UI Extensions: CAPA 0.0.0-rc3
• Browser type & version: ff

Describe the bug
When the aws capi provider is not installed, the CAPI AWS card shouldn't be shown in the provisioning cluster creation screen (see screenshot). This should be fixable from the capa extension repo.

To Reproduce

1. install the capa extension; do NOT install the aws capi provider
2. navigate to the cluster management cluster list view and click 'create'

Result
CAPA AWS card is present, selectable

Expected Result
The CAPA AWS card should only be visible once the aws capiprovider is installed

Screenshots

Additional context
To make the CAPA ui extension available for install, add the following clusterrepo to your local cluster

apiVersion: catalog.cattle.io/v1
kind: ClusterRepo
metadata:
  name: prov-capi-ui-extensions
spec:
  url: https://rancher.github.io/prov-capi-ui-extensions

[github-actions]

🎯 Agentic Issue Triage

Summary: The CAPA extension registers a provisioning card for AWS CAPI clusters but does not check whether the AWS CAPI infrastructure provider (AWSCluster CRD) is actually installed before showing it. As a result, users see a selectable AWS card in the cluster-creation wizard even when the underlying provider is absent, leading to a broken provisioning flow.

The reporter correctly identifies that the fix belongs in the rancher/prov-capi-ui-extensions repo, not in the core dashboard.

---

📋 Technical Analysis

How provider cards are registered

The dashboard resolves provisioner cards via context.$extension.getProviders(context) (shell/core/extension-manager-impl.js#L466).
Each extension provides a class that is instantiated with a context object which includes:

• $store – full Vuex store (management + cluster)
• $extension – the extension manager

The IClusterProvisioner interface (shell/core/types-provisioning.ts#L192) already has a hidden?: boolean property specifically for this purpose:

/**
 * Hide the cluster provider card
 */
hidden?: boolean;

The gap

The CAPA extension's provisioner class doesn't implement conditional visibility based on whether the AWS CAPI infrastructure provider CRD is present.

Dashboard pattern for schema/CRD checks

The dashboard already uses this pattern widely:

// Check if schema/CRD is available
const hasAWSCluster = this.$store.getters['management/schemaFor']('infrastructure.cluster.x-k8s.io.awscluster');

Similar checks exist in shell/components/nav/TopLevelMenu.vue, shell/list/provisioning.cattle.io.cluster.vue, etc.

---

🔁 Reproduction Steps

1. Add the prov-capi-ui-extensions ClusterRepo to the local cluster:

   apiVersion: catalog.cattle.io/v1
   kind: ClusterRepo
   metadata:
     name: prov-capi-ui-extensions
   spec:
     url: (rancher.github.io/redacted)

2. Install the CAPA extension from Apps → Extensions.
3. Do NOT install the AWS CAPI infrastructure provider (i.e., do not install cluster-api-provider-aws/CAPA operator).
4. Go to Cluster Management → Create.
5. Observe the CAPA AWS card — it is visible and selectable.
6. Expected: card should not be shown (or should be disabled/hidden) when the AWS infrastructure provider CRD is absent.

---

🛠️ Debugging Strategy

• Check what CRDs/schemas are present when the AWS CAPI provider is not installed vs. when it is installed. In the browser console (with the store exposed):

  window.$nuxt.$store.getters['management/schemaFor']('infrastructure.cluster.x-k8s.io.awscluster')

  This should return undefined when the provider is absent.
• In the CAPA extension provisioner class, inspect the constructor context and verify that this.$store is accessible.
• Verify that setting hidden = true on the provisioner class instance removes the card from the creation wizard.

---

✅ Suggested Fix Checklist (for `rancher/prov-capi-ui-extensions`)

• In the CAPA provisioner class constructor, use context.$store.getters['management/schemaFor'] to check for the presence of the AWS CAPI infrastructure provider schema (e.g., infrastructure.cluster.x-k8s.io.awscluster or the equivalent AWSMachineTemplate schema).
• If the schema is absent, set this.hidden = true so the card is not shown in the creation wizard.
• Add a manual or automated test: install the CAPA extension, verify card is hidden; then install the AWS CAPI provider, verify card appears.
• Consider also handling the disabled state with a tooltip explaining "Install the AWS CAPI provider to enable this option" as an alternative to full hiding, for better UX discoverability.
• Backport if needed for Rancher v2.15.1 milestone.

---

🔗 Useful References

• IClusterProvisioner interface — hidden property
• extension-manager-impl.js — getProviders
• [Dashboard docs — Machine Drivers / API Calls]((rancher.github.io/redacted)
• CAPA UI Extensions repo
• Related issue — credential annotation bug (same CAPA area): Credentials created within cluster provisioning forms are missing an annotation applied when created from the credential list view #18105

Generated by Agentic Triage for issue #18243 · ● 707.9K · ◷

[github-actions]

🤖 Issue grooming analysis

All four primary grooming criteria are clearly met:

1. Clear Problem Statement ✅
The title and description unambiguously explain the issue: when the AWS CAPI provider is not installed, the CAPA AWS provisioning card still appears (and is selectable) on the cluster creation screen.

2. Acceptance Criteria ✅
The expected result is concrete and directly testable: the CAPA AWS card should only be visible when the AWS CAPI provider is installed. A QA engineer can verify this by checking card visibility against provider installation state.

3. Technical Details ✅
Environment details are provided (Rancher version, CAPA extension version, browser). A screenshot illustrates the problem, and a ClusterRepo YAML snippet is included to reproduce the exact test environment.

4. Reproducibility ✅
Two clear numbered steps are given: (1) install the CAPA extension without the AWS CAPI provider, (2) navigate to cluster management and click Create. Expected vs. actual behavior is clearly stated.

5. Dependencies / Additional Information ✅
A note indicates the fix should originate from the CAPA extension repo, providing useful triage context.

This analysis was generated automatically based on the repository's grooming checklist.

Generated by Daily Issue Grooming · ● 2M · ◷