cikraft

Automatically deploy your typesafe generated Integration Flows at the SAP Integration Suite with Gradle.

Name

cikraft comes from:

  • the (old) name SAP Cloud Integration (SAP CI)

  • the option to deploy your IFlows via Continuous Integration (CI)

  • to craft an IFlow using a type safe dsl written in Kotlin

  • and the German word Kraft (power) because this framework is very powerful and SAP SE is a German based corporation

All modules:

Link copied to clipboard

Ktor client api for the SAP-CI OData API.

Link copied to clipboard

Shared data models used by generator and internal-api-runtime to not share the network libraries/kotlin-poet.

Link copied to clipboard
Link copied to clipboard
Link copied to clipboard

The Gradle plugin creates an extension to define your IFlows, Proxies and stages in your Gradle script to automate your deployment.

Link copied to clipboard

The workers are extracted into its own module to support a lower JVM target.

Link copied to clipboard
Link copied to clipboard

The kotlin compiler plugin validates functions annotated with app.softwork.cikraft.ScriptEntry.

Link copied to clipboard

The ksp plugin extracts the meta information (Camel body, headers, properties and parameters) for each Kotlin function annotated with @ScriptEntry. These information are used by the gradle-plugin to generate a GroovyScript that calls the Kotlin function with the required parameters.

Link copied to clipboard

This module provides a Ktor server engine to use the SAP CI as a webserver with a Ktor server application.

Link copied to clipboard
Link copied to clipboard
Link copied to clipboard
Link copied to clipboard