Skip to content

Conversation

@aws-cdk-automation
Copy link
Contributor

@aws-cdk-automation aws-cdk-automation commented Nov 27, 2025

⚠️ 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

@github-actions
Copy link
Contributor

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 2251
git switch -c fix-pr-2251 && git push -u origin HEAD
gh pr create -t "fix: PR #2251" --body "Fixes https://github.com/cdklabs/awscdk-service-spec/pull/2251"

@github-actions
Copy link
Contributor

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

├[~] service aws-ecr
│ └ resources
│    └[~]  resource AWS::ECR::SigningConfiguration
│       ├ properties
│       │  └ Rules: (documentation changed)
│       ├ attributes
│       │  └ RegistryId: (documentation changed)
│       └ types
│          ├[~] type RepositoryFilter
│          │ ├      - documentation: The filter settings used with image replication. Specifying a repository filter to a replication rule provides a method for controlling which repositories in a private registry are replicated. If no filters are added, the contents of all repositories are replicated.
│          │ │      + documentation: A repository filter used to determine which repositories have their images automatically signed on push. Each filter consists of a filter type and filter value.
│          │ └ properties
│          │    ├ Filter: (documentation changed)
│          │    └ FilterType: (documentation changed)
│          └[~] type Rule
│            ├      - documentation: undefined
│            │      + documentation: A signing rule that specifies a signing profile and optional repository filters. When an image is pushed to a matching repository, a signing job is created using the specified profile.
│            └ properties
│               ├ RepositoryFilters: (documentation changed)
│               └ SigningProfileArn: (documentation changed)
├[~] service aws-s3
│ └ resources
│    ├[~]  resource AWS::S3::AccessPoint
│    │  └ types
│    │     └[~] type PublicAccessBlockConfiguration
│    │       └      - documentation: The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can enable the configuration options in any combination. For more information about when Amazon S3 considers a bucket or object public, see [The Meaning of "Public"](https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status) in the *Amazon S3 User Guide* .
│    │              + documentation: The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can enable the configuration options in any combination. Bucket-level settings work alongside account-level settings (which may inherit from organization-level policies). For more information about when Amazon S3 considers a bucket or object public, see [The Meaning of "Public"](https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status) in the *Amazon S3 User Guide* .
│    └[~]  resource AWS::S3::Bucket
│       └ types
│          └[~] type PublicAccessBlockConfiguration
│            └      - documentation: The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can enable the configuration options in any combination. For more information about when Amazon S3 considers a bucket or object public, see [The Meaning of "Public"](https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status) in the *Amazon S3 User Guide* .
│                   + documentation: The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can enable the configuration options in any combination. Bucket-level settings work alongside account-level settings (which may inherit from organization-level policies). For more information about when Amazon S3 considers a bucket or object public, see [The Meaning of "Public"](https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status) in the *Amazon S3 User Guide* .
└[~] service aws-sagemaker
  └ resources
     └[~]  resource AWS::SageMaker::Cluster
        └ types
           ├[~] type ClusterCapacityRequirements
           │ ├      - documentation: Specifies the capacity requirements configuration for an instance group
           │ │      + documentation: Defines the instance capacity requirements for an instance group, including configurations for both Spot and On-Demand capacity types.
           │ └ properties
           │    ├ OnDemand: (documentation changed)
           │    └ Spot: (documentation changed)
           ├[~] type ClusterKubernetesConfig
           │ ├      - documentation: Kubernetes configuration for cluster nodes including labels and taints.
           │ │      + documentation: Kubernetes configuration that specifies labels and taints to be applied to cluster nodes in an instance group.
           │ └ properties
           │    ├ Labels: (documentation changed)
           │    └ Taints: (documentation changed)
           └[~] type ClusterKubernetesTaint
             ├      - documentation: A Kubernetes taint to apply to cluster nodes.
             │      + documentation: A Kubernetes taint that can be applied to cluster nodes.
             └ properties
                └ Effect: (documentation changed)

> ⚠️ 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/19753300002

------

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

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@aws-cdk-automation aws-cdk-automation force-pushed the update-source/documentation branch from 936be15 to ce00b94 Compare November 28, 2025 03:34
@github-actions
Copy link
Contributor

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 2251
git switch -c fix-pr-2251 && git push -u origin HEAD
gh pr create -t "fix: PR #2251" --body "Fixes https://github.com/cdklabs/awscdk-service-spec/pull/2251"

@github-actions
Copy link
Contributor

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

├[~] service aws-ecr
│ └ resources
│    └[~]  resource AWS::ECR::SigningConfiguration
│       ├ properties
│       │  └ Rules: (documentation changed)
│       ├ attributes
│       │  └ RegistryId: (documentation changed)
│       └ types
│          ├[~] type RepositoryFilter
│          │ ├      - documentation: The filter settings used with image replication. Specifying a repository filter to a replication rule provides a method for controlling which repositories in a private registry are replicated. If no filters are added, the contents of all repositories are replicated.
│          │ │      + documentation: A repository filter used to determine which repositories have their images automatically signed on push. Each filter consists of a filter type and filter value.
│          │ └ properties
│          │    ├ Filter: (documentation changed)
│          │    └ FilterType: (documentation changed)
│          └[~] type Rule
│            ├      - documentation: undefined
│            │      + documentation: A signing rule that specifies a signing profile and optional repository filters. When an image is pushed to a matching repository, a signing job is created using the specified profile.
│            └ properties
│               ├ RepositoryFilters: (documentation changed)
│               └ SigningProfileArn: (documentation changed)
├[~] service aws-s3
│ └ resources
│    ├[~]  resource AWS::S3::AccessPoint
│    │  └ types
│    │     └[~] type PublicAccessBlockConfiguration
│    │       └      - documentation: The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can enable the configuration options in any combination. For more information about when Amazon S3 considers a bucket or object public, see [The Meaning of "Public"](https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status) in the *Amazon S3 User Guide* .
│    │              + documentation: The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can enable the configuration options in any combination. Bucket-level settings work alongside account-level settings (which may inherit from organization-level policies). For more information about when Amazon S3 considers a bucket or object public, see [The Meaning of "Public"](https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status) in the *Amazon S3 User Guide* .
│    └[~]  resource AWS::S3::Bucket
│       └ types
│          └[~] type PublicAccessBlockConfiguration
│            └      - documentation: The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can enable the configuration options in any combination. For more information about when Amazon S3 considers a bucket or object public, see [The Meaning of "Public"](https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status) in the *Amazon S3 User Guide* .
│                   + documentation: The PublicAccessBlock configuration that you want to apply to this Amazon S3 bucket. You can enable the configuration options in any combination. Bucket-level settings work alongside account-level settings (which may inherit from organization-level policies). For more information about when Amazon S3 considers a bucket or object public, see [The Meaning of "Public"](https://docs.aws.amazon.com/AmazonS3/latest/dev/access-control-block-public-access.html#access-control-block-public-access-policy-status) in the *Amazon S3 User Guide* .
└[~] service aws-sagemaker
  └ resources
     └[~]  resource AWS::SageMaker::Cluster
        └ types
           ├[~] type ClusterCapacityRequirements
           │ ├      - documentation: Specifies the capacity requirements configuration for an instance group
           │ │      + documentation: Defines the instance capacity requirements for an instance group, including configurations for both Spot and On-Demand capacity types.
           │ └ properties
           │    ├ OnDemand: (documentation changed)
           │    └ Spot: (documentation changed)
           ├[~] type ClusterKubernetesConfig
           │ ├      - documentation: Kubernetes configuration for cluster nodes including labels and taints.
           │ │      + documentation: Kubernetes configuration that specifies labels and taints to be applied to cluster nodes in an instance group.
           │ └ properties
           │    ├ Labels: (documentation changed)
           │    └ Taints: (documentation changed)
           └[~] type ClusterKubernetesTaint
             ├      - documentation: A Kubernetes taint to apply to cluster nodes.
             │      + documentation: A Kubernetes taint that can be applied to cluster nodes.
             └ properties
                └ Effect: (documentation changed)

@aws-cdk-automation aws-cdk-automation added this pull request to the merge queue Nov 28, 2025
Merged via the queue into main with commit 3d015d6 Nov 28, 2025
11 checks passed
@aws-cdk-automation aws-cdk-automation deleted the update-source/documentation branch November 28, 2025 03:58
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