Deployment and operator
Automating how a multi-technology SAP BTP project actually gets built and deployed, on top of what deploymentDeploymentGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.SAP and community, narrow by design covers: generating an MTA descriptor from a workspace that bundles CAP, Fiori Elements and MDK modules into one artifact, and the build, deploy, migrate and validate commands a Mobile Development Kit project needs to reach Cloud Foundry. Deployment is the target runtime's own topology; this is the tooling that drives a build toward it.
Overview
SAP publishes @sap/artifact-management@sap/artifact-managementA library a VS Code extension calls to read a multi-module workspace, generate its MTA descriptor and archive, and deploy the bundle to Cloud Foundry in one click.sap official, btp, which reads a multi-module VS Code workspace, generates its MTA yaml and MTAR, and one-click deploys the bundle to Cloud Foundry; and @sap/mdk-tools@sap/mdk-toolsA command-line tool for Mobile Development Kit projects — build, deploy, migrate and validate MDK metadata — built on the MTA Build Tool and the Cloud Foundry CLI.sap official, btp, a CLI with mdk build, mdk deploy, mdk migrate and mdk validate for Mobile Development Kit metadata projects specifically, built on the MTA Build Tool and the Cloud Foundry CLI.
Not covered: Both are scoped tools rather than a general deployment operator: artifact-management to the MTA-bundling workflow a VS Code workspace drives, mdk-tools to MDK projects specifically. Neither has a public repository, and no community alternative for either was found.
No community artifact is documented here.
Artifacts
Details
Coverage
For your agent
- Ref
capability:deployment-operator- JSON
- /capabilities/deployment-operator.json
- MCP
- Connecting an agent