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

chore(release): 2.110.0 #28041

Merged
merged 9 commits into from
Nov 16, 2023
Merged

chore(release): 2.110.0 #28041

merged 9 commits into from
Nov 16, 2023

Conversation

aws-cdk-automation
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation commented Nov 16, 2023

See CHANGELOG

mergify bot and others added 9 commits November 16, 2023 01:00
Add integ test for postgres with access to S3 bucket for import and export.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…on 2022 (#28029)

This PR supports RDS for SQL Server 16.00.4085.2.v1 as major version 2022.

https://aws.amazon.com/jp/about-aws/whats-new/2023/11/amazon-rds-sql-server-sql-server-major-version-2022/

```bash
❯ aws rds describe-db-engine-versions --engine sqlserver-ee --query "DBEngineVersions[?EngineVersion=='16.00.4085.2.v1'].[DBEngineVersionDescription,EngineVersion,DBParameterGroupFamily,MajorEngineVersion,Status]"
[
    [
        "SQL Server 2022 16.00.4085.2.v1",
        "16.00.4085.2.v1",
        "sqlserver-ee-16.0",
        "16.00",
        "available"
    ]
]
```

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Use npx to run project-specific cdk, not a globally installed version.

This ensures everybody working on the project uses the same version of the command-line interface.

With the previous instructions, if anybody had `cdk` installed globally, e.g., via `npm install --global aws-cdk` or `homebrew install aws-cdk`, they would run that version. It seems desirable that everybody working on a CDK app uses the same version of the command-line interface, as specified in `package.json` (or `package-lock.json`).

Example:

Given a `package.json` which specifies `"aws-cdk": "2.104.0"` and a globally installed `cdk`, this can happen:

```shell
$ cdk --version
2.108.1 (build 2320255)

$ npx cdk --version
2.104.0 (build 3b99abe)
```


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Document for AmazonLinux2023ImageSsmParameter has typo `amazon linux 2022`. 
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.AmazonLinux2023ImageSsmParameter.html
> Generates a SSM Parameter name for a specific amazon linux 2022 AMI.

It seems to be code clone from AmazonLinux2022ImageSsmParameter.
https://github.com/aws/aws-cdk/blob/2f26f78abec3ca313b18026e58eb24698baaa1f9/packages/aws-cdk-lib/aws-ec2/lib/machine-image/amazon-linux-2022.ts#L56

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
AWS Service Spec packages to latest versions.
Structured logging enables automated analysis of the logs, thus enables customers to perform quick exploratory and automated monitoring the health of their applications, and helps them troubleshoot their production issues faster. Structured logging is now considered to be a monitoring best practice.

Lambda is developing Advance Logging Controls to give developers and operators more control over their function logs. The feature allows customers to capture logs in JSON format and control the level of details in emitted logs. To ensure compatibility and enable these capabilities, four new fields (LogFormat, ApplicationLogLevel, SystemLogLevel, and LogGroup) will be added to the existing LoggingConfig structure. Also, even adding custom log group for Log group section to have the flexibility of changing the name instead of having it as default. This update empowers customers to define their logging behavior and efficiently manage their function logs, reflecting Lambda's commitment to delivering a user-friendly logging solution that addresses the evolving needs of users.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This feature is still under development and the warning isn't clear enough on that point.

I also added in a small improvement to compare the input language as lowercase. No need to throw an error just because someone types TypeScript instead of typescript.



----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@aws-cdk-automation aws-cdk-automation added auto-approve pr/no-squash This PR should be merged instead of squash-merging it labels Nov 16, 2023
@aws-cdk-automation aws-cdk-automation requested a review from a team November 16, 2023 21:15
@aws-cdk-automation
Copy link
Collaborator Author

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 7480baf
  • 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 16, 2023

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

@mergify mergify bot merged commit c6471f2 into v2-release Nov 16, 2023
28 of 29 checks passed
@mergify mergify bot deleted the bump/2.110.0 branch November 16, 2023 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-approve p2 pr/no-squash This PR should be merged instead of squash-merging it
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants