Skip to content

API for AWS CodeConnections

ABAP Package /AWS1/API_CON_IMPL
ABAP SDK "TLA" CON
ABAP Interface /AWS1/IF_CON

The "TLA" is a Three Letter Abbreviation that appears in ABAP class names, data dictionary objects and other ABAP objects throughout the AWS SDK for SAP ABAP. The TLA for AWS CodeConnections is CON. This TLA helps squeeze ABAP objects into the 30-character length limit of the ABAP data dictionary.

Installation

To install the AWS SDK for SAP ABAP, import the Core transport, along with the transport for the CodeConnections module and other API modules you are interested in. A few modules are included in the Core transport itself. For more information, see the Developer Guide guide.

About The Service

AWS CodeConnections

This Amazon Web Services CodeConnections API Reference provides descriptions and usage examples of the operations and data types for the Amazon Web Services CodeConnections API. You can use the connections API to work with connections and installations.

Connections are configurations that you use to connect Amazon Web Services resources to external code repositories. Each connection is a resource that can be given to services such as CodePipeline to connect to a third-party repository such as Bitbucket. For example, you can add the connection in CodePipeline so that it triggers your pipeline when a code change is made to your third-party code repository. Each connection is named and associated with a unique ARN that is used to reference the connection.

When you create a connection, the console initiates a third-party connection handshake. Installations are the apps that are used to conduct this handshake. For example, the installation for the Bitbucket provider type is the Bitbucket app. When you create a connection, you can choose an existing installation or create one.

When you want to create a connection to an installed provider type such as GitHub Enterprise Server, you create a host for your connections.

You can work with connections by calling:

  • CreateConnection, which creates a uniquely named connection that can be referenced by services such as CodePipeline.

  • DeleteConnection, which deletes the specified connection.

  • GetConnection, which returns information about the connection, including the connection status.

  • ListConnections, which lists the connections associated with your account.

You can work with hosts by calling:

  • CreateHost, which creates a host that represents the infrastructure where your provider is installed.

  • DeleteHost, which deletes the specified host.

  • GetHost, which returns information about the host, including the setup status.

  • ListHosts, which lists the hosts associated with your account.

You can work with tags in Amazon Web Services CodeConnections by calling the following:

  • ListTagsForResource, which gets information about Amazon Web Services tags for a specified Amazon Resource Name (ARN) in Amazon Web Services CodeConnections.

  • TagResource, which adds or updates tags for a resource in Amazon Web Services CodeConnections.

  • UntagResource, which removes tags for a resource in Amazon Web Services CodeConnections.

For information about how to use Amazon Web Services CodeConnections, see the Developer Tools User Guide.

Using the SDK

In your code, create a client using the SDK module for AWS CodeConnections, which is created with factory method /AWS1/CL_CON_FACTORY=>create(). In this example we will assume you have configured an SDK profile in transaction /AWS1/IMG called ZFINANCE.

DATA(go_session)   = /aws1/cl_rt_session_aws=>create( 'ZFINANCE' ).
DATA(go_con)       = /aws1/cl_con_factory=>create( go_session ).

Your variable go_con is an instance of /AWS1/IF_CON, and all of the operations in the AWS CodeConnections service are accessed by calling methods in /AWS1/IF_CON.

API Operations

For an overview of ABAP method calls corresponding to API operations in AWS CodeConnections, see the Operation List.

Factory Method

/AWS1/CL_CON_FACTORY=>create( )

Creates an object of type /AWS1/IF_CON.

IMPORTING

Optional arguments:

IV_PROTOCOL TYPE /AWS1/RT_PROTOCOL /AWS1/RT_PROTOCOL

IO_SESSION TYPE REF TO /AWS1/CL_RT_SESSION_BASE /AWS1/CL_RT_SESSION_BASE

IV_REGION TYPE /AWS1/RT_REGION_ID /AWS1/RT_REGION_ID

IV_CUSTOM_ENDPOINT TYPE /AWS1/RT_ENDPOINT /AWS1/RT_ENDPOINT

RETURNING

OO_CLIENT TYPE REF TO /AWS1/IF_CON /AWS1/IF_CON

/AWS1/IF_CON represents the ABAP client for the CodeConnections service, representing each operation as a method call. For more information see the API Page page.

Configuring Programmatically

DATA(lo_config) = DATA(go_con)->get_config( ).

lo_config is a variable of type /AWS1/CL_CON_CONFIG. See the documentation for /AWS1/CL_CON_CONFIG for details on the settings that can be configured.

Paginators

Paginators for AWS CodeConnections can be created via get_paginator() which returns a paginator object of type /AWS1/IF_CON_PAGINATOR. The operation method that is being paginated is called using the paginator object, which accepts any necessary parameters to provide to the underlying API operation. This returns an iterator object which can be used to iterate over paginated results using has_next() and get_next() methods.

Details about the paginator methods available for service AWS CodeConnections can be found in interface /AWS1/IF_CON_PAGINATOR.