LISTRESOLVERRULEASSOCIATIONS()`¶

About ListResolverRuleAssociations¶

Lists the associations that were created between Resolver rules and VPCs using the current Amazon Web Services account.

Method Signature¶

METHODS /AWS1/IF_R5R~LISTRESOLVERRULEASSOCIATIONS
  IMPORTING
    !IV_MAXRESULTS TYPE /AWS1/R5RMAXRESULTS OPTIONAL
    !IV_NEXTTOKEN TYPE /AWS1/R5RNEXTTOKEN OPTIONAL
    !IT_FILTERS TYPE /AWS1/CL_R5RFILTER=>TT_FILTERS OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_r5rlstresolverrlass01
  RAISING
    /AWS1/CX_R5RINTERNALSVCERROREX
    /AWS1/CX_R5RINVALIDNEXTTOKENEX
    /AWS1/CX_R5RINVALIDPARAMETEREX
    /AWS1/CX_R5RINVALIDREQUESTEX
    /AWS1/CX_R5RTHROTTLINGEX
    /AWS1/CX_R5RCLIENTEXC
    /AWS1/CX_R5RSERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING¶

Optional arguments:¶

`iv_maxresults` `TYPE /AWS1/R5RMAXRESULTS` `/AWS1/R5RMAXRESULTS`¶

The maximum number of rule associations that you want to return in the response to a ListResolverRuleAssociations request. If you don't specify a value for MaxResults, Resolver returns up to 100 rule associations.

`iv_nexttoken` `TYPE /AWS1/R5RNEXTTOKEN` `/AWS1/R5RNEXTTOKEN`¶

For the first ListResolverRuleAssociation request, omit this value.

If you have more than MaxResults rule associations, you can submit another ListResolverRuleAssociation request to get the next group of rule associations. In the next request, specify the value of NextToken from the previous response.

`it_filters` `TYPE /AWS1/CL_R5RFILTER=>TT_FILTERS` `TT_FILTERS`¶

An optional specification to return a subset of Resolver rules, such as Resolver rules that are associated with the same VPC ID.

If you submit a second or subsequent ListResolverRuleAssociations request and specify the NextToken parameter, you must use the same values for Filters, if any, as in the previous request.

RETURNING¶

`oo_output` `TYPE REF TO /aws1/cl_r5rlstresolverrlass01` `/AWS1/CL_R5RLSTRESOLVERRLASS01`¶

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->listresolverruleassociations(
  it_filters = VALUE /aws1/cl_r5rfilter=>tt_filters(
    (
      new /aws1/cl_r5rfilter(
        it_values = VALUE /aws1/cl_r5rfiltervalues_w=>tt_filtervalues(
          ( new /aws1/cl_r5rfiltervalues_w( |string| ) )
        )
        iv_name = |string|
      )
    )
  )
  iv_maxresults = 123
  iv_nexttoken = |string|
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
  lv_nexttoken = lo_result->get_nexttoken( ).
  lv_maxresults = lo_result->get_maxresults( ).
  LOOP AT lo_result->get_resolverruleassociations( ) into lo_row.
    lo_row_1 = lo_row.
    IF lo_row_1 IS NOT INITIAL.
      lv_resourceid = lo_row_1->get_id( ).
      lv_resourceid = lo_row_1->get_resolverruleid( ).
      lv_name = lo_row_1->get_name( ).
      lv_resourceid = lo_row_1->get_vpcid( ).
      lv_resolverruleassociation = lo_row_1->get_status( ).
      lv_statusmessage = lo_row_1->get_statusmessage( ).
    ENDIF.
  ENDLOOP.
ENDIF.

/AWS1/IF_R5R=>LISTRESOLVERRULEASSOCIATIONS()¶