actions-marketplace-validations/deploy-to-sap-btp-with-ctms
GitHub Action to deploy application archives (MTAR files) to SAP BTP via SAP Cloud Transport Management Service (CTMS)
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Apr 30, 2025
- License
- MIT
Pinned Snippet
uses: actions-marketplace-validations/mauriciolauffer_deploy-to-sap-btp-with-ctms@95425a4ca45f844cfe480acf1deca0d58bb4e14d # no releases — HEAD as of 2026-07-12tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| CTMS_TOKEN_SERVICE_URL | Value of url (within the uaa section) from the service key of your CTMS instance. | yes | — |
| CTMS_CLIENT_ID | Value of clientid from the service key of your CTMS instance. | yes | — |
| CTMS_CLIENT_SECRET | Value of clientsecret (within the uaa section) from the service key. | yes | — |
| CTMS_API_URL | Value of uri from the service key of your CTMS instance. | yes | — |
| CTMS_NODE_NAME | The name of the target Transport Node in CTMS where the archive should be imported | yes | — |
| CTMS_FILE_PATH | Path within the runner's workspace to the application archive file (e.g., app.mtar, my-app.zip) | yes | — |
| CTMS_TR_DESCRIPTION | Description for the transport request created in CTMS | yes | — |
| CTMS_TR_CONTENT_TYPE | Content type of the archive. Must be one of: MTA, XSCDU, APP | yes | — |
| CTMS_TR_STORAGE_TYPE | Storage type for the transport request. Must be one of: FILE, REFERENCE. Typically FILE for direct uploads | yes | — |
| CTMS_TR_USER_NAME | Optional user name displayed in the Cloud Transport Management UI. If omitted, the authentication user may be shown. | no | — |
Outputs
| name | description |
|---|---|
| CTMS_NODE_ID | ID of Transport Node where content was put in |
| CTMS_NODE_NAME | Name of Transport Node where content was put in |
| CTMS_QUEUE_ID | ID of Import Queue of the Transport Node |