Merge branch 'main' into dependabot/npm_and_yarn/tools/linters/smol-toml-1.6.1

Author: kaizencc

ACCEPTED.md

@@ -13,7 +13,6 @@
 [673](https://github.com/aws/aws-cdk-rfcs/issues/673)|[AWS CloudWatch Application Signals L2 Constructs for SLO](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0673-aws-applicationsignals-slo-l2.md)||👷 implementing
 [789](https://github.com/aws/aws-cdk-rfcs/issues/789)|[EC2 Image Builder L2 Constructs](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0789-bedrock-agentcore-gateway-l2.md)||👷 implementing
 [792](https://github.com/aws/aws-cdk-rfcs/issues/792)|[L2 Construct for AIOps](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0792-aws-aiops-investigationgroup-l2.md)||👷 implementing
-[814](https://github.com/aws/aws-cdk-rfcs/issues/814)|[Unified mechanism for abstractions that change constructs after construction](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0814-cdk-mixins.md)||👷 implementing
 [1](https://github.com/aws/aws-cdk-rfcs/issues/1)|[CDK Watch](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0001-cdk-update.md)||✅ done
 [4](https://github.com/aws/aws-cdk-rfcs/issues/4)|[CDK Testing Toolkit](https://github.com/aws/aws-cdk-rfcs/issues/4)|[@nija-at](https://github.com/nija-at)|✅ done
 [5](https://github.com/aws/aws-cdk-rfcs/issues/5)|[Security-restricted environments](https://github.com/aws/aws-cdk-rfcs/issues/5)||✅ done
@@ -81,4 +80,5 @@
 [745](https://github.com/aws/aws-cdk-rfcs/issues/745)|[User-Provided cdk init Templates](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0745-user-provided-cdk-init-templates.md)||✅ done
 [750](https://github.com/aws/aws-cdk-rfcs/issues/750)|[Feature Flag Advisor](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0750-feature-flag-advisor.md)||✅ done
 [808](https://github.com/aws/aws-cdk-rfcs/issues/808)|[Library Quality Scoring](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0808-library-quality-scoring.md)||✅ done
+[814](https://github.com/aws/aws-cdk-rfcs/issues/814)|[Unified mechanism for abstractions that change constructs after construction](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0814-cdk-mixins.md)||✅ done
 <!--END_TABLE-->

FULL_INDEX.md

@@ -203,9 +203,12 @@
 [789](https://github.com/aws/aws-cdk-rfcs/issues/789)|[EC2 Image Builder L2 Constructs](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0789-bedrock-agentcore-gateway-l2.md)||👷 implementing
 [792](https://github.com/aws/aws-cdk-rfcs/issues/792)|[L2 Construct for AIOps](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0792-aws-aiops-investigationgroup-l2.md)||👷 implementing
 [808](https://github.com/aws/aws-cdk-rfcs/issues/808)|[Library Quality Scoring](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0808-library-quality-scoring.md)||✅ done
-[814](https://github.com/aws/aws-cdk-rfcs/issues/814)|[Unified mechanism for abstractions that change constructs after construction](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0814-cdk-mixins.md)||👷 implementing
+[814](https://github.com/aws/aws-cdk-rfcs/issues/814)|[Unified mechanism for abstractions that change constructs after construction](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0814-cdk-mixins.md)||✅ done
 [835](https://github.com/aws/aws-cdk-rfcs/issues/835)|[Native EBS Snapshot Asset Handling](https://github.com/aws/aws-cdk-rfcs/issues/835)||💡 proposed
 [859](https://github.com/aws/aws-cdk-rfcs/issues/859)|[L2 Construct for AWS::ObservabilityAdmin::OrganizationCentralizationRule](https://github.com/aws/aws-cdk-rfcs/issues/859)||💡 proposed
 [867](https://github.com/aws/aws-cdk-rfcs/issues/867)|[S3 Vector L2 CDK Constructs](https://github.com/aws/aws-cdk-rfcs/issues/867)||💡 proposed
 [877](https://github.com/aws/aws-cdk-rfcs/issues/877)|[Automated issue triage and guidance for community PRs](https://github.com/aws/aws-cdk-rfcs/issues/877)||💡 proposed
+[884](https://github.com/aws/aws-cdk-rfcs/issues/884)|[L2 Constructs for AWS Elemental MediaConnect](https://github.com/aws/aws-cdk-rfcs/issues/884)||💡 proposed
+[886](https://github.com/aws/aws-cdk-rfcs/issues/886)|[Making Hotswap Faster](https://github.com/aws/aws-cdk-rfcs/issues/886)||💡 proposed
+[897](https://github.com/aws/aws-cdk-rfcs/issues/897)|[CDK Comprehensive Validation](https://github.com/aws/aws-cdk-rfcs/issues/897)||💡 proposed
 <!--END_TABLE-->

PROPOSED.md

@@ -35,4 +35,7 @@
 [859](https://github.com/aws/aws-cdk-rfcs/issues/859)|[L2 Construct for AWS::ObservabilityAdmin::OrganizationCentralizationRule](https://github.com/aws/aws-cdk-rfcs/issues/859)||💡 proposed
 [867](https://github.com/aws/aws-cdk-rfcs/issues/867)|[S3 Vector L2 CDK Constructs](https://github.com/aws/aws-cdk-rfcs/issues/867)||💡 proposed
 [877](https://github.com/aws/aws-cdk-rfcs/issues/877)|[Automated issue triage and guidance for community PRs](https://github.com/aws/aws-cdk-rfcs/issues/877)||💡 proposed
+[884](https://github.com/aws/aws-cdk-rfcs/issues/884)|[L2 Constructs for AWS Elemental MediaConnect](https://github.com/aws/aws-cdk-rfcs/issues/884)||💡 proposed
+[886](https://github.com/aws/aws-cdk-rfcs/issues/886)|[Making Hotswap Faster](https://github.com/aws/aws-cdk-rfcs/issues/886)||💡 proposed
+[897](https://github.com/aws/aws-cdk-rfcs/issues/897)|[CDK Comprehensive Validation](https://github.com/aws/aws-cdk-rfcs/issues/897)||💡 proposed
 <!--END_TABLE-->

README.md

@@ -26,7 +26,6 @@ future state of the libraries and to discover projects for contribution.
 [673](https://github.com/aws/aws-cdk-rfcs/issues/673)|[AWS CloudWatch Application Signals L2 Constructs for SLO](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0673-aws-applicationsignals-slo-l2.md)||👷 implementing
 [789](https://github.com/aws/aws-cdk-rfcs/issues/789)|[EC2 Image Builder L2 Constructs](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0789-bedrock-agentcore-gateway-l2.md)||👷 implementing
 [792](https://github.com/aws/aws-cdk-rfcs/issues/792)|[L2 Construct for AIOps](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0792-aws-aiops-investigationgroup-l2.md)||👷 implementing
-[814](https://github.com/aws/aws-cdk-rfcs/issues/814)|[Unified mechanism for abstractions that change constructs after construction](https://github.com/aws/aws-cdk-rfcs/blob/main/text/0814-cdk-mixins.md)||👷 implementing
 <!--END_TABLE-->
 
 ## What is an RFC?

text/0300-programmatic-toolkit.md

@@ -355,7 +355,8 @@ RFC pull request):
 
 ### What are we launching today?
 
-We are launching the [Programmatic Toolkit], a new TypeScript package that enables integrators to build custom lifecycle management solutions for CDK applications.
+We are launching the [Programmatic Toolkit], a new TypeScript package that enables integrators to build custom lifecycle management
+solutions for CDK applications.
 The toolkit provides implementation for all of the CDK's actions like bootstrap, synth or deploy.
 It gives integrators full control over all output and allows to interweave actions with custom steps.
 
@@ -648,7 +649,8 @@ interface RecoverableError<T, U> extends IoRequest<T, U> {
 }
 ```
 
-When `IoHost.requestResponse()` is called with a recoverable error, the integrator may choose to return `retry: true` to indicate the block should be retried.
+When `IoHost.requestResponse()` is called with a recoverable error, the integrator may choose to return `retry: true` to indicate
+the block should be retried.
 A single retry is allowed, if the block fails again with the same error it will be raised as an exception.
 Retries are not guaranteed and integrators must handle the case where a requested retry is not executed.
 Recoverable errors are rare as they require special programming and not always possible.

text/0474-event-bridge-scheduler-l2.md

@@ -48,7 +48,8 @@ See below
 # Amazon EventBridge Scheduler Contruct Library
 
 [Amazon EventBridge Scheduler](https://aws.amazon.com/blogs/compute/introducing-amazon-eventbridge-scheduler/) is a feature from Amazon EventBridge that
-allows you to create, run, and manage scheduled tasks at scale. With EventBridge Scheduler, you can schedule one-time or recurrently tens of millions of
+allows you to create, run, and manage scheduled tasks at scale. With EventBridge Scheduler, you can schedule one-time or recurrently tens of millions
+of
 tasks across many AWS services without provisioning or managing underlying infrastructure.
 
 1. **Schedule**: A schedule is the main resource you create, configure, and manage using Amazon EventBridge Scheduler.

text/0502_aws-vpclattice.md

@@ -750,7 +750,10 @@ export abstract class Target {
    * @param alb
    * @param config
    */
-  public static applicationLoadBalancer(alb: elbv2.ApplicationListener[], config: aws_vpclattice.CfnTargetGroup.TargetGroupConfigProperty): Target {  }
+  public static applicationLoadBalancer(
+    alb: elbv2.ApplicationListener[],
+    config: aws_vpclattice.CfnTargetGroup.TargetGroupConfigProperty,
+  ): Target {  }
 
 ```
 

text/0648-aspects-priority-ordering.md

@@ -18,7 +18,8 @@ Conceptually, there are two types of Aspects:
 * **Read-only aspects** scan the construct tree but do not make changes to the tree. Common use cases of read-only aspects include performing validations
 (for example, enforcing that all S3 Buckets have versioning enabled) and logging (for example, collecting information about all deployed resources for
 audits or compliance).
-* **Mutating aspects** either (1.) add new nodes or (2.) mutate existing nodes of the tree in-place. One commonly used mutating Aspect is adding Tags to
+* **Mutating aspects** either (1.) add new nodes or (2.) mutate existing nodes of the tree in-place. One commonly used mutating Aspect is adding
+Tags to
 resources. An example of an Aspect that adds a node is one that automatically adds a security group to every EC2 instance in the construct tree if
 no default is specified.
 
@@ -362,10 +363,10 @@ The behavior we want to guarantee in this algorithm is:
 Additionally, we will remove a constraint from the existing algorithm which prevent nested Aspects from being invoked. The current algorithm emits a warning
 if an Aspect creates another Aspect and does not invoke that new Aspect.
 
-The feature introduces an optional priority parameter when aspects are apdded. Aspects are then invoked on the construct tree in order of increasing priority
-values. This ensures that mutating aspects are applied first and validation aspects follow, if the application author specifies so. Additionally, the algorithm
-ensures that newly created nodes inherit aspects from their parent constructs, even if those nodes are added later in the process. See Appendix for
-Pseudocode for the new `invokeAspects` function.
+The feature introduces an optional priority parameter when aspects are added. Aspects are then invoked on the construct tree in order of
+increasing priority values. This ensures that mutating aspects are applied first and validation aspects follow, if the application author
+specifies so. Additionally, the algorithm ensures that newly created nodes inherit aspects from their parent constructs, even if those nodes
+are added later in the process. See Appendix for Pseudocode for the new `invokeAspects` function.
 
 Our new `invokeAspects` function will use a stabilization loop to recurse the construct tree and invoke Aspects. The stabilization loop is necessary in
 order to ensure that new nodes created by Aspects (as well as new Aspects created by Aspects) get visited.

text/0786-bedrock-agentcore-tools-l2.md

@@ -121,10 +121,10 @@ const browser = new agentcore.BrowserCustom(this, 'BrowserVpcWithRecording', {
 });
 ```
 
-Browser exposes a [connections](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.Connections.html) property. This property returns a connections
-object, which simplifies the process of defining and managing ingress and egress rules for security groups in your AWS CDK applications. Instead of directly
-manipulating security group rules, you interact with the Connections object of a construct, which then translates your connectivity requirements into the
-appropriate security group rules. For instance:
+Browser exposes a [connections](https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.Connections.html) property. This property
+returns a connections object, which simplifies the process of defining and managing ingress and egress rules for security groups in your
+AWS CDK applications. Instead of directly manipulating security group rules, you interact with the Connections object of a construct, which
+then translates your connectivity requirements into the appropriate security group rules. For instance:
 
 ```typescript fixture=default
 const vpc = new ec2.Vpc(this, 'testVPC');

text/0792-aws-aiops-investigationgroup-l2.md

@@ -332,7 +332,8 @@ It eliminates the complexity of manually configuring IAM roles, KMS encryption,
 
 ### Why are we doing this?
 
-The development of AIOps L2 constructs addresses significant customer needs and adoption patterns. Currently, customers rely on L1 constructs through CloudFormation,
+The development of AIOps L2 constructs addresses significant customer needs and adoption patterns. Currently, customers rely on L1 constructs through
+CloudFormation,
 requiring detailed understanding of resource configurations. Additionally, multiple Amazon internal teams have successfully adopted an internal
 L2 package for AIOps resource management, demonstrating the value and demand for higher-level abstractions.