Concert blocks for the IBM Cloud Global Search and Tagging APIs

The IBM Cloud integration's blocks cover the VPC API and a few others, but nothing exposes the Global Search and Tagging service (api.global-search-tagging.cloud.ibm.com, tags.global-search-tagging.cloud.ibm.com). That leaves three things impossible from a workflow today:

1. Tags. The VPC API does not return user tags on an instance. There is no way to read tags, accesstags, servicetags or catalogtags for any resource from a Concert workflow.

2. Account-wide inventory. There is no account-wide "list instances" endpoint on VPC, so collecting an account means one call per region plus cursor paging within each region. Global Search answers the same question across every region and every service in one cursor-paged query.

3. Everything that isn't VPC. Object Storage buckets, Cloud Databases, Kubernetes/OpenShift clusters, Code Engine projects, Event Streams — Global Search indexes them all. A workflow can't see any of them.

Concert's value is risk in IBM Cloud — owner, environment, data classification, cost centre, compliance scope — live in tags. Without tag access, a Concert workflow can enumerate resources but cannot say who owns one or whether it is in scope. Anyone building inventory/CMDB sync, discovery, drift detection, tag-hygiene reporting, cost allocation or ownership-based routing hits this wall immediately.



Search blocks

https://cloud.ibm.com/docs/apis/search

Search Resources — POST /v3/resources/search. Inputs: the Lucene query, the requested fields list, limit, search_cursor, sort, is_deleted / is_reclaimed / is_public, account_id, impersonate_account, can_tag. Outputs: items, search_cursor, limit, more_data.
List Supported Types — GET /v3/resources/supported_types, so a workflow can build valid queries instead of hardcoding type names.

Tagging blocks

https://cloud.ibm.com/docs/apis/tagging
List Tags — GET /v3/tags, including attached_to=<crn> for a single resource and the account-wide tag list.
Attach Tag and Detach Tag. These are what turn Concert from reporting into remediation: a policy finds an untagged or mis-tagged resource and the same workflow fixes it.
Delete Tag / Delete Unused Tags for tag hygiene.