TrustRolloutStatusVerticalKey

TrustRolloutStatusVerticalKey
Vertical Key

Identifies a vertical (platform component or integrated service) in the certificate rotation rollout. The set of verticals active in any given rotation depends on the deployment configuration (form factor and which services are deployed and enabled). Use GET /trust/trust-rollout-status to discover which verticals are involved in the current or most recent rotation.

Verticals fall into two behaviorally distinct categories:

With node-level detail - Trust manager tracks per-node rotation progress for these verticals. Their rollout_result reaches COMPLETED_SUCCESSFULLY or COMPLETED_WITH_FAILURES, and node-level arrays (success_nodes, failed_nodes, pending_nodes) are populated.

Start acknowledgment only - Trust manager records only whether rotation was successfully initiated. Actual rotation progress for these verticals is managed externally and is not visible through this API. Their rollout_result is START_SUCCESSFUL or FAILED_TO_START_ROTATION; node-level arrays are always empty.

Which specific verticals fall into which category depends on the deployment configuration. The known values are listed in the enum below.

Key naming conventions:

  • SSP - LicenseHub pushing its CA to remote SSP (ATP) sites it has onboarded.
  • LH - SSP (cluster-api) pushing its ingress certificate update to LicenseHub.
  • NSX - LicenseHub pushing its CA to remote NSX managers.
  • AVI - LicenseHub pushing its CA to remote AVI Copilot sites.
This data structure has no properties.
Enumeration: BAREMETALSECURITY, SENSOR, SSP, LH, NSX, AVI