-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
🪟🔧 Connector builder: Do not rely on local cdk anymore #22391
Conversation
# Make sure this is aligned with the CDK version of the connector builder server | ||
DEFAULT_CDK_VERSION="0.25.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just confirming, is the plan to address keeping these aligned automatically in a follow-up PR, since in the description you said this PR does not fully close that issue?
Do you have an idea of how to solve that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small nit about adding a comment but up to you on if you think it is necessary to add.
Otherwise this LGTM, tested locally and it works as expected
* do not rely on local cdk anymore * cache versioned schemas * fix used version * review comments
What
Related to #21830
Downloads the CDK in the specified version as part of the frontend build to build typescript types instead of relying on CDK files in a folder as part of the same repo.
This is not fixing the linked issue as it's not ensuring connector builder server and webapp use the same version of the CDK, it's done to unblock the repo split in the short term.
How
Do a curl request to fetch the tar ball of the cdk, then extract the declarative manifest schema from it. Also add a way to overwrite the used version and location of the manifest schema via environment variables to allow local development.