Skip to content
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

feat: update L1 CloudFormation resource definitions #32272

Merged
merged 1 commit into from
Nov 25, 2024

Conversation

aws-cdk-automation
Copy link
Collaborator

Updates the L1 CloudFormation resource definitions with the latest changes from @aws-cdk/aws-service-spec

L1 CloudFormation resource definition changes:

├[~] service aws-autoscaling
│ └ resources
│    └[~] resource AWS::AutoScaling::AutoScalingGroup
│      ├ properties
│      │  └ CapacityReservationSpecification: (documentation changed)
│      └ types
│         ├[~] type BaselinePerformanceFactorsRequest
│         │ ├  - documentation: undefined
│         │ │  + documentation: The baseline performance to consider, using an instance family as a baseline reference. The instance family establishes the lowest acceptable level of performance. Auto Scaling uses this baseline to guide instance type selection, but there is no guarantee that the selected instance types will always exceed the baseline for every application.
│         │ │  Currently, this parameter only supports CPU performance as a baseline performance factor. For example, specifying `c6i` uses the CPU performance of the `c6i` family as the baseline reference.
│         │ └ properties
│         │    └ Cpu: (documentation changed)
│         ├[~] type CapacityReservationSpecification
│         │ ├  - documentation: undefined
│         │ │  + documentation: Describes the Capacity Reservation preference and targeting options. If you specify `open` or `none` for `CapacityReservationPreference` , do not specify a `CapacityReservationTarget` .
│         │ └ properties
│         │    ├ CapacityReservationPreference: (documentation changed)
│         │    └ CapacityReservationTarget: (documentation changed)
│         ├[~] type CapacityReservationTarget
│         │ ├  - documentation: undefined
│         │ │  + documentation: The target for the Capacity Reservation. Specify Capacity Reservations IDs or Capacity Reservation resource group ARNs.
│         │ └ properties
│         │    ├ CapacityReservationIds: (documentation changed)
│         │    └ CapacityReservationResourceGroupArns: (documentation changed)
│         ├[~] type CpuPerformanceFactorRequest
│         │ ├  - documentation: undefined
│         │ │  + documentation: The CPU performance to consider, using an instance family as the baseline reference.
│         │ └ properties
│         │    └ References: (documentation changed)
│         ├[~] type InstanceRequirements
│         │ └ properties
│         │    └ BaselinePerformanceFactors: (documentation changed)
│         └[~] type PerformanceFactorReferenceRequest
│           ├  - documentation: undefined
│           │  + documentation: Specify an instance family to use as the baseline reference for CPU performance. All instance types that All instance types that match your specified attributes will be compared against the CPU performance of the referenced instance family, regardless of CPU manufacturer or architecture differences.
│           │  > Currently only one instance family can be specified in the list.
│           └ properties
│              └ InstanceFamily: (documentation changed)
├[~] service aws-cloudformation
│ └ resources
│    ├[~] resource AWS::CloudFormation::GuardHook
│    │ ├  - documentation: This is a CloudFormation resource for activating the first-party AWS::Hooks::GuardHook.
│    │ │  + documentation: The `AWS::CloudFormation::GuardHook` resource creates a Guard Hook with the specified attributes within your CloudFormation template. Using the Guard domain specific language (DSL), you can author Hooks to evaluate your resources before allowing stack creation, modification, or deletion. For more information, see [Guard Hooks](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/guard-hooks.html) in the *AWS CloudFormation Hooks User Guide* .
│    │ ├ properties
│    │ │  ├ Alias: (documentation changed)
│    │ │  ├ ExecutionRole: (documentation changed)
│    │ │  ├ FailureMode: (documentation changed)
│    │ │  ├ HookStatus: (documentation changed)
│    │ │  ├ LogBucket: (documentation changed)
│    │ │  ├ Options: (documentation changed)
│    │ │  ├ RuleLocation: (documentation changed)
│    │ │  ├ StackFilters: (documentation changed)
│    │ │  ├ TargetFilters: (documentation changed)
│    │ │  └ TargetOperations: (documentation changed)
│    │ ├ attributes
│    │ │  └ HookArn: (documentation changed)
│    │ └ types
│    │    ├[~] type Options
│    │    │ ├  - documentation: undefined
│    │    │ │  + documentation: Specifies the input parameters for a Guard Hook.
│    │    │ └ properties
│    │    │    └ InputParams: (documentation changed)
│    │    ├[~] type S3Location
│    │    │ ├  - documentation: S3 Source Location for the Guard files.
│    │    │ │  + documentation: Specifies the S3 location where your Guard rules or input parameters are located.
│    │    │ └ properties
│    │    │    ├ Uri: (documentation changed)
│    │    │    └ VersionId: (documentation changed)
│    │    ├[~] type StackFilters
│    │    │ ├  - documentation: Filters to allow hooks to target specific stack attributes
│    │    │ │  + documentation: The `StackFilters` property type specifies stack level filters for a Hook.
│    │    │ │  The `StackNames` or `StackRoles` properties are optional. However, you must specify at least one of these properties.
│    │    │ │  For more information, see [AWS CloudFormation Hooks stack level filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/hooks-stack-level-filtering.html) .
│    │    │ └ properties
│    │    │    ├ FilteringCriteria: (documentation changed)
│    │    │    ├ StackNames: (documentation changed)
│    │    │    └ StackRoles: (documentation changed)
│    │    ├[~] type StackNames
│    │    │ ├  - documentation: List of stack names as filters
│    │    │ │  + documentation: Specifies the stack names for the `StackFilters` property type to include or exclude specific stacks from Hook invocations.
│    │    │ │  For more information, see [AWS CloudFormation Hooks stack level filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/hooks-stack-level-filtering.html) .
│    │    │ └ properties
│    │    │    ├ Exclude: (documentation changed)
│    │    │    └ Include: (documentation changed)
│    │    ├[~] type StackRoles
│    │    │ ├  - documentation: List of stack roles that are performing the stack operations.
│    │    │ │  + documentation: Specifies the stack roles for the `StackFilters` property type to include or exclude specific stacks from Hook invocations based on their associated IAM roles.
│    │    │ │  For more information, see [AWS CloudFormation Hooks stack level filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/hooks-stack-level-filtering.html) .
│    │    │ └ properties
│    │    │    ├ Exclude: (documentation changed)
│    │    │    └ Include: (documentation changed)
│    │    └[~] type TargetFilters
│    │      └  - documentation: undefined
│    │         + documentation: The `TargetFilters` property type specifies the target filters for the Hook.
│    │         For more information, see [AWS CloudFormation Hook target filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/specify-hook-configuration-targetfilters.html) .
│    ├[~] resource AWS::CloudFormation::HookDefaultVersion
│    │ ├  - documentation: The `HookDefaultVersion` resource specifies the default version of the hook. The default version of the hook is used in CloudFormation operations for this AWS account and AWS Region .
│    │ │  + documentation: The `HookDefaultVersion` resource specifies the default version of the Hook. The default version of the Hook is used in CloudFormation operations for this AWS account and AWS Region .
│    │ └ properties
│    │    └ TypeName: (documentation changed)
│    ├[~] resource AWS::CloudFormation::HookTypeConfig
│    │ ├  - documentation: The `HookTypeConfig` resource specifies the configuration of a hook.
│    │ │  + documentation: The `HookTypeConfig` resource specifies the configuration of a Hook.
│    │ ├ properties
│    │ │  ├ Configuration: (documentation changed)
│    │ │  ├ ConfigurationAlias: (documentation changed)
│    │ │  ├ TypeArn: (documentation changed)
│    │ │  └ TypeName: (documentation changed)
│    │ └ attributes
│    │    └ ConfigurationArn: (documentation changed)
│    ├[~] resource AWS::CloudFormation::HookVersion
│    │ ├  - documentation: The `HookVersion` resource publishes new or first hook version to the AWS CloudFormation registry.
│    │ │  + documentation: The `HookVersion` resource publishes new or first Hook version to the AWS CloudFormation registry.
│    │ ├ properties
│    │ │  ├ ExecutionRoleArn: (documentation changed)
│    │ │  └ SchemaHandlerPackage: (documentation changed)
│    │ └ attributes
│    │    ├ Arn: (documentation changed)
│    │    ├ IsDefaultVersion: (documentation changed)
│    │    ├ TypeArn: (documentation changed)
│    │    └ VersionId: (documentation changed)
│    └[~] resource AWS::CloudFormation::LambdaHook
│      ├  - documentation: This is a CloudFormation resource for the first-party AWS::Hooks::LambdaHook.
│      │  + documentation: The `AWS::CloudFormation::LambdaHook` resource creates a Lambda Hook with the specified attributes within your CloudFormation template. You can use a Lambda Hook to evaluate your resources before allowing stack creation, modification, or deletion. This resource forwards requests for resource evaluation to a Lambda function. For more information, see [Lambda Hooks](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/lambda-hooks.html) in the *AWS CloudFormation Hooks User Guide* .
│      ├ properties
│      │  ├ Alias: (documentation changed)
│      │  ├ ExecutionRole: (documentation changed)
│      │  ├ FailureMode: (documentation changed)
│      │  ├ HookStatus: (documentation changed)
│      │  ├ LambdaFunction: (documentation changed)
│      │  ├ StackFilters: (documentation changed)
│      │  ├ TargetFilters: (documentation changed)
│      │  └ TargetOperations: (documentation changed)
│      ├ attributes
│      │  └ HookArn: (documentation changed)
│      └ types
│         ├[~] type StackFilters
│         │ ├  - documentation: Filters to allow hooks to target specific stack attributes
│         │ │  + documentation: The `StackFilters` property type specifies stack level filters for a Hook.
│         │ │  The `StackNames` or `StackRoles` properties are optional. However, you must specify at least one of these properties.
│         │ │  For more information, see [AWS CloudFormation Hooks stack level filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/hooks-stack-level-filtering.html) .
│         │ └ properties
│         │    ├ FilteringCriteria: (documentation changed)
│         │    ├ StackNames: (documentation changed)
│         │    └ StackRoles: (documentation changed)
│         ├[~] type StackNames
│         │ ├  - documentation: List of stack names as filters
│         │ │  + documentation: Specifies the stack names for the `StackFilters` property type to include or exclude specific stacks from Hook invocations.
│         │ │  For more information, see [AWS CloudFormation Hooks stack level filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/hooks-stack-level-filtering.html) .
│         │ └ properties
│         │    ├ Exclude: (documentation changed)
│         │    └ Include: (documentation changed)
│         ├[~] type StackRoles
│         │ ├  - documentation: List of stack roles that are performing the stack operations.
│         │ │  + documentation: Specifies the stack roles for the `StackFilters` property type to include or exclude specific stacks from Hook invocations based on their associated IAM roles.
│         │ │  For more information, see [AWS CloudFormation Hooks stack level filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/hooks-stack-level-filtering.html) .
│         │ └ properties
│         │    ├ Exclude: (documentation changed)
│         │    └ Include: (documentation changed)
│         └[~] type TargetFilters
│           └  - documentation: undefined
│              + documentation: The `TargetFilters` property type specifies the target filters for the Hook.
│              For more information, see [AWS CloudFormation Hook target filters](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/specify-hook-configuration-targetfilters.html) .
├[~] service aws-cloudfront
│ └ resources
│    ├[~] resource AWS::CloudFront::Distribution
│    │ └ types
│    │    └[~] type Logging
│    │      ├  - documentation: A complex type that controls whether access logs are written for the distribution.
│    │      │  + documentation: A complex type that specifies whether access logs are written for the distribution.
│    │      │  > If you already enabled standard logging (legacy) and you want to enable standard logging (v2) to send your access logs to Amazon S3, we recommend that you specify a *different* Amazon S3 bucket or use a *separate path* in the same bucket (for example, use a log prefix or partitioning). This helps you keep track of which log files are associated with which logging subscription and prevents log files from overwriting each other. For more information, see [Standard logging (access logs)](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/AccessLogs.html) in the *Amazon CloudFront Developer Guide* .
│    │      └ properties
│    │         └ Bucket: (documentation changed)
│    └[~] resource AWS::CloudFront::StreamingDistribution
│      └ types
│         └[~] type Logging
│           └ properties
│              └ Bucket: (documentation changed)
├[~] service aws-ecs
│ └ resources
│    ├[~] resource AWS::ECS::Service
│    │ ├ properties
│    │ │  └ AvailabilityZoneRebalancing: (documentation changed)
│    │ └ types
│    │    └[~] type DeploymentController
│    │      └  - documentation: The deployment controller to use for the service. For more information, see [Amazon ECS deployment types](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html) in the *Amazon Elastic Container Service Developer Guide* .
│    │         + documentation: The deployment controller to use for the service.
│    └[~] resource AWS::ECS::TaskDefinition
│      └ types
│         └[~] type ContainerDefinition
│           └ properties
│              └ VersionConsistency: (documentation changed)
├[~] service aws-lambda
│ └ resources
│    ├[~] resource AWS::Lambda::EventInvokeConfig
│    │ ├ properties
│    │ │  └ DestinationConfig: (documentation changed)
│    │ └ types
│    │    ├[~] type OnFailure
│    │    │ └ properties
│    │    │    └ Destination: (documentation changed)
│    │    └[~] type OnSuccess
│    │      └  - documentation: A destination for events that were processed successfully.
│    │         + documentation: A destination for events that were processed successfully.
│    │         To retain records of successful [asynchronous invocations](https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html#invocation-async-destinations) , you can configure an Amazon SNS topic, Amazon SQS queue, Lambda function, or Amazon EventBridge event bus as the destination.
│    └[~] resource AWS::Lambda::EventSourceMapping
│      └ types
│         └[~] type OnFailure
│           └ properties
│              └ Destination: (documentation changed)
├[~] service aws-mwaa
│ └ resources
│    └[~] resource AWS::MWAA::Environment
│      └ properties
│         ├ MaxWebservers: (documentation changed)
│         └ MinWebservers: (documentation changed)
├[~] service aws-qbusiness
│ └ resources
│    └[~] resource AWS::QBusiness::Application
│      └  - documentation: Creates an Amazon Q Business application.
│         > There are new tiers for Amazon Q Business. Not all features in Amazon Q Business Pro are also available in Amazon Q Business Lite. For information on what's included in Amazon Q Business Lite and what's included in Amazon Q Business Pro, see [Amazon Q Business tiers](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/tiers.html#user-sub-tiers) . You must use the Amazon Q Business console to assign subscription tiers to users.
│         > 
│         > A Amazon Q Apps service linked role will be created if it's absent in the AWS account when the QAppsConfiguration is enabled in the request. For more information, see [Using service-linked roles for Q Apps](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/using-service-linked-roles-qapps.html)
│         + documentation: Creates an Amazon Q Business application.
│         > There are new tiers for Amazon Q Business. Not all features in Amazon Q Business Pro are also available in Amazon Q Business Lite. For information on what's included in Amazon Q Business Lite and what's included in Amazon Q Business Pro, see [Amazon Q Business tiers](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/tiers.html#user-sub-tiers) . You must use the Amazon Q Business console to assign subscription tiers to users.
│         > 
│         > An Amazon Q Apps service linked role will be created if it's absent in the AWS account when `QAppsConfiguration` is enabled in the request. For more information, see [Using service-linked roles for Q Apps](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/using-service-linked-roles-qapps.html) .
│         > 
│         > When you create an application, Amazon Q Business may securely transmit data for processing from your selected AWS region, but within your geography. For more information, see [Cross region inference in Amazon Q Business](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/cross-region-inference.html) .
├[~] service aws-rbin
│ └ resources
│    └[~] resource AWS::Rbin::Rule
│      ├  - documentation: Resource Type definition for AWS::Rbin::Rule
│      │  + documentation: Creates a Recycle Bin retention rule. You can create two types of retention rules:
│      │  - *Tag-level retention rules* - These retention rules use resource tags to identify the resources to protect. For each retention rule, you specify one or more tag key and value pairs. Resources (of the specified type) that have at least one of these tag key and value pairs are automatically retained in the Recycle Bin upon deletion. Use this type of retention rule to protect specific resources in your account based on their tags.
│      │  - *Region-level retention rules* - These retention rules, by default, apply to all of the resources (of the specified type) in the Region, even if the resources are not tagged. However, you can specify exclusion tags to exclude resources that have specific tags. Use this type of retention rule to protect all resources of a specific type in a Region.
│      │  For more information, see [Create Recycle Bin retention rules](https://docs.aws.amazon.com/ebs/latest/userguide/recycle-bin.html) in the *Amazon EBS User Guide* .
│      ├ properties
│      │  ├ Description: (documentation changed)
│      │  ├ LockConfiguration: (documentation changed)
│      │  ├ ResourceTags: (documentation changed)
│      │  ├ RetentionPeriod: (documentation changed)
│      │  └ Status: (documentation changed)
│      ├ attributes
│      │  ├ Arn: (documentation changed)
│      │  └ LockState: (documentation changed)
│      └ types
│         ├[~] type ResourceTag
│         │ ├  - documentation: The resource tag of the rule.
│         │ │  + documentation: [Tag-level retention rules only] Information about the resource tags used to identify resources that are retained by the retention rule.
│         │ └ properties
│         │    ├ ResourceTagKey: (documentation changed)
│         │    └ ResourceTagValue: (documentation changed)
│         ├[~] type RetentionPeriod
│         │ ├  - documentation: The retention period of the rule.
│         │ │  + documentation: Information about the retention period for which the retention rule is to retain resources.
│         │ └ properties
│         │    ├ RetentionPeriodUnit: (documentation changed)
│         │    └ RetentionPeriodValue: (documentation changed)
│         └[~] type UnlockDelay
│           ├  - documentation: undefined
│           │  + documentation: Information about the retention rule unlock delay. The unlock delay is the period after which a retention rule can be modified or edited after it has been unlocked by a user with the required permissions. The retention rule can't be modified or deleted during the unlock delay.
│           └ properties
│              └ UnlockDelayValue: (documentation changed)
├[~] service aws-rds
│ └ resources
│    ├[~] resource AWS::RDS::DBCluster
│    │ └ types
│    │    └[~] type ServerlessV2ScalingConfiguration
│    │      └ properties
│    │         └ MinCapacity: (documentation changed)
│    └[~] resource AWS::RDS::GlobalCluster
│      ├ properties
│      │  └ GlobalEndpoint: (documentation changed)
│      └ types
│         └[~] type GlobalEndpoint
│           ├  - documentation: undefined
│           │  + documentation: The writer endpoint for the new global database cluster. This endpoint always points to the writer DB instance in the current primary cluster.
│           └ properties
│              └ Address: (documentation changed)
└[~] service aws-route53resolver
  └ resources
     └[~] resource AWS::Route53Resolver::FirewallRuleGroup
       └ types
          └[~] type FirewallRule
            └ properties
               ├ ConfidenceThreshold: (documentation changed)
               ├ DnsThreatProtection: (documentation changed)
               └ FirewallThreatProtectionId: (documentation changed)

Updates the L1 CloudFormation resource definitions with the latest changes from `@aws-cdk/aws-service-spec`
@aws-cdk-automation aws-cdk-automation added auto-approve contribution/core This is a PR that came from AWS. dependencies This issue is a problem in a dependency or a pull request that updates a dependency file. pr-linter/exempt-readme The PR linter will not require README changes pr-linter/exempt-test The PR linter will not require test changes pr-linter/exempt-integ-test The PR linter will not require integ test changes labels Nov 25, 2024
@aws-cdk-automation aws-cdk-automation requested review from a team November 25, 2024 13:47
@github-actions github-actions bot added the p2 label Nov 25, 2024
Copy link

codecov bot commented Nov 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.17%. Comparing base (bedcf16) to head (5ef2b3d).

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #32272   +/-   ##
=======================================
  Coverage   77.17%   77.17%           
=======================================
  Files         105      105           
  Lines        7169     7169           
  Branches     1315     1315           
=======================================
  Hits         5533     5533           
  Misses       1455     1455           
  Partials      181      181           
Flag Coverage Δ
suite.unit 77.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
packages/aws-cdk 77.17% <ø> (ø)
---- 🚨 Try these New Features:

@aws-cdk-automation
Copy link
Collaborator Author

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 5ef2b3d
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Copy link
Contributor

mergify bot commented Nov 25, 2024

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify bot merged commit 421d327 into main Nov 25, 2024
43 checks passed
@mergify mergify bot deleted the automation/spec-update branch November 25, 2024 14:18
Copy link

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-approve contribution/core This is a PR that came from AWS. dependencies This issue is a problem in a dependency or a pull request that updates a dependency file. p2 pr-linter/exempt-integ-test The PR linter will not require integ test changes pr-linter/exempt-readme The PR linter will not require README changes pr-linter/exempt-test The PR linter will not require test changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant