DELETESTACK()`¶

About DeleteStack¶

Deletes a specified stack. Once the call completes successfully, stack deletion starts. Deleted stacks don't show up in the DescribeStacks operation if the deletion has been completed successfully.

For more information about deleting a stack, see Delete a stack from the CloudFormation console in the CloudFormation User Guide.

Method Signature¶

IMPORTING¶

Required arguments:¶

`iv_stackname` `TYPE /AWS1/FRMSTACKNAME` `/AWS1/FRMSTACKNAME`¶

The name or the unique stack ID that's associated with the stack.

Optional arguments:¶

`it_retainresources` `TYPE /AWS1/CL_FRMRETAINRESOURCES_W=>TT_RETAINRESOURCES` `TT_RETAINRESOURCES`¶

For stacks in the DELETE_FAILED state, a list of resource logical IDs that are associated with the resources you want to retain. During deletion, CloudFormation deletes the stack but doesn't delete the retained resources.

Retaining resources is useful when you can't delete a resource, such as a non-empty S3 bucket, but you want to delete the stack.

`iv_rolearn` `TYPE /AWS1/FRMROLEARN` `/AWS1/FRMROLEARN`¶

The Amazon Resource Name (ARN) of an IAM role that CloudFormation assumes to delete the stack. CloudFormation uses the role's credentials to make calls on your behalf.

If you don't specify a value, CloudFormation uses the role that was previously associated with the stack. If no role is available, CloudFormation uses a temporary session that's generated from your user credentials.

`iv_clientrequesttoken` `TYPE /AWS1/FRMCLIENTREQUESTTOKEN` `/AWS1/FRMCLIENTREQUESTTOKEN`¶

A unique identifier for this DeleteStack request. Specify this token if you plan to retry requests so that CloudFormation knows that you're not attempting to delete a stack with the same name. You might retry DeleteStack requests to ensure that CloudFormation successfully received them.

All events initiated by a given stack operation are assigned the same client request token, which you can use to track operations. For example, if you execute a CreateStack operation with the token token1, then all the StackEvents generated by that operation will have ClientRequestToken set as token1.

In the console, stack operations display the client request token on the Events tab. Stack operations that are initiated from the console use the token format Console-StackOperation-ID, which helps you easily identify the stack operation . For example, if you create a stack using the console, each stack event would be assigned the same token in the following format: Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002.

`iv_deletionmode` `TYPE /AWS1/FRMDELETIONMODE` `/AWS1/FRMDELETIONMODE`¶

Specifies the deletion mode for the stack. Possible values are:

STANDARD - Use the standard behavior. Specifying this value is the same as not specifying this parameter.

FORCE_DELETE_STACK - Delete the stack if it's stuck in a DELETE_FAILED state due to resource deletion failure.

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.

lo_client->/aws1/if_frm~deletestack(
  it_retainresources = VALUE /aws1/cl_frmretainresources_w=>tt_retainresources(
    ( new /aws1/cl_frmretainresources_w( |string| ) )
  )
  iv_clientrequesttoken = |string|
  iv_deletionmode = |string|
  iv_rolearn = |string|
  iv_stackname = |string|
).

/AWS1/CL_FRM=>DELETESTACK()¶