Cicd/gcp configuration #49
Annotations
1 error and 6 warnings
|
failed to execute gcloud command `gcloud beta run deploy sepomex-pr80 --image us-central1-docker.pkg.dev/sepomex-365521/icalialabs-sepomex/sepomex@sha256:864f9a07e3f4a0363f50f3f9e0494c2ffafad694569abb5c8592f1ce98ea5b14 --quiet --platform managed --region us-central1 --update-env-vars DATABASE_URL=postgres://%2Fcloudsql%2Fsepomex-365521%3Aus-central1%3Asepomex/sepomex-pr80,GOOGLE_CLOUD_PROJECT=sepomex-365521 --update-secrets DATABASE_USERNAME=database-username:latest,DATABASE_PASSWORD=database-password:latest --revision-suffix 8089fbd-1692745100 --allow-unauthenticated --add-cloudsql-instances sepomex-365521:us-central1:sepomex --min-instances 0 --service-account [email protected] --project sepomex-365521 --format json`: Skipped validating Cloud SQL API and Cloud SQL Admin API enablement due to an issue contacting the Service Usage API. Please ensure the Cloud SQL API and Cloud SQL Admin API are activated (see https://console.cloud.google.com/apis/dashboard).
Deploying container to Cloud Run service [sepomex-pr80] in project [sepomex-365521] region [us-central1]
Deploying...
Setting IAM Policy...............done
Creating Revision...........done
Routing traffic.......................................................................failed
Deployment failed
ERROR: (gcloud.beta.run.deploy) Revision 'sepomex-pr80-8089fbd-1692745100' is not ready and cannot serve traffic. The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable. Logs for this revision might contain more information.
Logs URL: https://console.cloud.google.com/logs/viewer?project=sepomex-365521&resource=cloud_run_revision/service_name/sepomex-pr80/revision_name/sepomex-pr80-8089fbd-1692745100&advancedFilter=resource.type%3D%22cloud_run_revision%22%0Aresource.labels.service_name%3D%22sepomex-pr80%22%0Aresource.labels.revision_name%3D%22sepomex-pr80-8089fbd-1692745100%22
For more troubleshooting guidance, see https://cloud.google.com/run/docs/troubleshooting#container-failed-to-start
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
The logs for this run have expired and are no longer available.
Loading