neo-deploy-mta-oauth

CLI tool for deploying MTAs to SAP BTP, Neo environment.

Motivation

1. SAP BTP, Neo environment is not going away anytime soon;

2. The official Neo console client uses basic authentication, which adds a burden of maintaining an user account for CI pipelines;

3. Project Piper's CLI still does not expose the neoDeploy step as a command, so the only way to use it is through Jenkins.

How it works

Same logic as implemented in the deployWithBearerToken method from the neoDeploy step.

Usage

Prerequisite

Have an OAuth API client ready for your subaccount. Follow step 1 on the help document.
When assigning scopes, make sure to:

1. give the client a meaningful description; and
2. select the Solution Lifecycle Management API scopes (Read Multi-Target Applications and Manage Multi-Target Applications).

Installation

# install the tool globally
npm install --global neo-deploy-mta-oauth

# or locally as a dev dependency
npm install --save-dev neo-deploy-mta-oauth

CLI

Example usage:

ndmo -a abcde12345 -h myregion.hana.ondemand.com -i abcd1234-ab12-cd34-ef56-abcdef123456 -s dcba4321-ba21-dc43-fe65-fedcba654321 path/to/my/file.mtar

Arguments can be provided as CLI options or environment variables. Each CLI option provided overrides the corresponding environment variable.

• -a, --account <subaccount> (environment variable: NDMO_ACCOUNT)
  Subaccount technical name, as displayed under the "Subaccount Info" section on the subaccount Overview page.

• -h, --host <host> (environment variable: NDMO_HOST)
  Region host, as described in the documentation.

• -i, --client-id <clientid> (environment variable: NDMO_CLIENT_ID)
  OAuth client ID for the API client.

• -s, --client-secret <clientsecret> (environment variable: NDMO_CLIENT_SECRET)
  OAuth client secret for the API client.