integrationArtifactUpdateConfiguration¶

Update integration flow Configuration parameter

Description¶

With this step you can update the value for a configuration parameters of a designtime integration flow using the OData API. Learn more about the SAP Cloud Integration remote API for configuration update of the integration flow parameter here.

Usage¶

We recommend to define values of step parameters via .pipeline/config.yml file.
In this case, calling the step is essentially reduced to defining the step name.
Calling the step can be done either in an orchestrator specific way (e.g. via a Jenkins library step) or on the command line.

JenkinsCommand Line

library('piper-lib-os')

integrationArtifactUpdateConfiguration script: this

piper integrationArtifactUpdateConfiguration

Prerequisites¶

Parameters¶

Overview - Step¶

Name	Mandatory	Additional information
apiServiceKey	(yes)	pass via ENV or Jenkins credentials (`cpiApiServiceKeyCredentialsId`)
integrationFlowId	yes
integrationFlowVersion	yes
parameterKey	yes
parameterValue	yes
script	(yes)	reference to Jenkins main pipeline script
verbose	no	activates debug output

Overview - Execution Environment¶

Orchestrator-specific only

These parameters are relevant for orchestrator usage and not considered when using the command line option.

Name	Mandatory	Additional information

Details¶

apiServiceKey¶

Service key JSON string to access the Process Integration Runtime service instance of plan 'api'

back to overview

Scope	Details
Aliases	-
Type	`string`
Mandatory	yes
Default	`$PIPER_apiServiceKey` (if set)
Secret	yes
Configuration scope	☒ parameter ☐ general ☐ steps ☐ stages
Resource references	Jenkins credential id: id: `cpiApiServiceKeyCredentialsId` reference to: `apiServiceKey`

integrationFlowId¶

Specifies the ID of the Integration Flow artifact

back to overview

Scope	Details
Aliases	-
Type	`string`
Mandatory	yes
Default	`$PIPER_integrationFlowId` (if set)
Secret	no
Configuration scope	☒ parameter ☒ general ☒ steps ☒ stages
Resource references	none

integrationFlowVersion¶

Specifies the version of the Integration Flow artifact

back to overview

Scope	Details
Aliases	-
Type	`string`
Mandatory	yes
Default	`$PIPER_integrationFlowVersion` (if set)
Secret	no
Configuration scope	☒ parameter ☒ general ☒ steps ☒ stages
Resource references	none

parameterKey¶

Specifies the externalized parameter name.

back to overview

Scope	Details
Aliases	-
Type	`string`
Mandatory	yes
Default	`$PIPER_parameterKey` (if set)
Secret	no
Configuration scope	☒ parameter ☐ general ☒ steps ☒ stages
Resource references	none

parameterValue¶

Specifies the externalized parameter value.

back to overview

Scope	Details
Aliases	-
Type	`string`
Mandatory	yes
Default	`$PIPER_parameterValue` (if set)
Secret	no
Configuration scope	☒ parameter ☐ general ☒ steps ☒ stages
Resource references	none

script¶

Jenkins-specific: Used for proper environment setup.

The common script environment of the Jenkinsfile running. Typically the reference to the script calling the pipeline step is provided with the this parameter, as in script: this. This allows the function to access the commonPipelineEnvironment for retrieving, e.g. configuration parameters.

back to overview

Scope	Details
Aliases	-
Type	`Jenkins Script`
Mandatory	yes
Default
Secret	no
Configuration scope	☐ parameter ☐ general ☐ steps ☐ stages
Resource references	none

verbose¶

verbose output

back to overview

Scope	Details
Aliases	-
Type	`bool`
Mandatory	no
Default	`false`
Possible values	- `true` - `false`
Secret	no
Configuration scope	☒ parameter ☒ general ☒ steps ☒ stages
Resource references	none

cpiApiServiceKeyCredentialsId¶

Jenkins-specific: Used for proper environment setup. See using credentials for details.

Jenkins secret text credential ID containing the service key to the Process Integration Runtime service instance of plan 'api'

back to overview

Scope	Details
Aliases	-
Type	`string`
Configuration scope	☒ parameter ☒ general ☒ steps ☒ stages

Example¶

Example configuration for the use in a Jenkinsfile.

integrationArtifactUpdateConfiguration script: this

Example of a YAML configuration file (such as .pipeline/config.yaml).

steps:
  <...>
  integrationArtifactUpdateConfiguration:
    cpiApiServiceKeyCredentialsId: 'MY_API_SERVICE_KEY'
    integrationFlowId: 'MY_INTEGRATION_FLOW_NAME'
    integrationFlowVersion: 'MY_INTEGRATION_FLOW_VERSION'
    parameterKey: 'MY_INTEGRATION_FLOW_CONFIG_PARAMETER_NAME'
    parameterValue: 'MY_INTEGRATION_FLOW_CONFIG_PARAMETER_VALUE'