buildspec-- handle manifest validation failures

[huanjani]

Currently, if a workload manifest fails the validation step, the cause for the build failure isn't immediately clear. We should try to fail faster or surface the error better.

[wolverian]

Just as an example, my experience today might illustrate why this is a problem. (If this isn't the issue you meant, @huanjani, my apologies and I can create a new issue.)

I changed my deployment to platform: linux/arm64. The build step of my pipeline passed, but the deployment failed with this unclear message:

Looking into the execution details confused me even more!

Here we see a message with a red background (it's an error!) saying the stack updated (it's not an error). So which one is it?

I downloaded the input to the deployment step and saw the deployment manifest (i.e. the CloudFormation template) was empty. I then looked into the Build step logs and found this error hidden among the thousands of lines of output:

✘ validate manifest against environment test: validate ARM: 'Fargate Spot' is not supported when deploying on ARM architecture

The build didn't stop on this error, though, so I had to go through this backwards debugging session to find out the root cause.

[huanjani]

Thanks so much, @wolverian, for documenting your experience. Yes, this is exactly the issue we hope to fix soon!

[Lou1415926]

This is now released 🎉 in v1.14.0 https://github.com/aws/copilot-cli/releases/tag/v1.14.0 !