Skip to content

Commit e881cd7

Browse files
committed
update FEATURE_FLAGS.md
1 parent cf92ddd commit e881cd7

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

packages/aws-cdk-lib/cx-api/FEATURE_FLAGS.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Flags come in three types:
3838
| [@aws-cdk/core:enablePartitionLiterals](#aws-cdkcoreenablepartitionliterals) | Make ARNs concrete if AWS partition is known | 2.38.0 | fix |
3939
| [@aws-cdk/aws-ecs:disableExplicitDeploymentControllerForCircuitBreaker](#aws-cdkaws-ecsdisableexplicitdeploymentcontrollerforcircuitbreaker) | Avoid setting the "ECS" deployment controller when adding a circuit breaker | 2.51.0 | fix |
4040
| [@aws-cdk/aws-events:eventsTargetQueueSameAccount](#aws-cdkaws-eventseventstargetqueuesameaccount) | Event Rules may only push to encrypted SQS queues in the same account | 2.51.0 | fix |
41-
| [@aws-cdk/aws-iam:importedRoleStackSafeDefaultPolicyName](#aws-cdkaws-iamimportedrolestacksafedefaultpolicyname) | Enable this feature to by default create default policy names for imported roles that depend on the stack the role is in. | 2.60.0 | fix |
41+
| [@aws-cdk/aws-iam:importedRoleStackSafeDefaultPolicyName](#aws-cdkaws-iamimportedrolestacksafedefaultpolicyname) | Enable this feature to create default policy names for imported roles that depend on the stack the role is in. | 2.60.0 | fix |
4242
| [@aws-cdk/aws-s3:serverAccessLogsUseBucketPolicy](#aws-cdkaws-s3serveraccesslogsusebucketpolicy) | Use S3 Bucket Policy instead of ACLs for Server Access Logging | 2.60.0 | fix |
4343
| [@aws-cdk/customresources:installLatestAwsSdkDefault](#aws-cdkcustomresourcesinstalllatestawssdkdefault) | Whether to install the latest SDK by default in AwsCustomResource | 2.60.0 | new default |
4444
| [@aws-cdk/aws-route53-patters:useCertificate](#aws-cdkaws-route53-pattersusecertificate) | Use the official `Certificate` resource instead of `DnsValidatedCertificate` | 2.61.0 | new default |
@@ -877,7 +877,7 @@ always apply, regardless of the value of this flag.
877877

878878
### @aws-cdk/aws-iam:importedRoleStackSafeDefaultPolicyName
879879

880-
*Enable this feature to by default create default policy names for imported roles that depend on the stack the role is in.*
880+
*Enable this feature to create default policy names for imported roles that depend on the stack the role is in.*
881881

882882
Flag type: Backwards incompatible bugfix
883883

@@ -900,7 +900,7 @@ This new implementation creates default policy names based on the constructs nod
900900

901901
Flag type: Backwards incompatible bugfix
902902

903-
Enable this feature flag to use S3 Bucket Policy for granting permission fo Server Access Logging
903+
Enable this feature flag to use S3 Bucket Policy for granting permission for Server Access Logging
904904
rather than using the canned `LogDeliveryWrite` ACL. ACLs do not work when Object Ownership is
905905
enabled on the bucket.
906906

@@ -1280,7 +1280,7 @@ Set this flag to false for existing mount targets.
12801280
Flag type: New default behavior
12811281

12821282
If this is set, and a `runtime` prop is not passed to, Lambda NodeJs
1283-
functions will us the latest version of the runtime provided by the Lambda
1283+
functions will use the latest version of the runtime provided by the Lambda
12841284
service. Do not use this if you your lambda function is reliant on dependencies
12851285
shipped as part of the runtime environment.
12861286

@@ -1502,7 +1502,7 @@ When this feature flag is disabled, it will keep the root account principal in t
15021502

15031503
Flag type: New default behavior
15041504

1505-
When this featuer flag is enabled, remove the default deployment alarm settings when creating a AWS ECS service.
1505+
When this feature flag is enabled, remove the default deployment alarm settings when creating a AWS ECS service.
15061506

15071507

15081508
| Since | Unset behaves like | Recommended value |
@@ -1753,8 +1753,8 @@ the latest Amazon Linux 2023 version will be used instead of Amazon Linux 2.
17531753

17541754
Flag type: Configuration option
17551755

1756-
Currently, when Aspects are invoked in one single pass of the construct tree.
1757-
This means that the Aspects that create other Aspects are not run and Aspects that create new nodes of the tree sometimes do not inherit their parent Aspects.
1756+
Previously, Aspects were invoked in a single pass of the construct tree.
1757+
This meant that Aspects which created other Aspects were not run, and Aspects that created new nodes in the tree sometimes did not inherit their parent Aspects.
17581758

17591759
When this feature flag is enabled, a stabilization loop is run to recurse the construct tree multiple times when invoking Aspects.
17601760

@@ -1993,7 +1993,7 @@ When enabled, table replica will be default to the removal policy of source tabl
19931993

19941994
Flag type: New default behavior
19951995

1996-
When this feature flag is enabled, the SDK API call response to desribe user pool client values will be logged in the custom
1996+
When this feature flag is enabled, the SDK API call response to describe user pool client values will be logged in the custom
19971997
resource lambda function logs.
19981998

19991999
When this feature flag is disabled, the SDK API call response to describe user pool client values will not be logged in the custom
@@ -2172,7 +2172,7 @@ When this feature flag is disabled, a loggroup is created by Lambda service on f
21722172
of the function (existing behavior).
21732173
LogGroups created in this way do not support Tag propagation, Property Injectors, Aspects.
21742174

2175-
DO NOT ENABLE: If you have and existing app defining a lambda function and
2175+
DO NOT ENABLE: If you have an existing app defining a lambda function and
21762176
have not supplied a logGroup or logRetention prop and your lambda function has
21772177
executed at least once, the logGroup has been already created with the same name
21782178
so your deployment will start failing.

0 commit comments

Comments
 (0)