UPDATESERVICEPIPELINE()`¶

About UpdateServicePipeline¶

Update the service pipeline.

There are four modes for updating a service pipeline. The deploymentType field defines the mode.

NONE

In this mode, a deployment doesn't occur. Only the requested metadata parameters are updated.

CURRENT_VERSION

In this mode, the service pipeline is deployed and updated with the new spec that you provide. Only requested parameters are updated. Don’t include major or minor version parameters when you use this deployment-type.

MINOR_VERSION

In this mode, the service pipeline is deployed and updated with the published, recommended (latest) minor version of the current major version in use, by default. You can specify a different minor version of the current major version in use.

MAJOR_VERSION

In this mode, the service pipeline is deployed and updated with the published, recommended (latest) major and minor version of the current template by default. You can specify a different major version that's higher than the major version in use and a minor version.

Method Signature¶

METHODS /AWS1/IF_PRN~UPDATESERVICEPIPELINE
  IMPORTING
    !IV_SERVICENAME TYPE /AWS1/PRNRESOURCENAME OPTIONAL
    !IV_SPEC TYPE /AWS1/PRNSPECCONTENTS OPTIONAL
    !IV_DEPLOYMENTTYPE TYPE /AWS1/PRNDEPLOYMENTUPDATETYPE OPTIONAL
    !IV_TEMPLATEMAJORVERSION TYPE /AWS1/PRNTEMPLATEVERSIONPART OPTIONAL
    !IV_TEMPLATEMINORVERSION TYPE /AWS1/PRNTEMPLATEVERSIONPART OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_prnupdsvcplinoutput
  RAISING
    /AWS1/CX_PRNACCESSDENIEDEX
    /AWS1/CX_PRNCONFLICTEXCEPTION
    /AWS1/CX_PRNINTERNALSERVEREX
    /AWS1/CX_PRNRESOURCENOTFOUNDEX
    /AWS1/CX_PRNTHROTTLINGEX
    /AWS1/CX_PRNVALIDATIONEX
    /AWS1/CX_PRNCLIENTEXC
    /AWS1/CX_PRNSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING¶

Required arguments:¶

`iv_servicename` `TYPE /AWS1/PRNRESOURCENAME` `/AWS1/PRNRESOURCENAME`¶

The name of the service to that the pipeline is associated with.

`iv_spec` `TYPE /AWS1/PRNSPECCONTENTS` `/AWS1/PRNSPECCONTENTS`¶

The spec for the service pipeline to update.

`iv_deploymenttype` `TYPE /AWS1/PRNDEPLOYMENTUPDATETYPE` `/AWS1/PRNDEPLOYMENTUPDATETYPE`¶

The deployment type.

There are four modes for updating a service pipeline. The deploymentType field defines the mode.

NONE

In this mode, a deployment doesn't occur. Only the requested metadata parameters are updated.

CURRENT_VERSION

In this mode, the service pipeline is deployed and updated with the new spec that you provide. Only requested parameters are updated. Don’t include major or minor version parameters when you use this deployment-type.

MINOR_VERSION

In this mode, the service pipeline is deployed and updated with the published, recommended (latest) minor version of the current major version in use, by default. You can specify a different minor version of the current major version in use.

MAJOR_VERSION

In this mode, the service pipeline is deployed and updated with the published, recommended (latest) major and minor version of the current template, by default. You can specify a different major version that's higher than the major version in use and a minor version.

Optional arguments:¶

`iv_templatemajorversion` `TYPE /AWS1/PRNTEMPLATEVERSIONPART` `/AWS1/PRNTEMPLATEVERSIONPART`¶

The major version of the service template that was used to create the service that the pipeline is associated with.

`iv_templateminorversion` `TYPE /AWS1/PRNTEMPLATEVERSIONPART` `/AWS1/PRNTEMPLATEVERSIONPART`¶

The minor version of the service template that was used to create the service that the pipeline is associated with.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_prnupdsvcplinoutput` `/AWS1/CL_PRNUPDSVCPLINOUTPUT`¶

Domain /AWS1/RT_ACCOUNT_ID

Primitive Type NUMC

Examples¶

Syntax Example¶

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

DATA(lo_result) = lo_client->updateservicepipeline(
  iv_deploymenttype = |string|
  iv_servicename = |string|
  iv_spec = |string|
  iv_templatemajorversion = |string|
  iv_templateminorversion = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lo_servicepipeline = lo_result->get_pipeline( ).
  IF lo_servicepipeline IS NOT INITIAL.
    lv_arn = lo_servicepipeline->get_arn( ).
    lv_timestamp = lo_servicepipeline->get_createdat( ).
    lv_timestamp = lo_servicepipeline->get_lastdeploymentattempte00( ).
    lv_timestamp = lo_servicepipeline->get_lastdeploymentsuccat( ).
    lv_resourcename = lo_servicepipeline->get_templatename( ).
    lv_templateversionpart = lo_servicepipeline->get_templatemajorversion( ).
    lv_templateversionpart = lo_servicepipeline->get_templateminorversion( ).
    lv_deploymentstatus = lo_servicepipeline->get_deploymentstatus( ).
    lv_statusmessage = lo_servicepipeline->get_deploymentstatusmessage( ).
    lv_speccontents = lo_servicepipeline->get_spec( ).
    lv_deploymentid = lo_servicepipeline->get_lastattempteddeploymen00( ).
    lv_deploymentid = lo_servicepipeline->get_lastsuccdeploymentid( ).
  ENDIF.
ENDIF.

/AWS1/IF_PRN=>UPDATESERVICEPIPELINE()¶