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(deps-dev): bump the cdk group in /cdk with 3 updates #2904

Merged
merged 1 commit into from
Sep 23, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 23, 2024

Bumps the cdk group in /cdk with 3 updates: @guardian/cdk, aws-cdk and aws-cdk-lib.

Updates @guardian/cdk from 59.4.0 to 59.5.2

Release notes

Sourced from @​guardian/cdk's releases.

v59.5.2

Patch Changes

  • 1110a11: fix(experimental-ec2-pattern): Create Policy first

    When deploying Prism with the GuEc2AppExperimental for the first time, the deployment failed with the cloud-init-output logs stating:

    An error occurred (AccessDenied) when calling the DescribeTargetHealth operation: User: arn:aws:sts::000000000000:assumed-role/prism-CODE-InstanceRolePrism/i-0cee86d64de253ca4 is not authorized to perform: elasticloadbalancing:DescribeTargetHealth because no identity-based policy allows the elasticloadbalancing:DescribeTargetHealth action
    

    This suggests the instance update was started before the policy was created.

    Make the ASG depend on the policy that grants these permissions to resolve, as CloudFormation creates dependencies first.

  • 5add16c: feat(experimental-ec2-pattern): Tag launch template to improve observability

v59.5.1

Patch Changes

  • fed2598: fix(experimental-ec2-pattern): Add buffer to rolling update timeout

    If we consider the health check grace period to be the time it takes the "normal" user data to run, the rolling update should be configured to be a little longer to cover the additional time spent polling the target group.

    A buffer of 1 minute is somewhat arbitrarily chosen. Too high a value, then we increase the time it takes to automatically rollback from a failing healthcheck. Too low a value, then we risk flaky deploys.

v59.5.0

Minor Changes

feat(experimental-ec2-pattern): Pattern to deploy ASG updates w/CFN (#2417)

Included in this update is a new experimental pattern GuEc2AppExperimental, which can be used in place of a GuEc2App:

import { GuEc2AppExperimental } from "@guardian/cdk/lib/experimental/patterns/ec2-app";

This pattern will add an AutoScalingRollingUpdate policy to the autoscaling group.This allows application updates to be performed like a standard CloudFormation update, and using the custom logic provided by Riff-Raff's autoscaling deployment type is unnecessary.

This experimental pattern has few requirements.

Add the build number to the application artifact

This change requires versioned artifacts.

The easiest way to achieve this is by adding the build number to the filename of the artifact:

</tr></table> 

... (truncated)

Changelog

Sourced from @​guardian/cdk's changelog.

59.5.2

Patch Changes

  • 1110a11: fix(experimental-ec2-pattern): Create Policy first

    When deploying Prism with the GuEc2AppExperimental for the first time, the deployment failed with the cloud-init-output logs stating:

    An error occurred (AccessDenied) when calling the DescribeTargetHealth operation: User: arn:aws:sts::000000000000:assumed-role/prism-CODE-InstanceRolePrism/i-0cee86d64de253ca4 is not authorized to perform: elasticloadbalancing:DescribeTargetHealth because no identity-based policy allows the elasticloadbalancing:DescribeTargetHealth action
    

    This suggests the instance update was started before the policy was created.

    Make the ASG depend on the policy that grants these permissions to resolve, as CloudFormation creates dependencies first.

  • 5add16c: feat(experimental-ec2-pattern): Tag launch template to improve observability

59.5.1

Patch Changes

  • fed2598: fix(experimental-ec2-pattern): Add buffer to rolling update timeout

    If we consider the health check grace period to be the time it takes the "normal" user data to run, the rolling update should be configured to be a little longer to cover the additional time spent polling the target group.

    A buffer of 1 minute is somewhat arbitrarily chosen. Too high a value, then we increase the time it takes to automatically rollback from a failing healthcheck. Too low a value, then we risk flaky deploys.

59.5.0

Minor Changes

  • f4e2a7c: feat(experimental-ec2-pattern): Pattern to deploy ASG updates w/CFN

    Included in this update is a new experimental pattern GuEc2AppExperimental, which can be used in place of a GuEc2App:

    import { GuEc2AppExperimental } from "@guardian/cdk/lib/experimental/patterns/ec2-app";

    This pattern will add an AutoScalingRollingUpdate policy to the autoscaling group. This allows application updates to be performed like a standard CloudFormation update, and using the custom logic provided by Riff-Raff's autoscaling deployment type is unnecessary.

    This experimental pattern has few requirements.

... (truncated)

Commits
  • 71af94b Merge pull request #2466 from guardian/changeset-release/main
  • 8bdea84 Bump package version
  • e9f9862 Merge pull request #2465 from guardian/aa/build-identifier
  • 311607c Merge pull request #2464 from guardian/aa/depends-on
  • 5add16c chore: Add changeset
  • 17a00be feat(experimental-ec2-pattern): Add buildIdentifier prop
  • 1110a11 chore: Add changeset
  • 21015c2 fix(experimental-ec2-pattern): Create Policy first
  • 70de4fb Merge pull request #2463 from guardian/changeset-release/main
  • 5eee278 Bump package version
  • Additional commits viewable in compare view

Updates aws-cdk from 2.158.0 to 2.159.1

Release notes

Sourced from aws-cdk's releases.

v2.159.1

Reverts

  • fix(ec2): fixing vpc endpoint pattern for ecr and ecr docker (#31496) (f7e8452)

Alpha modules (2.159.1-alpha.0)

v2.159.0

Features

Bug Fixes


Alpha modules (2.159.0-alpha.0)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • kinesisfirehose-alpha: encryptionKey property is removed and encryption property type has changed from the StreamEncryption enum to the StreamEncryption class.

To pass in a KMS key for the customer managed key case, use StreamEncryption.customerManagedKey(key)

Details

Replaced encryption and encryptionKey properties with a single property encryption of type StreamEncryption and is used by calling one of the 3 methods:

SreamEncryption.unencrypted()
StreamEncryption.awsOwnedKey()
StreamEncryption.customerManagedKey(key?: IKey)

This makes it so it's not longer possible to pass in a key when the encryption type is AWS owned or unencrypted. The key is an optional parameter in StreamEncryption.customerManagedKey(key?: IKey) so following the previous behaviour, if a key is provided it will be used, otherwise a key will be created for the user.

Description of how you validated changes

... (truncated)

Changelog

Sourced from aws-cdk's changelog.

2.159.1 (2024-09-19)

Reverts

  • fix(ec2): fixing vpc endpoint pattern for ecr and ecr docker (#31496) (f7e8452)

2.159.0 (2024-09-18)

Features

Bug Fixes

Commits
  • 0da4f43 fix(cli): hotswapping appsync functions fails when API does not return functi...
  • b6ad97f fix(cli): release outdir lock when synth fails (#30874)
  • 44134ad fix(cli): bootstrap respects qualifier from cdk.json (#31410)
  • ff02cca fix(ssm): update ssm-context to prevent raising an error on missing parameter...
  • See full diff in compare view

Updates aws-cdk-lib from 2.158.0 to 2.159.1

Release notes

Sourced from aws-cdk-lib's releases.

v2.159.1

Reverts

  • fix(ec2): fixing vpc endpoint pattern for ecr and ecr docker (#31496) (f7e8452)

Alpha modules (2.159.1-alpha.0)

v2.159.0

Features

Bug Fixes


Alpha modules (2.159.0-alpha.0)

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

  • kinesisfirehose-alpha: encryptionKey property is removed and encryption property type has changed from the StreamEncryption enum to the StreamEncryption class.

To pass in a KMS key for the customer managed key case, use StreamEncryption.customerManagedKey(key)

Details

Replaced encryption and encryptionKey properties with a single property encryption of type StreamEncryption and is used by calling one of the 3 methods:

SreamEncryption.unencrypted()
StreamEncryption.awsOwnedKey()
StreamEncryption.customerManagedKey(key?: IKey)

This makes it so it's not longer possible to pass in a key when the encryption type is AWS owned or unencrypted. The key is an optional parameter in StreamEncryption.customerManagedKey(key?: IKey) so following the previous behaviour, if a key is provided it will be used, otherwise a key will be created for the user.

Description of how you validated changes

... (truncated)

Changelog

Sourced from aws-cdk-lib's changelog.

2.159.1 (2024-09-19)

Reverts

  • fix(ec2): fixing vpc endpoint pattern for ecr and ecr docker (#31496) (f7e8452)

2.159.0 (2024-09-18)

Features

Bug Fixes

Commits
  • f7e8452 revert: fix(ec2): fixing vpc endpoint pattern for ecr and ecr docker (#31496)
  • 7ecfae4 chore(release): 2.159.0
  • de7ab7c fix(ecs): reduce ecs service task role cloudwatch permissions when no log con...
  • 60ce351 feat: update L1 CloudFormation resource definitions (#31484)
  • f60d13b docs(s3): updated docstring for BucketPolicy() (#31395)
  • 33eea3f feat(opensearch): support OpenSearch version 2.15 (#31398)
  • 95c49ab fix(ec2): fixing vpc endpoint pattern for ecr and ecr docker (#31434)
  • 1726abd fix(lambda): invalid Version object created from Version.fromVersionArn (#31433)
  • 386fca3 fix(eks): update private ecr repo url regex (#31394)
  • 84701d6 chore(s3): readme update with mixing L1 and L2 bucket policy (#31437)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the cdk group in /cdk with 3 updates: [@guardian/cdk](https://github.com/guardian/cdk), [aws-cdk](https://github.com/aws/aws-cdk/tree/HEAD/packages/aws-cdk) and [aws-cdk-lib](https://github.com/aws/aws-cdk/tree/HEAD/packages/aws-cdk-lib).


Updates `@guardian/cdk` from 59.4.0 to 59.5.2
- [Release notes](https://github.com/guardian/cdk/releases)
- [Changelog](https://github.com/guardian/cdk/blob/main/CHANGELOG.md)
- [Commits](guardian/cdk@v59.4.0...v59.5.2)

Updates `aws-cdk` from 2.158.0 to 2.159.1
- [Release notes](https://github.com/aws/aws-cdk/releases)
- [Changelog](https://github.com/aws/aws-cdk/blob/main/CHANGELOG.v2.md)
- [Commits](https://github.com/aws/aws-cdk/commits/v2.159.1/packages/aws-cdk)

Updates `aws-cdk-lib` from 2.158.0 to 2.159.1
- [Release notes](https://github.com/aws/aws-cdk/releases)
- [Changelog](https://github.com/aws/aws-cdk/blob/main/CHANGELOG.v2.md)
- [Commits](https://github.com/aws/aws-cdk/commits/v2.159.1/packages/aws-cdk-lib)

---
updated-dependencies:
- dependency-name: "@guardian/cdk"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: cdk
- dependency-name: aws-cdk
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: cdk
- dependency-name: aws-cdk-lib
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: cdk
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested a review from a team as a code owner September 23, 2024 08:18
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 23, 2024
@coldlink coldlink merged commit 823839e into main Sep 23, 2024
19 checks passed
@coldlink coldlink deleted the dependabot/npm_and_yarn/cdk/cdk-902e2e0c6b branch September 23, 2024 08:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant