You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have no idea if it's related to this action, but it's where the issue appears, so I will report it here. Please let me know if I need to report it elsewhere.
What basically happens is I trigger a Github Action to deploy my Firebase development, and I get an error during deployment:
Request to https://cloudscheduler.googleapis.com/v1/projects/*****-test/locations/europe-west1/jobs/firebase-schedule-pubsub-****-europe-west1?updateMask=name%2CtimeZone%2CpubsubTarget%2Cschedule%2CretryConfig.maxDoublings%2CretryConfig.retryCount%2CretryConfig.maxBackoffDuration%2CretryConfig.minBackoffDuration%2CretryConfig.maxRetryDuration had HTTP Error: 403, The principal (user or service account) lacks IAM permission "cloudscheduler.jobs.update" for the resource "projects/*****-test/locations/europe-west1/jobs/firebase-schedule-pubsub-****-europe-west1" (or the resource may not exist).
Request to https://cloudscheduler.googleapis.com/v1/projects/*****-test/locations/europe-west1/jobs/firebase-schedule-pubsub-****-europe-west1?updateMask=name%2CtimeZone%2CpubsubTarget%2Cschedule%2CretryConfig.maxDoublings%2CretryConfig.retryCount%2CretryConfig.maxBackoffDuration%2CretryConfig.minBackoffDuration%2CretryConfig.maxRetryDuration had HTTP Error: 403, The principal (user or service account) lacks IAM permission "cloudscheduler.jobs.update" for the resource "projects/*****-test/locations/europe-west1/jobs/firebase-schedule-pubsub-****-europe-west1" (or the resource may not exist).
Request to https://cloudscheduler.googleapis.com/v1/projects/*****-test/locations/europe-west1/jobs/firebase-schedule-pubsub-****-europe-west1?updateMask=name%2CtimeZone%2CpubsubTarget%2Cschedule%2CretryConfig.maxDoublings%2CretryConfig.retryCount%2CretryConfig.maxBackoffDuration%2CretryConfig.minBackoffDuration%2CretryConfig.maxRetryDuration had HTTP Error: 403, The principal (user or service account) lacks IAM permission "cloudscheduler.jobs.update" for the resource "projects/*****-test/locations/europe-west1/jobs/firebase-schedule-pubsub-****-europe-west1" (or the resource may not exist).
However simply running the Action a second time shows no issues and everything is deployed correctly.
I use w9jds/firebase-action@master in my deployment configuration file with the following args: deploy --project test --force
The text was updated successfully, but these errors were encountered:
This isn't related to the Action, it looks like you don't have the proper permissions setup in your GCP project. Look at the README it tells you that you need specific permissions setup, your error specifically tells you which ones you are missing.
But why does it work the second time without changing anything?
On 7 Jan 2025, at 07:25, Jeremy Shore ***@***.***> wrote:
This isn't related to the Action, it looks like you don't have the proper permissions setup in your GCP project. Look at the README it tells you that you need specific permissions setup, your error specifically tells you which ones you are missing.
—
Reply to this email directly, view it on GitHub<#244 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAMAGUZLKAMSNANLB6IBH532JNXNFAVCNFSM6AAAAABUV5ZAV6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZUGQ4DANBRGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
I have no idea if it's related to this action, but it's where the issue appears, so I will report it here. Please let me know if I need to report it elsewhere.
What basically happens is I trigger a Github Action to deploy my Firebase development, and I get an error during deployment:
However simply running the Action a second time shows no issues and everything is deployed correctly.
I use
w9jds/firebase-action@master
in my deployment configuration file with the following args:deploy --project test --force
The text was updated successfully, but these errors were encountered: