The feature 'sandbox selector' is not supported in the declared launch about deploy-cloudrun HOT 8 CLOSED

Any updates on this? Also started seeing this on one of our services, though not all. Not sure why as all the services use this action in the same way. It happens every time on the service where there is a problem so perhaps something in the config on GCP side that can be changed?

from deploy-cloudrun.

Any updates on this? Also started seeing this on one of our services, though not all. Not sure why as all the services use this action in the same way. It happens every time on the service where there is a problem so perhaps something in the config on GCP side that can be changed?

I believe PR #30 should fix this due to additional annotations added on the GCP side.

from deploy-cloudrun.

No stress! We are deploying manually for now so not the end of the world 🙂

A ping on this thread would be great, thank you 👍

from deploy-cloudrun.

Hi @rainy-me , I wouldn't expect this error when you are not using the metadata input and I am not able to reproduce. It also doesn't seem like updates to the action is causing this. My assumption is that your container is not starting correctly. Can you go the the Cloud Run UI to check the logs for more information? Can you also try to deploy this manually?

from deploy-cloudrun.

Thanks for your quick response :) I tried to deploy a new version but this issue still happens. The most wired part is it worked before but stop working all of a sudden.

when you are not using the metadata input

I have some configurations set in the Cloud Run console like max instances, but not putting them explicitly in the metadata field in of this action. Should I include them in the action yml too?

container is not starting correctly
check the logs for more information

It seems that the action failed before creating a cloudrun new revision. The only log I can found is something similar. If the container is not starting correctly, I expect to see logs show a new revision is created by failed to start. Is that correct?

I can find built and pushed container in the previous step in the container registry though.

Can you also try to deploy this manually

I'm able to deploy it manually from the console.

from deploy-cloudrun.

Thank you!

from deploy-cloudrun.

I see PR #30 has been merged but the issue is still occurring, I assume this is because there hasn't yet been a new release. Is the plan to do a new release sometime soon?

from deploy-cloudrun.

I apologize @rickkln , I haven't rebuilt and released the new version yet due to PR #31 . I can ping this thread once released.

from deploy-cloudrun.