IBM Concert kinds

The concert service has 11 resource kinds, each listed below with its endpoints, fields, and dependencies. Values resolve late, so you reference another resource with ${kind.ref_name}. For defaults, validation rules, and examples, run wxctl explain <kind>.

YAML envelope & reference syntax

• Envelope: A config is one or more YAML documents separated by ---. Each has top-level kind and ref_name, then the fields below at the top level (not nested under spec).
• ref_name: Unique handle for this resource within the config. Used to reference it from other resources, then stripped before the API call (not a schema field).
• References: Reference another resource by its ref_name: ${<kind>.<ref_name>} resolves to its id, ${<kind>.<ref_name>.<field>} to a specific field. Values resolve late, at plan/apply time.

​

concert_application

A Concert application is the top-level managed entity in IBM Concert’s inventory, the unit Concert tracks for risk posture, vulnerabilities, dependencies, and resilience. Runs on Software · ID field id Endpoints Fields Computed outputs: id, status, created_on, last_updated_on, application_release_id. Consumers

• concert_automation_rule → .component_id (optional)
• concert_compliance_profile → .application_releases_ids (optional)

​

concert_automation_rule

A Concert automation rule fires an action (e.g. auto-create an ITSM ticket) when a use-case condition is met, the declarative half of Concert’s auto-ticketing. Runs on Software · ID field id Endpoints Fields Computed outputs: id, created_on, created_by. Depends on

• component_id → concert_application (optional)
• component_id → concert_environment (optional)
• credential_id → concert_credential (optional)

​

concert_compliance_profile

A Concert compliance profile is a named, versioned set of controls (drawn from a pre-imported compliance catalog) that Concert evaluates applications against to score compliance posture, the declarative half of Concert’s compliance / AI-governance surface (sovereign, CSCF/ISCF, etc.). Runs on Software · ID field uuid Endpoints Fields Computed outputs: uuid, mapped_profile, last_updated_by, last_updated_on. Depends on

• application_releases_ids → concert_application (optional)

​

concert_credential

A Concert credential is a named key/value secret bundle used by ingestion jobs to authenticate against source systems. Runs on Software · ID field id Endpoints Fields Computed outputs: id, created_on, last_updated_on. Consumers

• concert_automation_rule → .credential_id (optional)
• concert_ingestion_job → .credentials_id (optional)

​

concert_environment

A Concert environment is a deployment target (e.g. a cluster, region, or stage) tracked in IBM Concert’s inventory. Runs on Software · ID field id Endpoints Fields Computed outputs: id, last_updated_on. Consumers

• concert_automation_rule → .component_id (optional)

​

concert_ingestion_job

A Concert ingestion job pulls data from a source system (authenticating with a concert_credential) into IBM Concert’s inventory on a schedule. Runs on Software · ID field id Endpoints Fields Computed outputs: id, created_on, last_updated_on. Depends on

• credentials_id → concert_credential (optional)

​

concert_resilience_input_data_key

A Concert resilience input-data key (InputDataKeyRequest) defines a named metric input, its label, units, and data type, that resilience requirements evaluate against. Runs on Software · ID field input_data_key_id Endpoints Fields Computed outputs: input_data_key_id, domain_id, is_oob, created_by, creation_ts. Consumers

• concert_resilience_profile → .input_data_keys (optional)

​

concert_resilience_library

A Concert resilience library (LibraryRequest) groups resilience requirements into a reusable set. Runs on Software · ID field id Endpoints Fields Computed outputs: id, is_oob, nfr_count.

​

concert_resilience_posture

A Concert resilience assessment posture (GraderPostureRequest) binds a concert_resilience_profile to a target (application/deployment) and schedules its resilience assessment. Runs on Software · ID field id Endpoints Fields Computed outputs: id, is_primary, app_name, env_name. Depends on

• profile_name → concert_resilience_profile (required)

​

concert_resilience_profile

A Concert resilience assessment profile (GraderProfileRequest) is a named set of resilience requirements, scored against metric input-data keys, that Concert evaluates to rate an application’s resilience posture. Runs on Software · ID field id Endpoints Fields Computed outputs: id, is_oob, nfr_count, input_data_keys_count, creation_ts, created_by. Depends on

• input_data_keys → concert_resilience_input_data_key (optional)

Consumers

• concert_resilience_posture → .profile_name (required)

​

concert_source_repo

A Concert source repository is a version-controlled code repo tracked in IBM Concert’s inventory for SBOM, CVE, and dependency posture. Runs on Software · ID field id Endpoints Fields Computed outputs: id, created_on, last_updated_on.