wait_until_stack_exists
async
¶
wait_until_stack_exists(
*,
max_wait_time: float,
min_delay: float = 5,
max_delay: float = 120,
config_overrides: Optional[AsyncCloudFormationClientConfig] = None,
stack_name: Optional[StackName] = None,
next_token: Optional[NextToken] = None,
) -> DescribeStacksOutput
Wait for stack_exists.
Parameters:
-
max_wait_time(float) –Maximum total seconds to wait before raising WaiterTimeoutError.
-
min_delay(float, default:5) –Minimum seconds between operation attempts (spec default 2).
-
max_delay(float, default:120) –Maximum seconds between operation attempts (spec default 120).
-
stack_name(Optional[StackName], default:None) –If you don't pass a parameter to
StackName, the API returns a response that describes all resources in the account, which can impact performance. This requiresListStacksandDescribeStackspermissions.Consider using the ListStacks API if you're not passing a parameter to
StackName.The IAM policy below can be added to IAM policies when you want to limit resource-level permissions and avoid returning a response when no parameter is sent in the request:
{ "Version": "2012-10-17", "Statement": [{ "Effect": "Deny", "Action": "cloudformation:DescribeStacks", "NotResource": "arn:aws:cloudformation:::stack//" }] }
The name or the unique stack ID that's associated with the stack, which aren't always interchangeable:
-
Running stacks: You can specify either the stack's name or its unique stack ID.
-
Deleted stacks: You must specify the unique stack ID.
-
-
next_token(Optional[NextToken], default:None) –The token for the next set of items to return. (You received this token from a previous call.)