@sap/artifact-management
A 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.
A project that mixes CAP, Fiori Elements, MDK and XSUAA modules needs one MTA yaml and one MTAR describing them all before Cloud Foundry can deploy it as a unit. This gives a VS Code extension access to the workspace's project properties and its list of modules, watches the project for changes, and can generate the MTA yaml and MTAR and push the result to Cloud Foundry, rather than a developer hand-writing the descriptor and running the build tool separately.
Facts
Where it sits
Before choosing this
Conditions
PracticalFunctional boundary
A library a VS Code extension calls, not something installed and run on its own; there is no documented standalone CLI. No public repository either, so what it does is read from its own README rather than checked against source.
What it declares
Every artifact
- Type
- Package
- Origin
- By SAP
- Runtime
- Node.js
As a package
- Where it runs
- does not say
- Distributed through
- npm
Connections
Automating build and deployment of multi-module projects
Download
Install
npm add @sap/artifact-managementDerived from the package name. No recipe recorded; the README has the configuration.
README
quoted from @sap/artifact-management@1.53.4, readIntroduction
Artifact Management on SAP BTP facilitates the generation of project metadata comprising of multiple modules of different technologies, bundles the module into one single deployment artifact and supports one click deploy to Cloud Foundry
History
v1.53.4
v1.53.3
v1.53.2
v1.53.1
v1.52.0
v1.51.0
v1.50.0
v1.49.1
v1.49.0
v1.48.0
v1.47.10
v1.47.4
v1.47.0
v1.46.0
v1.45.1
v1.44.1
v1.44.0
v1.43.1
v1.43.0
v1.42.1
v1.42.0
v1.41.0
v1.40.1
v1.40.0
v1.39.1
v1.39.0
v1.38.0
v1.37.0
v1.36.2
v1.36.1
v1.36.0
v1.35.0
v1.34.0
v1.33.0
v1.32.0
v1.30.1
v1.30.0
v1.29.0
v1.28.1
v1.28.0
v1.27.1
v1.27.0
v1.26.1
v1.26.0
v1.25.1
v1.25.0
v1.24.2
v1.24.1
v1.23.4
v1.23.3
v1.23.2
v1.23.0
v1.22.1
v1.22.0
v1.21.0
v1.20.2
v1.20.1
v1.20.0
v1.19.1
v1.18.1
v1.19.0
v1.18.0
v1.17.2
v1.17.1
v1.17.0
v1.16.4
v1.16.3
v1.16.0
v1.15.1
v1.15.0
v1.14.2
v1.14.1
v1.13.1
v1.13.0
v1.12.1
v1.12.0
v1.11.1
v1.11.0
v1.10.0
v1.9.0
v1.8.1
v1.8.0
v1.7.0
v1.6.1
v1.6.0
v1.5.0
v1.4.0
v1.3.0
v1.2.0
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.1
v1.0.0
Others providing
Compare all 2 on the Deployment and operator page →- @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, btpCLI to build, deploy, migrate and validate MDK projects
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- researched from the npm record: artifact_type corrected to package (it is a library a VS Code extension calls, not something cds.requires loads), ecosystem corrected to btp to match the other MDK-related artifacts already in the graph (sap-mdk-mcp-server, sap-samples-cloud-mdk-samples).
- First seen.
For your agent
- Ref
artifact:sap-artifact-management- JSON
- /artifacts/sap-artifact-management.json
- MCP
- Connecting an agent