Rico Hermans
Rico Hermans
There is no easy workaround as of yet.
What could work is producing 2 cloud artifacts from the synth step (one with the assets, one without) and then using [property overrides](https://docs.aws.amazon.com/cdk/latest/guide/cfn_layer.html) to switch between them for the different...
There is no timeline as of yet.
Another workaround you could try is postprocessing the `.json` files in a post-build script in your Synth step and dedupe the assets yourself.
> e.g., GitHub workflows Probably only GitHub workflows running on CodeBuild runners (i.e., this will happen on anything that runs on EC2)
Red herring! We in fact only see this on naked GitHub Actions machines.
I've come to a discovery: * On GitHub Actions, they're running a routable version of the IMDS endpoint (`169.254.169.254`) that always returns a 400. So here's the difference: | Machine...
Relatedly, I've been looking at the `NodeHttpHandler` and I noticed the handling of error cases could be a bit cleaner. Specifically, when introducing `console.log()`s in there to see what's happening...
We can add a property to customize that URL.
Disappointing that this has been open for 5 years and nobody from the Jest team has responded to it 🫤