Merge branch 'main' into flink_1_19

aws · Jul 31, 2024 · 39ca1ae · 39ca1ae
2 parents 9d1eb64 + ad3a25d
commit 39ca1ae
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 4 deletions.
diff --git a/packages/@aws-cdk/aws-apprunner-alpha/lib/service.ts b/packages/@aws-cdk/aws-apprunner-alpha/lib/service.ts
@@ -202,6 +202,11 @@ export class Runtime {
    */
   public static readonly NODEJS_16 = Runtime.of('NODEJS_16')
 
+  /**
+   * NodeJS 18
+   */
+  public static readonly NODEJS_18 = Runtime.of('NODEJS_18')
+
   /**
    * PHP 8.1
    */
@@ -212,6 +217,11 @@ export class Runtime {
    */
   public static readonly PYTHON_3 = Runtime.of('PYTHON_3')
 
+  /**
+   * Python 3.11
+   */
+  public static readonly PYTHON_311 = Runtime.of('PYTHON_311')
+
   /**
    * Ruby 3.1
    */

diff --git a/packages/aws-cdk-lib/core/lib/stack.ts b/packages/aws-cdk-lib/core/lib/stack.ts
@@ -1171,8 +1171,6 @@ export class Stack extends Construct implements ITaggable {
    * remove the reference from the consuming stack. After that, you can remove
    * the resource and the manual export.
    *
-   * ## Example
-   *
    * 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
@@ -1183,7 +1181,7 @@ export class Stack extends Construct implements ITaggable {
    *
    * Instead, the process takes two deployments:
    *
-   * ### Deployment 1: break the relationship
+   * **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
@@ -1193,7 +1191,7 @@ export class Stack extends Construct implements ITaggable {
    *   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
+   * **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.