sapse/application-content-deployer
Application Content Deployer is a library built using Golang offered to facilitate SAP BTP application content import. Here the supported content type is multi media file (.MTAR) that contains deployment descriptor and data belonging to any of the supported SAP BTP application such as Cloud Integration, workflow, HTML5 Repo apps, Portal service etc.
The mtar file would ideally look like this:
├─ *.mtar*/
│ └─ META-INF/
│ ├─ mtad.yaml
│ └─ MANIFEST.MF
├─ content/
| └─ data.zip
└─ content/
└─ data.zip
In order to proceed with deployment, it is essential to have the required environment credentials and the MTAR/ZIP properly mounted and provided to the application. The environment should encompass the essential secrets for both the content provider and content agent. The Application Content Deployer offers the folwwing set of commands:
deploy: Deploy the content using SAP Content Agent Service. version: Prints the version of content agent go deployer. help: Help about any command.
[flags]
[command]
Available Commands:
completion Generate the autocompletion script for the specified shell
deploy Deploy contents using SAP Content Agent Service
help Help about any command
version Prints the version of content agent go deployer
Flags:
-s, --expand-source Display log source file in console output. (default: false)
-h, --help help for this command
-l, --local Enable .env file loader. (default: false)
-v, --verbose Display more verbose output in console output. (default: false)
Use " [command] --help" for more information about a command.
The section helps you understand the prerequisites required to deploy content using the Application Content Deployer.
Service Credentials The Application Content Deployer requires service credentials to authenticate with content agent & different content providers. The service credentials are used to gather the necessary information to deploy the content.
Note: While running with Kyma, the service credentials are provided by the BTP Service Operator once the service binding is created. Note: While running locally, the service credentials must be provided. It should be collated into a single folder & provided as an environment variable pointing to the folder i.e. SERVICE_BINDING_ROOT. As an alternative, the service credentials can also be provided in CF format as part of the environment variables i.e. VCAP_SERVICES.
docker pull sapse/application-content-deployer