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

Update to latest AWS CDK version (2.151.0) #1058

Closed
1 task done
hshepherd opened this issue Aug 12, 2024 · 4 comments
Closed
1 task done

Update to latest AWS CDK version (2.151.0) #1058

hshepherd opened this issue Aug 12, 2024 · 4 comments

Comments

@hshepherd
Copy link

Describe the feature

Would it be possible to get a new release of blueprints that has peerDependencies on aws-cdk and aws-cdk-lib v2.151.0?

e.g.

NatGatewayProvider: https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.NatGatewayProvider.html
aws-cdk release: https://github.com/aws/aws-cdk/releases/tag/v2.151.0

Use Case

We have a requirement to be able to use the newly exported NatGatewayProvider in aws-cdk-lib version 2.151.0.
Since we are using cdk-eks-blueprints in the same project -- and blueprints is locked to 2.147.3 -- we cannot yet use this class.

Proposed Solution

// package.json
"peerDependencies": {
    "aws-cdk-lib": "2.150.0",
    "aws-cdk": "2.150.0"
}

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request

CDK version used

2.147.3

EKS Blueprints Version

1.15.1

Node.js Version

18.20.4

Environment details (OS name and version, etc.)

OSX 13.4

@shapirov103
Copy link
Collaborator

shapirov103 commented Aug 12, 2024

You should be able to upgrade your project to the latest CDK by overriding the version of the CDK in your package.json and running with --force flag, similar to what we use in our patterns repo here.

We do have plans to release 1.16 once the ipv6 support PR is merged.

@hshepherd
Copy link
Author

OK I will give this a try if this is a supported pattern
Thanks for the response!

Copy link

This issue has been automatically marked as stale because it has been open 60 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Nov 11, 2024
@shapirov103
Copy link
Collaborator

This was addressed in #1087.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants