Skip to main content

Provider Capabilities

Capabilities define what a provider can do. They are configured during creation and surfaced both per-row (Capabilities column) and in aggregate (Capabilities Health card).

Discovery​

When Discovery is enabled, Stack Automation scans the provider and inventories the resources it manages. Discovered resources become browsable by drilling into the provider from the inventory list. Discovery typically requires read-level credentials.

  • Enumerates resources managed by the provider (e.g., Blades, Rack Units, VMs, cloud objects).
  • Captures resource metadata such as name, type, model, and location.
  • Powers the resource list and usage metrics on the provider drill-down page.

Deploy​

When Deploy is enabled, the provider can serve as a target for deploying blueprints and launching deployments. Deploy generally requires write-level credentials and may use a separate credential set when Multiple Credentials Set is selected.

Capability health​

Each enabled capability is health-checked. The Capabilities Health card rolls these checks up into percentages so operators can see, for example, that Discovery is healthy on 52% of providers while Deploy is healthy on 86%. Unhealthy capabilities appear as red icons in the provider row, making it easy to locate connections that need attention.