/AWS1/IF_FRM=>DETECTSTACKDRIFT()
¶
About DetectStackDrift¶
Detects whether a stack's actual configuration differs, or has drifted, from its expected configuration, as defined in the stack template and any values specified as template parameters. For each resource in the stack that supports drift detection, CloudFormation compares the actual configuration of the resource with its expected template configuration. Only resource properties explicitly defined in the stack template are checked for drift. A stack is considered to have drifted if one or more of its resources differ from their expected template configurations. For more information, see Detect unmanaged configuration changes to stacks and resources with drift detection.
Use DetectStackDrift
to detect drift on all supported resources for a given
stack, or DetectStackResourceDrift to detect drift on individual
resources.
For a list of stack resources that currently support drift detection, see Resource type support for imports and drift detection.
DetectStackDrift
can take up to several minutes, depending on the number of
resources contained within the stack. Use DescribeStackDriftDetectionStatus
to monitor the progress of a detect stack drift operation. Once the drift detection operation
has completed, use DescribeStackResourceDrifts to return drift information
about the stack and its resources.
When detecting drift on a stack, CloudFormation doesn't detect drift on any nested stacks
belonging to that stack. Perform DetectStackDrift
directly on the nested stack
itself.
Method Signature¶
IMPORTING¶
Required arguments:¶
iv_stackname
TYPE /AWS1/FRMSTACKNAMEORID
/AWS1/FRMSTACKNAMEORID
¶
The name of the stack for which you want to detect drift.
Optional arguments:¶
it_logicalresourceids
TYPE /AWS1/CL_FRMLOGICALRESRCIDS_W=>TT_LOGICALRESOURCEIDS
TT_LOGICALRESOURCEIDS
¶
The logical names of any resources you want to use as filters.
RETURNING¶
oo_output
TYPE REF TO /aws1/cl_frmdetectstackdrift01
/AWS1/CL_FRMDETECTSTACKDRIFT01
¶
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_frm~detectstackdrift(
it_logicalresourceids = VALUE /aws1/cl_frmlogicalresrcids_w=>tt_logicalresourceids(
( new /aws1/cl_frmlogicalresrcids_w( |string| ) )
)
iv_stackname = |string|
).
This is an example of reading all possible response values
lo_result = lo_result.
IF lo_result IS NOT INITIAL.
lv_stackdriftdetectionid = lo_result->get_stackdriftdetectionid( ).
ENDIF.