IntegTestCaseStack

class aws_cdk.integ_tests_alpha.IntegTestCaseStack(scope, id, *, allow_destroy=None, cdk_command_options=None, diff_assets=None, hooks=None, regions=None, stack_update_workflow=None, analytics_reporting=None, cross_region_references=None, description=None, env=None, notification_arns=None, permissions_boundary=None, property_injectors=None, stack_name=None, suppress_template_indentation=None, synthesizer=None, tags=None, termination_protection=None)

Bases: Stack

(experimental) An integration test case stack. Allows the definition of test properties that should apply to this stack.

This should be used if there are multiple stacks in the integration test and it is necessary to specify different test case option for each. Otherwise normal stacks should be added to IntegTest

Stability:: experimental
ExampleMetadata:: infused

Example:

# app: App
# stack_under_test: Stack

test_case_with_assets = IntegTestCaseStack(app, "TestCaseAssets",
    diff_assets=True
)

IntegTest(app, "Integ", test_cases=[stack_under_test, test_case_with_assets])

Parameters:

scope (Construct)
id (str)
allow_destroy (Optional[Sequence[str]]) – List of CloudFormation resource types in this stack that can be destroyed as part of an update without failing the test. This list should only include resources that for this specific integration test we are sure will not cause errors or an outage if destroyed. For example, maybe we know that a new resource will be created first before the old resource is destroyed which prevents any outage. e.g. [‘AWS::IAM::Role’] Default: - do not allow destruction of any resources on update
cdk_command_options (Union[CdkCommands, Dict[str, Any], None]) – Additional options to use for each CDK command. Default: - runner default options
diff_assets (Optional[bool]) – Whether or not to include asset hashes in the diff Asset hashes can introduces a lot of unneccessary noise into tests, but there are some cases where asset hashes should be included. For example any tests involving custom resources or bundling Default: false
hooks (Union[Hooks, Dict[str, Any], None]) – Additional commands to run at predefined points in the test workflow. e.g. { postDeploy: [‘yarn’, ‘test’] } Default: - no hooks
regions (Optional[Sequence[str]]) – Limit deployment to these regions. Default: - can run in any region
stack_update_workflow (Optional[bool]) – Run update workflow on this test case This should only be set to false to test scenarios that are not possible to test as part of the update workflow. Default: true
analytics_reporting (Optional[bool]) – Include runtime versioning information in this Stack. Default: analyticsReporting setting of containing App, or value of ‘aws:cdk:version-reporting’ context key
cross_region_references (Optional[bool]) – Enable this flag to allow native cross region stack references. Enabling this will create a CloudFormation custom resource in both the producing stack and consuming stack in order to perform the export/import This feature is currently experimental Default: false
description (Optional[str]) – A description of the stack. Default: - No description.
env (Union[Environment, Dict[str, Any], None]) – The AWS environment (account/region) where this stack will be deployed. Set the region/account fields of env to either a concrete value to select the indicated environment (recommended for production stacks), or to the values of environment variables CDK_DEFAULT_REGION/CDK_DEFAULT_ACCOUNT to let the target environment depend on the AWS credentials/configuration that the CDK CLI is executed under (recommended for development stacks). If the Stack is instantiated inside a Stage, any undefined region/account fields from env will default to the same field on the encompassing Stage, if configured there. If either region or account are not set nor inherited from Stage, the Stack will be considered “environment-agnostic””. Environment-agnostic stacks can be deployed to any environment but may not be able to take advantage of all features of the CDK. For example, they will not be able to use environmental context lookups such as ec2.Vpc.fromLookup and will not automatically translate Service Principals to the right format based on the environment’s AWS partition, and other such enhancements. Default: - The environment of the containing Stage if available, otherwise create the stack will be environment-agnostic.
notification_arns (Optional[Sequence[str]]) – SNS Topic ARNs that will receive stack events. Default: - no notification arns.
permissions_boundary (Optional[PermissionsBoundary]) – Options for applying a permissions boundary to all IAM Roles and Users created within this Stage. Default: - no permissions boundary is applied
property_injectors (Optional[Sequence[IPropertyInjector]]) – A list of IPropertyInjector attached to this Stack. Default: - no PropertyInjectors
stack_name (Optional[str]) – Name to deploy the stack with. Default: - Derived from construct path.
suppress_template_indentation (Optional[bool]) – Enable this flag to suppress indentation in generated CloudFormation templates. If not specified, the value of the @aws-cdk/core:suppressTemplateIndentation context key will be used. If that is not specified, then the default value false will be used. Default: - the value of @aws-cdk/core:suppressTemplateIndentation, or false if that is not set.
synthesizer (Optional[IStackSynthesizer]) – Synthesis method to use while deploying this stack. The Stack Synthesizer controls aspects of synthesis and deployment, like how assets are referenced and what IAM roles to use. For more information, see the README of the main CDK package. If not specified, the defaultStackSynthesizer from App will be used. If that is not specified, DefaultStackSynthesizer is used if @aws-cdk/core:newStyleStackSynthesis is set to true or the CDK major version is v2. In CDK v1 LegacyStackSynthesizer is the default if no other synthesizer is specified. Default: - The synthesizer specified on App, or DefaultStackSynthesizer otherwise.
tags (Optional[Mapping[str, str]]) – Tags that will be applied to the Stack. These tags are applied to the CloudFormation Stack itself. They will not appear in the CloudFormation template. However, at deployment time, CloudFormation will apply these tags to all resources in the stack that support tagging. You will not be able to exempt resources from tagging (using the excludeResourceTypes property of Tags.of(...).add()) for tags applied in this way. Default: {}
termination_protection (Optional[bool]) – Whether to enable termination protection for this stack. Default: false

Stability:

experimental

Methods

add_dependency(target, reason=None)

Add a dependency between this stack and another stack.

This can be used to define dependencies between any two stacks within an app, and also supports nested stacks.

Parameters:

target (Stack)
reason (Optional[str])

Return type:

None

add_metadata(key, value)

Adds an arbitrary key-value pair, with information you want to record about the stack.

These get translated to the Metadata section of the generated template.

Parameters:

key (str)
value (Any)

See:

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/metadata-section-structure.html

Return type:

None

add_stack_tag(tag_name, tag_value)

Configure a stack tag.

At deploy time, CloudFormation will automatically apply all stack tags to all resources in the stack.

Parameters:

tag_name (str)
tag_value (str)

Return type:

None

add_transform(transform)

Add a Transform to this stack. A Transform is a macro that AWS CloudFormation uses to process your template.

Duplicate values are removed when stack is synthesized.

Parameters:: transform (str) – The transform to add.
See:: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/transform-section-structure.html
Return type:: None

Example:

# stack: Stack

stack.add_transform("AWS::Serverless-2016-10-31")

export_string_list_value(exported_value, *, description=None, name=None)

Create a CloudFormation Export for a string list value.

Returns a string list representing the corresponding Fn.importValue() expression for this Export. The export expression is automatically wrapped with an Fn::Join and the import value with an Fn::Split, since CloudFormation can only export strings. You can control the name for the export by passing the name option.

If you don’t supply a value for name, the value you’re exporting must be a Resource attribute (for example: bucket.bucketName) and it will be given the same name as the automatic cross-stack reference that would be created if you used the attribute in another Stack.

One of the uses for this method is to remove the relationship between two Stacks established by automatic cross-stack references. It will temporarily ensure that the CloudFormation Export still exists while you remove the reference from the consuming stack. After that, you can remove the resource and the manual export.

See exportValue for an example of this process.

Parameters:

exported_value (Any)
description (Optional[str]) – The description of the outputs. Default: - No description
name (Optional[str]) – The name of the export to create. Default: - A name is automatically chosen

Return type:

List[str]

export_value(exported_value, *, description=None, name=None)

Create a CloudFormation Export for a string value.

Returns a string representing the corresponding Fn.importValue() expression for this Export. You can control the name for the export by passing the name option.

If you don’t supply a value for name, the value you’re exporting must be a Resource attribute (for example: bucket.bucketName) and it will be given the same name as the automatic cross-stack reference that would be created if you used the attribute in another Stack.

One of the uses for this method is to remove the relationship between two Stacks established by automatic cross-stack references. It will temporarily ensure that the CloudFormation Export still exists while you remove the reference from the consuming stack. After that, you can remove the resource and the manual export.

Here is how the process works. Let’s say there are two stacks, producerStack and consumerStack, and producerStack has a bucket called bucket, which is referenced by consumerStack (perhaps because an AWS Lambda Function writes into it, or something like that).

It is not safe to remove producerStack.bucket because as the bucket is being deleted, consumerStack might still be using it.

Instead, the process takes two deployments:

Deployment 1: break the relationship:

Make sure consumerStack no longer references bucket.bucketName (maybe the consumer stack now uses its own bucket, or it writes to an AWS DynamoDB table, or maybe you just remove the Lambda Function altogether).
In the ProducerStack class, call this.exportValue(this.bucket.bucketName). This will make sure the CloudFormation Export continues to exist while the relationship between the two stacks is being broken.
Deploy (this will effectively only change the consumerStack, but it’s safe to deploy both).

Deployment 2: remove the bucket resource:

You are now free to remove the bucket resource from producerStack.
Don’t forget to remove the exportValue() call as well.
Deploy again (this time only the producerStack will be changed – the bucket will be deleted).

Parameters:

exported_value (Any)
description (Optional[str]) – The description of the outputs. Default: - No description
name (Optional[str]) – The name of the export to create. Default: - A name is automatically chosen

Return type:

str

format_arn(*, resource, service, account=None, arn_format=None, partition=None, region=None, resource_name=None)

Creates an ARN from components.

If partition, region or account are not specified, the stack’s partition, region and account will be used.

If any component is the empty string, an empty string will be inserted into the generated ARN at the location that component corresponds to.

The ARN will be formatted as follows:

arn:{partition}:{service}:{region}:{account}:{resource}{sep}{resource-name}

The required ARN pieces that are omitted will be taken from the stack that the ‘scope’ is attached to. If all ARN pieces are supplied, the supplied scope can be ‘undefined’.

Parameters:

resource (str) – Resource type (e.g. “table”, “autoScalingGroup”, “certificate”). For some resource types, e.g. S3 buckets, this field defines the bucket name.
service (str) – The service namespace that identifies the AWS product (for example, ‘s3’, ‘iam’, ‘codepipeline’).
account (Optional[str]) – The ID of the AWS account that owns the resource, without the hyphens. For example, 123456789012. Note that the ARNs for some resources don’t require an account number, so this component might be omitted. Default: The account the stack is deployed to.
arn_format (Optional[ArnFormat]) – The specific ARN format to use for this ARN value. Default: - uses value of sep as the separator for formatting, ArnFormat.SLASH_RESOURCE_NAME if that property was also not provided
partition (Optional[str]) – The partition that the resource is in. For standard AWS regions, the partition is aws. If you have resources in other partitions, the partition is aws-partitionname. For example, the partition for resources in the China (Beijing) region is aws-cn. Default: The AWS partition the stack is deployed to.
region (Optional[str]) – The region the resource resides in. Note that the ARNs for some resources do not require a region, so this component might be omitted. Default: The region the stack is deployed to.
resource_name (Optional[str]) – Resource name or path within the resource (i.e. S3 bucket object key) or a wildcard such as "*". This is service-dependent.

Return type:

str

get_logical_id(element)

Allocates a stack-unique CloudFormation-compatible logical identity for a specific resource.

This method is called when a CfnElement is created and used to render the initial logical identity of resources. Logical ID renames are applied at this stage.

This method uses the protected method allocateLogicalId to render the logical ID for an element. To modify the naming scheme, extend the Stack class and override this method.

Parameters:: element (CfnElement) – The CloudFormation element for which a logical identity is needed.
Return type:: str

regional_fact(fact_name, default_value=None)

Look up a fact value for the given fact for the region of this stack.

Will return a definite value only if the region of the current stack is resolved. If not, a lookup map will be added to the stack and the lookup will be done at CDK deployment time.

What regions will be included in the lookup map is controlled by the @aws-cdk/core:target-partitions context value: it must be set to a list of partitions, and only regions from the given partitions will be included. If no such context key is set, all regions will be included.

This function is intended to be used by construct library authors. Application builders can rely on the abstractions offered by construct libraries and do not have to worry about regional facts.

If defaultValue is not given, it is an error if the fact is unknown for the given region.

Parameters:

fact_name (str)
default_value (Optional[str])

Return type:

str

remove_stack_tag(tag_name)

Remove a stack tag.

At deploy time, CloudFormation will automatically apply all stack tags to all resources in the stack.

Parameters:: tag_name (str)
Return type:: None

rename_logical_id(old_id, new_id)

Rename a generated logical identities.

To modify the naming scheme strategy, extend the Stack class and override the allocateLogicalId method.

Parameters:

old_id (str)
new_id (str)

Return type:

None

report_missing_context_key(*, key, props, provider)

Indicate that a context key was expected.

Contains instructions which will be emitted into the cloud assembly on how the key should be supplied.

Parameters:

key (str) – The missing context key.
props (Union[AmiContextQuery, Dict[str, Any], AvailabilityZonesContextQuery, HostedZoneContextQuery, SSMParameterContextQuery, VpcContextQuery, EndpointServiceAvailabilityZonesContextQuery, LoadBalancerContextQuery, LoadBalancerListenerContextQuery, SecurityGroupContextQuery, KeyContextQuery, CcApiContextQuery, PluginContextQuery]) – A set of provider-specific options.
provider (ContextProvider) – The provider from which we expect this context key to be obtained.

Return type:

None

resolve(obj)

Resolve a tokenized value in the context of the current stack.

Parameters:: obj (Any)
Return type:: Any

split_arn(arn, arn_format)

Splits the provided ARN into its components.

Works both if ‘arn’ is a string like ‘arn:aws:s3:::bucket’, and a Token representing a dynamic CloudFormation expression (in which case the returned components will also be dynamic CloudFormation expressions, encoded as Tokens).

Parameters:

arn (str) – the ARN to split into its components.
arn_format (ArnFormat) – the expected format of ‘arn’ - depends on what format the service ‘arn’ represents uses.

Return type:

ArnComponents

to_json_string(obj, space=None)

Convert an object, potentially containing tokens, to a JSON string.

Parameters:

obj (Any)
space (Union[int, float, None])

Return type:

str

to_string()

Returns a string representation of this construct.

Return type:: str

to_yaml_string(obj)

Convert an object, potentially containing tokens, to a YAML string.

Parameters:: obj (Any)
Return type:: str

Attributes

account

The AWS account into which this stack will be deployed.

This value is resolved according to the following rules:

The value provided to env.account when the stack is defined. This can either be a concrete account (e.g. 585695031111) or the Aws.ACCOUNT_ID token.
Aws.ACCOUNT_ID, which represents the CloudFormation intrinsic reference { "Ref": "AWS::AccountId" } encoded as a string token.

Preferably, you should use the return value as an opaque string and not attempt to parse it to implement your logic. If you do, you must first check that it is a concrete value an not an unresolved token. If this value is an unresolved token (Token.isUnresolved(stack.account) returns true), this implies that the user wishes that this stack will synthesize into an account-agnostic template. In this case, your code should either fail (throw an error, emit a synth error using Annotations.of(construct).addError()) or implement some other account-agnostic behavior.

artifact_id: The ID of the cloud assembly artifact for this stack.

assertions

(experimental) Make assertions on resources in this test case.

Stability:: experimental

availability_zones

Returns the list of AZs that are available in the AWS environment (account/region) associated with this stack.

If the stack is environment-agnostic (either account and/or region are tokens), this property will return an array with 2 tokens that will resolve at deploy-time to the first two availability zones returned from CloudFormation’s Fn::GetAZs intrinsic function.

If they are not available in the context, returns a set of dummy values and reports them as missing, and let the CLI resolve them by calling EC2 DescribeAvailabilityZones on the target environment.

To specify a different strategy for selecting availability zones override this method.

bundling_required: Indicates whether the stack requires bundling or not.

dependencies: Return the stacks this stack depends on.

environment

The environment coordinates in which this stack is deployed.

In the form aws://account/region. Use stack.account and stack.region to obtain the specific values, no need to parse.

You can use this value to determine if two stacks are targeting the same environment.

If either stack.account or stack.region are not concrete values (e.g. Aws.ACCOUNT_ID or Aws.REGION) the special strings unknown-account and/or unknown-region will be used respectively to indicate this stack is region/account-agnostic.

nested: Indicates if this is a nested stack, in which case parentStack will include a reference to it’s parent.

nested_stack_parent: If this is a nested stack, returns it’s parent stack.

nested_stack_resource

If this is a nested stack, this represents its AWS::CloudFormation::Stack resource.

undefined for top-level (non-nested) stacks.

node: The tree node.

notification_arns: Returns the list of notification Amazon Resource Names (ARNs) for the current stack.

partition: The partition in which this stack is defined.

region

The AWS region into which this stack will be deployed (e.g. us-west-2).

This value is resolved according to the following rules:

The value provided to env.region when the stack is defined. This can either be a concrete region (e.g. us-west-2) or the Aws.REGION token.
Aws.REGION, which is represents the CloudFormation intrinsic reference { "Ref": "AWS::Region" } encoded as a string token.

Preferably, you should use the return value as an opaque string and not attempt to parse it to implement your logic. If you do, you must first check that it is a concrete value an not an unresolved token. If this value is an unresolved token (Token.isUnresolved(stack.region) returns true), this implies that the user wishes that this stack will synthesize into a region-agnostic template. In this case, your code should either fail (throw an error, emit a synth error using Annotations.of(construct).addError()) or implement some other region-agnostic behavior.

stack_id

The ID of the stack.

Example:

# After resolving, looks like
"arn:aws:cloudformation:us-west-2:123456789012:stack/teststack/51af3dc0-da77-11e4-872e-1234567db123"

stack_name

The concrete CloudFormation physical stack name.

This is either the name defined explicitly in the stackName prop or allocated based on the stack’s location in the construct tree. Stacks that are directly defined under the app use their construct id as their stack name. Stacks that are defined deeper within the tree will use a hashed naming scheme based on the construct path to ensure uniqueness.

If you wish to obtain the deploy-time AWS::StackName intrinsic, you can use Aws.STACK_NAME directly.

synthesizer: Synthesis method for this stack.

tags: Tags to be applied to the stack.

template_file

The name of the CloudFormation template file emitted to the output directory during synthesis.

Example value: MyStack.template.json

template_options: Options for CloudFormation template (like version, transform, description).

termination_protection: Whether termination protection is enabled for this stack.

url_suffix: The Amazon domain suffix for the region in which this stack is defined.

Static Methods

classmethod is_construct(x)

Checks if x is a construct.

Use this method instead of instanceof to properly detect Construct instances, even when the construct library is symlinked.

Explanation: in JavaScript, multiple copies of the constructs library on disk are seen as independent, completely different libraries. As a consequence, the class Construct in each copy of the constructs library is seen as a different class, and an instance of one class will not test as instanceof the other class. npm install will not create installations like this, but users may manually symlink construct libraries together or use a monorepo tool: in those cases, multiple copies of the constructs library can be accidentally installed, and instanceof will behave unpredictably. It is safest to avoid using instanceof, and using this type-testing method instead.

Parameters:: x (Any) – Any object.
Return type:: bool
Returns:: true if x is an object created from a class which extends Construct.

classmethod is_integ_test_case_stack(x)

(experimental) Returns whether the construct is a IntegTestCaseStack.

Parameters:: x (Any)
Stability:: experimental
Return type:: bool

classmethod is_stack(x)

Return whether the given object is a Stack.

We do attribute detection since we can’t reliably use ‘instanceof’.

Parameters:: x (Any)
Return type:: bool

classmethod of(construct)

Looks up the first stack scope in which construct is defined.

Fails if there is no stack up the tree.

Parameters:: construct (IConstruct) – The construct to start the search from.
Return type:: Stack