Upgrade CDK to v2 #1452
Closed
Upgrade CDK to v2 #1452
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
javiertoledo
added
do not merge
|
Oops, looks like you forgot to add a changeset.
This command will prompt you for a change description and generate a changeset file. You can read more about changesets here. Remember that you should use the version bump that is appropriate for the change you are making:
If you are unsure about which version bump to use, please ask in the comments and we will help you out. |
7 tasks
This was referenced Oct 8, 2023
javiertoledo
force-pushed
the
upgrade/cdk-v2
branch
from
74aac9e to
350bbaf
Compare
javiertoledo
force-pushed
the
upgrade/cdk-v2
branch
2 times, most recently
from
c453788 to
0ad74bb
Compare
javiertoledo
force-pushed
the
upgrade/cdk-v2
branch
from
0ad74bb to
cfc048e
Compare
|
Closing as this no longer seem to make sense for the future of the project. See #1477 for more detail. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is an exploration branch to upgrade the CDK to v2 for AWS.
Update: The CDK v2 comes with major changes in how CDK applications are handled. The CDKToolkit has been extracted into a CLI tool, so upgrading to v2 would force us to rewrite a significant portion of our deployment and nuke scripts, and the new implementation would require either running shell commands or using alpha packages. Given the situation, we want to explore the cost of migrating the AWS provider to the CDKTF before going further on this path.
Checks