/AWS1/IF_GDY=>UPDATEIPSET()¶
About UpdateIPSet¶
Updates the IPSet specified by the IPSet ID.
Method Signature¶
METHODS /AWS1/IF_GDY~UPDATEIPSET
IMPORTING
!IV_DETECTORID TYPE /AWS1/GDYDETECTORID OPTIONAL
!IV_IPSETID TYPE /AWS1/GDYSTRING OPTIONAL
!IV_NAME TYPE /AWS1/GDYNAME OPTIONAL
!IV_LOCATION TYPE /AWS1/GDYLOCATION OPTIONAL
!IV_ACTIVATE TYPE /AWS1/GDYBOOLEAN OPTIONAL
!IV_EXPECTEDBUCKETOWNER TYPE /AWS1/GDYACCOUNTID OPTIONAL
RETURNING
VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_gdyupdateipsetrsp
RAISING
/AWS1/CX_GDYACCESSDENIEDEX
/AWS1/CX_GDYBADREQUESTEX
/AWS1/CX_GDYINTERNALSERVERER00
/AWS1/CX_GDYCLIENTEXC
/AWS1/CX_GDYSERVEREXC
/AWS1/CX_RT_TECHNICAL_GENERIC
/AWS1/CX_RT_SERVICE_GENERIC.
IMPORTING¶
Required arguments:¶
iv_detectorid TYPE /AWS1/GDYDETECTORID /AWS1/GDYDETECTORID¶
The detectorID that specifies the GuardDuty service whose IPSet you want to update.
To find the
detectorIdin the current Region, see the Settings page in the GuardDuty console, or run the ListDetectors API.
iv_ipsetid TYPE /AWS1/GDYSTRING /AWS1/GDYSTRING¶
The unique ID that specifies the IPSet that you want to update.
Optional arguments:¶
iv_name TYPE /AWS1/GDYNAME /AWS1/GDYNAME¶
The unique ID that specifies the IPSet that you want to update.
iv_location TYPE /AWS1/GDYLOCATION /AWS1/GDYLOCATION¶
The updated URI of the file that contains the IPSet.
iv_activate TYPE /AWS1/GDYBOOLEAN /AWS1/GDYBOOLEAN¶
The updated Boolean value that specifies whether the IPSet is active or not.
iv_expectedbucketowner TYPE /AWS1/GDYACCOUNTID /AWS1/GDYACCOUNTID¶
The Amazon Web Services account ID that owns the Amazon S3 bucket specified in the location parameter.
RETURNING¶
oo_output TYPE REF TO /aws1/cl_gdyupdateipsetrsp /AWS1/CL_GDYUPDATEIPSETRSP¶
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->updateipset(
iv_activate = ABAP_TRUE
iv_detectorid = |string|
iv_expectedbucketowner = |string|
iv_ipsetid = |string|
iv_location = |string|
iv_name = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
ENDIF.