/AWS1/IF_R53=>CREATETRAFFICPOLICYVERSION()¶
About CreateTrafficPolicyVersion¶
Creates a new version of an existing traffic policy. When you create a new version of a traffic policy, you specify the ID of the traffic policy that you want to update and a JSON-formatted document that describes the new version. You use traffic policies to create multiple DNS resource record sets for one domain name (such as example.com) or one subdomain name (such as www.example.com). You can create a maximum of 1000 versions of a traffic policy. If you reach the limit and need to create another version, you'll need to start a new traffic policy.
Method Signature¶
METHODS /AWS1/IF_R53~CREATETRAFFICPOLICYVERSION
IMPORTING
!IV_ID TYPE /AWS1/R53TRAFFICPOLICYID OPTIONAL
!IV_DOCUMENT TYPE /AWS1/R53TRAFFICPOLICYDOCUMENT OPTIONAL
!IV_COMMENT TYPE /AWS1/R53TRAFFICPOLICYCOMMENT OPTIONAL
RETURNING
VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_r53cretrafplyvrsrsp
RAISING
/AWS1/CX_R53CONCURRENTMOD
/AWS1/CX_R53INVALIDINPUT
/AWS1/CX_R53INVTRAFPOLICYDOC
/AWS1/CX_R53NOSUCHTRAFPOLICY
/AWS1/CX_R53TOOMANYTRFPLYVRS00
/AWS1/CX_R53CLIENTEXC
/AWS1/CX_R53SERVEREXC
/AWS1/CX_RT_TECHNICAL_GENERIC
/AWS1/CX_RT_SERVICE_GENERIC.
IMPORTING¶
Required arguments:¶
iv_id TYPE /AWS1/R53TRAFFICPOLICYID /AWS1/R53TRAFFICPOLICYID¶
The ID of the traffic policy for which you want to create a new version.
iv_document TYPE /AWS1/R53TRAFFICPOLICYDOCUMENT /AWS1/R53TRAFFICPOLICYDOCUMENT¶
The definition of this version of the traffic policy, in JSON format. You specified the JSON in the
CreateTrafficPolicyVersionrequest. For more information about the JSON format, see CreateTrafficPolicy.
Optional arguments:¶
iv_comment TYPE /AWS1/R53TRAFFICPOLICYCOMMENT /AWS1/R53TRAFFICPOLICYCOMMENT¶
The comment that you specified in the
CreateTrafficPolicyVersionrequest, if any.
RETURNING¶
oo_output TYPE REF TO /aws1/cl_r53cretrafplyvrsrsp /AWS1/CL_R53CRETRAFPLYVRSRSP¶
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->createtrafficpolicyversion(
iv_comment = |string|
iv_document = |string|
iv_id = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
lo_trafficpolicy = lo_result->get_trafficpolicy( ).
IF lo_trafficpolicy IS NOT INITIAL.
lv_trafficpolicyid = lo_trafficpolicy->get_id( ).
lv_trafficpolicyversion = lo_trafficpolicy->get_version( ).
lv_trafficpolicyname = lo_trafficpolicy->get_name( ).
lv_rrtype = lo_trafficpolicy->get_type( ).
lv_trafficpolicydocument = lo_trafficpolicy->get_document( ).
lv_trafficpolicycomment = lo_trafficpolicy->get_comment( ).
ENDIF.
lv_resourceuri = lo_result->get_location( ).
ENDIF.