1
0
mirror of https://github.com/SAP/jenkins-library.git synced 2024-12-14 11:03:09 +02:00
sap-jenkins-library/resources/metadata/integrationArtifactTriggerIntegrationTest.yaml
Jakob Marius Kjaer 452b2a1ef5
refactor: rebranding from scp to btp (#4049)
* refactor: rebranding 

rebranding from SAP Cloud Platform to SAP BTP

* refactor: rebranding from SCP to BTP

Co-authored-by: tiloKo <70266685+tiloKo@users.noreply.github.com>
2022-11-29 09:52:23 +01:00

59 lines
2.3 KiB
YAML

metadata:
name: integrationArtifactTriggerIntegrationTest
description: Test the service endpoint of your iFlow
longDescription: |
With this step you can test your intergration flow exposed by SAP BTP Integration on a tenant using OData API.Learn more about the SAP Cloud Integration remote API for getting service endpoint of deployed integration artifact [here](https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/d1679a80543f46509a7329243b595bdb.html).
spec:
inputs:
secrets:
- name: integrationFlowServiceKeyCredentialsId
description: Jenkins secret text credential ID containing the service key to the Process Integration Runtime service instance of plan 'integration-flow'
type: jenkins
params:
- name: integrationFlowServiceKey
type: string
description: Service key JSON string to access the Process Integration Runtime service instance of plan 'integration-flow'
scope:
- PARAMETERS
mandatory: true
secret: true
resourceRef:
- name: integrationFlowServiceKeyCredentialsId
type: secret
param: integrationFlowServiceKey
- name: integrationFlowId
type: string
description: Specifies the ID of the Integration Flow artifact
scope:
- PARAMETERS
- STAGES
- STEPS
- GENERAL
mandatory: true
- name: integrationFlowServiceEndpointUrl
resourceRef:
- name: commonPipelineEnvironment
param: custom/integrationFlowServiceEndpoint
type: string
description: Specifies the URL endpoint of the iFlow. Please provide in the format `<protocol>://<host>:<port>`. Supported protocols are `http` and `https`.
scope:
- PARAMETERS
mandatory: true
- name: contentType
type: string
description: Specifies the content type of the file defined in messageBodyPath e.g. application/json
scope:
- PARAMETERS
- STAGES
- STEPS
mandatory: false
- name: messageBodyPath
type: string
description: Speficfies the relative file path to the message body.
scope:
- PARAMETERS
- STAGES
- STEPS
mandatory: false