/AWS1/CL_EC2=>MODIFYMANAGEDPREFIXLIST()

About ModifyManagedPrefixList

Modifies the specified managed prefix list.

Adding or removing entries in a prefix list creates a new version of the prefix list. Changing the name of the prefix list does not affect the version.

If you specify a current version number that does not match the true current version number, the request fails.

Method Signature

IMPORTING

Required arguments:

iv_prefixlistid TYPE /AWS1/EC2PREFIXLISTRESOURCEID /AWS1/EC2PREFIXLISTRESOURCEID

The ID of the prefix list.

Optional arguments:

iv_dryrun TYPE /AWS1/EC2BOOLEAN /AWS1/EC2BOOLEAN

Checks whether you have the required permissions for the action, without actually making the request, and provides an error response. If you have the required permissions, the error response is DryRunOperation. Otherwise, it is UnauthorizedOperation.

iv_currentversion TYPE /AWS1/EC2LONG /AWS1/EC2LONG

The current version of the prefix list.

iv_prefixlistname TYPE /AWS1/EC2STRING /AWS1/EC2STRING

A name for the prefix list.

it_addentries TYPE /AWS1/CL_EC2ADDPREFIXLISTENTRY=>TT_ADDPREFIXLISTENTRIES TT_ADDPREFIXLISTENTRIES

One or more entries to add to the prefix list.

it_removeentries TYPE /AWS1/CL_EC2REMPREFIXLISTENTRY=>TT_REMOVEPREFIXLISTENTRIES TT_REMOVEPREFIXLISTENTRIES

One or more entries to remove from the prefix list.

iv_maxentries TYPE /AWS1/EC2INTEGER /AWS1/EC2INTEGER

The maximum number of entries for the prefix list. You cannot modify the entries
of a prefix list and modify the size of a prefix list at the same time.

If any of the resources that reference the prefix list cannot support the new maximum size, the modify operation fails. Check the state message for the IDs of the first ten resources that do not support the new maximum size.

RETURNING

oo_output TYPE REF TO /aws1/cl_ec2modmanagedprefix01 /AWS1/CL_EC2MODMANAGEDPREFIX01

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->/aws1/if_ec2~modifymanagedprefixlist(
  it_addentries = VALUE /aws1/cl_ec2addprefixlistentry=>tt_addprefixlistentries(
    (
      new /aws1/cl_ec2addprefixlistentry(
        iv_cidr = |string|
        iv_description = |string|
      )
    )
  )
  it_removeentries = VALUE /aws1/cl_ec2remprefixlistentry=>tt_removeprefixlistentries(
    ( new /aws1/cl_ec2remprefixlistentry( |string| ) )
  )
  iv_currentversion = 123
  iv_dryrun = ABAP_TRUE
  iv_maxentries = 123
  iv_prefixlistid = |string|
  iv_prefixlistname = |string|
).

This is an example of reading all possible response values

lv_prefixlistresourceid = lo_managedprefixlist->get_prefixlistid( ).
lv_string = lo_managedprefixlist->get_addressfamily( ).
lv_prefixliststate = lo_managedprefixlist->get_state( ).
lv_string = lo_managedprefixlist->get_statemessage( ).
lv_resourcearn = lo_managedprefixlist->get_prefixlistarn( ).
lv_string = lo_managedprefixlist->get_prefixlistname( ).
lv_integer = lo_managedprefixlist->get_maxentries( ).
lv_long = lo_managedprefixlist->get_version( ).
LOOP AT lo_managedprefixlist->get_tags( ) into lo_row.
  lv_string = lo_row_1->get_key( ).
  lv_string = lo_row_1->get_value( ).
ENDLOOP.
lv_string = lo_managedprefixlist->get_ownerid( ).