@rizing/cds-customer-stepbystep-tool
A tool that checks and completes the deployment configuration of a CAP project, written for Rizing's step-by-step CAP training, last released August 2023 from a repository since deleted.
Runs over a project root and applies the adjustments the training would otherwise have you make by hand, so the exercise is about what changed rather than about typing it.
Facts
Where it sits
Who is behind it
Before choosing this
Conditions
PracticalFunctional boundary
Tied to a specific training repository and last released August 2023. The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2from DeploymentA productive CAP customer application is deployed using materials covered by this agreement.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
- § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
The CAP-specific agreement makes the deployment platform part of the permitted productive-use condition, so deployment choices need the applicable agreement checked rather than treated as purely technical.
SAP Developer License Agreement 3.2 CAP →What it declares
Every artifact
- Type
- Generator
- Origin
- Independently maintained
- Runtime
- build time
As a generator
- Generates
- does not say
- Run with
- does not say
- Distributed through
- does not say
Connections
Getting an application onto a runtime and keeping it there
Download
Install
npm add @rizing/cds-customer-stepbystep-toolDerived from the package name. No recipe recorded; the README has the configuration.
History
Others providing
Compare all 7 on the Deployment page →- Application AutoscalerApplication AutoscalerA Cloud Foundry service that raises or lowers the number of an application's instances by the scaling rules and schedules in a policy the developer defines.sap official, btpScales Cloud Foundry app instances by policy rules and schedulesfrom BTP/BAIP
- SAP Cloud Transport ManagementSAP Cloud Transport ManagementMoves software deliverables between SAP BTP accounts along a modelled landscape of transport nodes and routes: Multitarget Application archives, and application-specific content such as SAP Cloud Integration iFlows.sap official, btpMoves MTA archives and content between SAP BTP accountsfrom BTP/BAIP
- SAP Content Agent ServiceSAP Content Agent ServiceA BTP service that assembles content from other BTP services into an MTAR with its dependencies, then downloads it, exports it to a transport queue or imports it into another subaccount.sap official, btpAssembles BTP service content into an MTAR for transportfrom BTP/BAIP
- SAP Solution Lifecycle Management service for SAP BTPSAP Solution Lifecycle Management service for SAP BTPDeploys, updates, monitors and deletes Solutions in the Neo environment of SAP BTP, each carried by a Multitarget Application archive, and subscribes a subaccount to a multitenant Solution provided by another.sap official, btpDeploys and manages MTA-based Solutions in the Neo environmentfrom BTP/BAIP
- @cap-js/cap-operator-plugin@cap-js/cap-operator-pluginGenerates Helm charts for deploying CAP applications with the CAP Operator on Kubernetes.sap official, capGenerates Helm charts for the CAP Operator on Kubernetesfrom CAP
- @sap/cds-dk@sap/cds-dkThe command line client and development toolkit for CAP projects, with the commands cds build, cds deploy, cds watch and cds add among them.sap official, capCommand line client and development toolkit for CAPfrom CAP
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
- 404 from the GitHub API. Found by the first full run of scripts/check-links.mjs — the citation had a checked date and nobody had re-read it.
- First seen.
For your agent
- Ref
artifact:rizing-cds-customer-stepbystep-tool- JSON
- /artifacts/rizing-cds-customer-stepbystep-tool.json
- MCP
- Connecting an agent