菜单
SAP BTP Cloud Foundry runtime — CF CLI operations, deployment, service lifecycle, troubleshooting, manifest authoring.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/williamcorrea23/sap-router-skill --skill btp-cloud-foundry命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | btp-cloud-foundry |
| description | SAP BTP Cloud Foundry runtime — CF CLI operations, deployment, service lifecycle, troubleshooting, manifest authoring. |
| trigger | ["cloud foundry","cf push","cf deploy","cf org","cf space","cf marketplace","cf logs","manifest.yml","buildpack","cf route","btp cf","cf create-service","cf bind-service"] |
| prerequisites | ["CF CLI v8+ installed (https://github.com/cloudfoundry/cli/releases)","BTP subaccount with Cloud Foundry environment enabled","Org and space already created in BTP Cockpit","Network access to CF API endpoint"] |
# Login to BTP CF API (region-specific endpoint)
cf login -a https://api.cf.us10.hana.ondemand.com
# Target specific org and space
cf target -o my-org -s dev
# Verify current target
cf target
# Standard push (uses manifest.yml if present)
cf push my-app
# Push with custom manifest
cf push my-app -f manifest-prod.yml
# Push with specific buildpack
cf push my-app -b nodejs_buildpack
# Push without starting (for binding services first)
cf push my-app --no-start
# List marketplace services and plans
cf marketplace
cf marketplace -s xsuaa
# Create service instance
cf create-service xsuaa application my-xsuaa -c xs-security.json
cf create-service hana hdi-shared my-hdi-container
cf create-service destination lite my-destination
# Bind service to app
cf bind-service my-app my-xsuaa
# Create and view service keys
cf create-service-key my-xsuaa my-key
cf service-key my-xsuaa my-key
# List all services in space
cf services
# Deploy new version with temporary route
cf push my-app-green
# Map production route to new version
cf map-route my-app-green cfapps.us10.hana.ondemand.com -n my-app
# Unmap route from old version
cf unmap-route my-app cfapps.us10.hana.ondemand.com -n my-app
# Stop and rename old version
cf stop my-app
cf rename my-app my-app-old
cf rename my-app-green my-app
cf logs my-app --recent # recent logs
cf logs my-app # stream live logs
cf app my-app # app status and instances
cf events my-app # crash/start/stop events
cf env my-app # VCAP_SERVICES and env vars
cf enable-ssh my-app && cf ssh my-app # SSH into container
cf restart my-app # restart with same droplet
cf restage my-app # rebuild droplet (needed after new bindings)
mbt build # build MTA archive
cf deploy mta_archives/my-cap-app_1.0.0.mtar # deploy to CF
cf mta my-cap-app # verify deployment
# Check app is running
cf app my-app
# Expected: #0 running, state=RUNNING
# Health check endpoint
curl -s https://my-app.cfapps.us10.hana.ondemand.com/health
# Expected: 200 OK
# Verify service bindings
cf env my-app | grep -A5 VCAP_SERVICES
# Expected: JSON with bound service credentials
# Check org quota usage
cf org-quota my-org
App crashes immediately after push (401 on all endpoints)
cf push my-app --no-start → cf bind-service my-app my-xsuaa → cf start my-app.Memory quota exceeded
cf org-quota my-org. Reduce memory in manifest or stop unused apps.Route collision during blue-green deploy
-green suffix for new version. Map route only after green is healthy.SSH fails with "not enabled"
cf enable-ssh my-app then cf restage my-app. Disable in production.Restage needed after binding new service
cf bind-service, run cf restage my-app to pick up new credentials.Buildpack version mismatch
buildpack: nodejs_buildpack#1.8.0.Service plan not available in region
cf marketplace -s <service> to verify plan availability before creating.