Service Instances for Subaccount: shared
Auto-generated from the Terraform output
globalaccount_metadata- do not edit by hand. Regenerate withmake docs(SPEC-TF-004; ADR-TF-008 / ADR-TF-009).
Service instances in Subaccount shared (14ee2b27-844b-47ad-977e-4ab58a12ad90), 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.
Total service instances: 1
| Name | Instance ID | Service plan | Platform | Ready | Usable | Dashboard URL | Created | Last modified |
|---|---|---|---|---|---|---|---|---|
flag-lite |
d6e476a0-60a3-4215-9173-b31407bb0c7d |
e9d9a508-0039-4b3a-97df-a09525d113dd |
0406da05-d049-4fca-a7a1-0460c6c212a8 |
true |
true |
dashboard | 2026-10-02T20:41:26Z | 2026-10-02T20:41:26Z |
serviceplan_id is rendered exactly as the capture carries it: a
plan GUID, not a readable plan name. No readable plan name (the
lite shown in the BTP cockpit) is obtainable from this capture —
subaccount_entitlements.plan_unique_identifier holds readable
strings in a different namespace and does not join, and the
Cloud Foundry page's service_plan is a different GUID for the
same plan, so it is not a join key either. That is a capture
gap, not an unknown value: the plan behind the GUID is not lost,
only its display name.
labels are not rendered on this page. In the live capture the
subaccount_service_instances labels map carries a malformed upstream
value — a subaccount_id list element with a stray trailing double
quote. Reproducing it verbatim would publish a value that is not valid
upstream data, and the only key it holds is the subaccount id this page
is already scoped to, so nothing is lost by omitting it. The value is
passed through the Terraform capture unmodified; the omission is a
rendering decision, not a fix.
The Cloud Foundry page lists the same instance per space with its CF service plan, instance type, upgrade availability and credential binding names. Credential values are never collected by either page.
Generated from the Terraform output globalaccount_metadata (SPEC-TF-004). Subaccount shared (14ee2b27-844b-47ad-977e-4ab58a12ad90) in Global Account 24767a6d-72de-4bb7-8d44-221f3286a7e7 - subdomain vinehousesolutionsltd - generated 2026-10-02T21:34:30Z (UTC).