Skip to content

sap-iac.services

Summary

Role: Required. · Reads: specs/scenario.md, specs/landscape.md (+ governance) · Writes: specs/services.md

Classifies each requested service, then resolves a dependency-ordered list of BTP entitlements, subscriptions, and service instances for each subaccount.

When to run it

After sap-iac.accounts, once the account topology exists.

Inputs and outputs
Reads memory/service-params-catalogue.yaml, specs/scenario.md, and specs/landscape.md, plus memory/global-account.md and memory/governance.md when present.
Writes specs/services.md — per subaccount: required entitlements (service + plan), subscriptions, and service instances with configuration, consumption type, and location metadata.

Behaviour

  • Maps the scenario's needs onto concrete BTP services and plans for each subaccount in the landscape.
  • Derives the default consumption type from the entitlement plan category: SERVICE, ELASTIC_SERVICE, and ELASTIC_LIMITED map to instances; APPLICATION and QUOTA_BASED_APPLICATION map to subscriptions. It then lets you confirm the derived type or choose entitlement-only. If platform data cannot resolve the category, it asks you to classify the service.
  • For each service instance in a subaccount with Cloud Foundry enabled, asks whether it belongs on BTP or in a CF space. CF instances record their selected cf_space; if the landscape contains no CF space, the command asks you to add one with sap-iac.accounts before continuing.
  • Records consumption_type for every service and records location (btp or cf) and cf_space for CF instances. Entitlement-only services receive only their entitlement assignment.
  • For matching service instances, reads required and optional parameters from memory/service-params-catalogue.yaml and records the supplied values in a parameters: block. See Service-parameter catalogue.
  • Records quota_required: true for plans in the SERVICE or QUOTA_BASED_APPLICATION categories.
  • For every Cloud Foundry-enabled subaccount with structured application sizing, derives one entitlement-only APPLICATION_RUNTIME / MEMORY entry. Its amount is max(1, ceil(total memory_mb / 1024)); it is never converted into an instance or subscription.
  • Resolves the dependency ordering between services so they can be created in a valid sequence.
  • Prefers the sap-docs MCP server over web fetches for SAP documentation.

Governance enforcement

For each user-requested service instance, services determines the environment tier from specs/landscape.md and validates the chosen plan against the Service Plans rules, stopping on a violation unless - Override: true is set. The derived runtime-memory entitlement is mandatory and is not a user-selectable service-plan decision. Without a governance file the command proceeds without enforcement and says so.

BTP platform validation

Before writing specs/services.md, services validates every resolved entitlement, subscription, service offering, and plan against the configured global-account subdomain from memory/global-account.md, using read-only BTP CLI/MCP lookups (no mutations). If a resolved item is unavailable in that global account, it asks for a valid replacement before writing.

Example

/sap-iac.services

For the HR leave-request subaccount, services records the SAP HANA Cloud and XSUAA entitlements and their instances in specs/services.md. This example selects BTP for XSUAA and a CF space for HANA Cloud:

## hr-leave-prod
### Entitlements
- hana-cloud / hana (SAP HANA Cloud)
- xsuaa / application
### Service instances (in order)
1. xsuaa (application) — consumption_type: instance, location: btp
2. hana-cloud (hana) — consumption_type: instance, location: cf, cf_space: hr-leave-apps

Next: sap-iac.security.