Skip to content

feat(sources): update documentation #1959

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 17, 2025

Conversation

aws-cdk-automation
Copy link
Contributor

⚠️ This Pull Request updates daily and will overwrite all manual changes pushed to the branch

Updates the documentation source from upstream. See details in workflow run.


Automatically created by projen via the "update-source-documentation" workflow

> ⚠️ This Pull Request updates daily and will overwrite **all** manual changes pushed to the branch

Updates the documentation source from upstream. See details in [workflow run].

[Workflow Run]: https://github.com/cdklabs/awscdk-service-spec/actions/runs/16335646078

------

*Automatically created by projen via the "update-source-documentation" workflow*

Signed-off-by: github-actions <[email protected]>
Copy link

To work on this Pull Request, please create a new branch and PR. This prevents your work from being deleted by the automation.

Run the following commands inside the repo:

gh co 1959
git switch -c fix-pr-1959 && git push -u origin HEAD
gh pr create -t "fix: PR #1959" --body "Fixes https://github.com/cdklabs/awscdk-service-spec/pull/1959"

Copy link

@aws-cdk/aws-service-spec: Model database diff detected

├[~] service aws-certificatemanager
│ └ resources
│    └[~]  resource AWS::CertificateManager::Certificate
│       └ properties
│          └ KeyAlgorithm: (documentation changed)
├[~] service aws-ec2
│ └ resources
│    └[~]  resource AWS::EC2::InstanceConnectEndpoint
│       └ properties
│          └ PreserveClientIp: (documentation changed)
├[~] service aws-ecs
│ └ resources
│    └[~]  resource AWS::ECS::Service
│       ├ properties
│       │  ├ DeploymentController: (documentation changed)
│       │  └ EnableECSManagedTags: (documentation changed)
│       └ types
│          ├[~] type DeploymentAlarms
│          │ └      - documentation: One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment.
│          │        When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure.
│          │        You can only use the `DeploymentAlarms` method to detect failures when the `DeploymentController` is set to `ECS` (rolling update).
│          │        For more information, see [Rolling update](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html) in the **Amazon Elastic Container Service Developer Guide** .
│          │        + documentation: One of the methods which provide a way for you to quickly identify when a deployment has failed, and then to optionally roll back the failure to the last working deployment.
│          │        When the alarms are generated, Amazon ECS sets the service deployment to failed. Set the rollback parameter to have Amazon ECS to roll back your service to the last completed deployment after a failure.
│          │        You can only use the `DeploymentAlarms` method to detect failures when the `DeploymentController` is set to `ECS` .
│          │        For more information, see [Rolling update](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-type-ecs.html) in the **Amazon Elastic Container Service Developer Guide** .
│          └[~] type DeploymentController
│            └ properties
│               └ Type: (documentation changed)
└[~] service aws-s3
  └ resources
     └[~]  resource AWS::S3::Bucket
        ├ properties
        │  └ InventoryConfigurations: (documentation changed)
        └ types
           ├[~] type InventoryConfiguration
           │ └      - documentation: Specifies the inventory configuration for an Amazon S3 bucket. For more information, see [GET Bucket inventory](https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGETInventoryConfig.html) in the *Amazon S3 API Reference* .
           │        + documentation: Specifies the S3 Inventory configuration for an Amazon S3 bucket. For more information, see [GET Bucket inventory](https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketGETInventoryConfig.html) in the *Amazon S3 API Reference* .
           └[~] type S3TablesDestination
             └      - documentation: The destination information for the metadata table configuration. The destination table bucket must be in the same Region and AWS account as the general purpose bucket. The specified metadata table name must be unique within the `aws_s3_metadata` namespace in the destination table bucket.
                    + documentation: The destination information for a V1 S3 Metadata configuration. The destination table bucket must be in the same Region and AWS account as the general purpose bucket. The specified metadata table name must be unique within the `aws_s3_metadata` namespace in the destination table bucket.
                    > If you created your S3 Metadata configuration before July 15, 2025, we recommend that you delete and re-create your configuration by using [CreateBucketMetadataConfiguration](https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucketMetadataConfiguration.html) so that you can expire journal table records and create a live inventory table.

@aws-cdk-automation aws-cdk-automation added this pull request to the merge queue Jul 17, 2025
Merged via the queue into main with commit 10ac334 Jul 17, 2025
11 checks passed
@aws-cdk-automation aws-cdk-automation deleted the update-source/documentation branch July 17, 2025 04:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant