Service Instances for Subaccount: sub2

Auto-generated from the Terraform output globalaccount_metadata - do not edit by hand. Regenerate with make docs (SPEC-TF-004; ADR-TF-008 / ADR-TF-009).

Service instances in Subaccount sub2 (4d199eed-4b77-4e81-84fb-eb2a48462cb7), as reported by btp_subaccount_service_instances (SPEC-TF-004 subaccount phase, ADR-TF-007).

This is the account-side view and it covers all environments — Cloud Foundry, Kyma and any other — because BTP reports a service instance against the subaccount, not against one runtime. For Cloud Foundry specifics (org, space, service plan, credential binding names) see Cloud Foundry.

Why the same instance appears on two pages. The Cloud Foundry page reads the cloudfoundry/cloudfoundry provider via modules/cf_environment and is the only view that can place an instance in an org and space. This page reads the SAP/BTP account API and is the only view that reports the instance's ready and usable state. The two read the same instance from opposite sides, so both lists are expected to name it; neither is a duplicate of the other.

No credential or parameter values are collected or rendered here. The btp_subaccount_service_instance singular data source exposes a parameters field that can carry secrets; it is deliberately not wired in, so no such value exists in this capture to render.

!!! info "No service instances reported" btp_subaccount_service_instances returned no rows for Subaccount sub2 (4d199eed-4b77-4e81-84fb-eb2a48462cb7). That is an empty API result, not a collection gap.

Generated from the Terraform output globalaccount_metadata (SPEC-TF-004). Subaccount sub2 (4d199eed-4b77-4e81-84fb-eb2a48462cb7) in Global Account 24767a6d-72de-4bb7-8d44-221f3286a7e7 - subdomain vinehousesolutionsltd - generated 2026-10-02T21:34:30Z (UTC).