Should check if App Runner is available in current region before creating svc

[idawnwon]

Hi all! Thanks for your great work! ♥️

I tried to create a Request-Driven Web Service in ap-northeast-2.

At first I didn't know this region does not support App Runner.

While copilot is creating test env, an error popped up:

- Update regional resources with stack set "APP_NAME-infrastructure"  [failed]

get app resources: describing application resources: getting outputs for stack  in region ap-northeast-2: describe stack : ValidationError: 2 validation errors detected: Value '' at 'stackName' failed to satisfy constraint: Member must have length greater than or equal to 1; Value '' at 'stackName' failed to satisfy constraint: Member must satisfy regular expression pattern: [a-zA-Z][-a-zA-Z0-9]*|arn:[-a-zA-Z0-9:/._+]*

While it is easy to figure out App Runner is not supported in current region, but is hard to clean up with copilot app delete, the same error would pop up again, then command terminated. Ended up cleaning by hand:

• Delete app name in SSM Parameter Store
• Delete stack APP_NAME-infrastructure-roles in Cloudformation
• Delete copilot folder in project

Is it possible to check if App Runner is available in current region before doing anything further?

I would like to create a PR for this great product, but I am not good at Go language, feeling so hard to find where to fix.

Given this is not a critical issue, I wish someone would give me some hint 😅, I would learn on the fly then fix it.
If pointing out problems is more trouble than fixing them, then don't let me, a newbie, mess around. 🤣

[bvtujo]

Thanks @idawnwon for pointing this out. It definitely makes sense to me for us to check whether app runner is available before deployment. Do you have a place that you check, or an API that you call, to determine availability?

edit: It looks like we print a warning about this when you deploy a new App Runner service. We don't error out, though, because availability is hardcoded in the SDK and we don't want to block customers with older Copilot/SDK versions if a new region is made available.

It still totally makes sense to print this warning during RDWS initialization, though, since during deploy you have to interrupt the CLI very quickly to avoid a messy CFN stack deployment.

[idawnwon]

Thanks @bvtujo for your timely approach!
Waiting for enhancement!
Contact me anytime if you need help!