-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
AWS assets broken #33492
Comments
Yes, related to #33491 All CodePipelines generated with AWS CDK are failing. :( |
Seems to be fixed now. |
This should have been fixed. Let me know if the issue still exists. |
I believe there is an additional issue is coming from the new version of In my case, I have a self-mutating pipeline that is broken because it is using
See the following line that installs new version that breaks this image:
Let me know if I'm incorrect in this assumption |
To confirm that I saw the above WebAssembly error on 1.0.17 and 1.2.0 of the standard CDKDeploy step.
|
@jonnysmith1981 issue referenced in #33494 |
@jonnysmith1981 We started getting the same exact error today when we run the code in our codepipeline. Note that when we cdk ls and synth locally, we dont see the error. Then we updated CDK to version 2.175.1, changed python3 to python in our cdk.json and then we passed through that and got to this error which is also opened today #33495 Before that (but also today) we got error in FileAsset stage related to NPM which suddenly fixed on its own. Seems AWS released something on their end that broke some components? |
lolol yeah I'm now seeing this with 2.1000.1. Looks like they sorted out the wasm one, but this is new. At this point they should just rollback to 2.179.0 because almost everyone is completely unable to deploy stuff at the moment. Seems like the version split should have happened after significantly more testing. |
If you are seeing The |
Comments on closed issues and PRs are hard for our team to see. |
aws-cdk/packages/aws-cdk-lib/pipelines/lib/codepipeline/codepipeline.ts
Line 841 in 7be4456
Hi looks like you need to replace @latest with @2 Thanks
The text was updated successfully, but these errors were encountered: