# google-cloud


05/16/2022, 2:35 PM
Hello ! I’m trying to deploy the firestore rules file I have through Pulumi. I use
Copy code
new gcp.firebaserules.Ruleset(
      project: gcp.config.project,
      source: {
        files: [
            content: fs
              .readFileSync(path.resolve(__dirname, "../../firestore.rules"))
            name: "firestore.rules",
    { dependsOn: services }
I have enabled the firebaserules service this way:
Copy code
new gcp.projects.Service("firebaserules", {
  service: "<|>",
But I receive a SERVICE_DISABLED error when I run pulumi up:
Copy code
        "@type": "<|>",
        "domain": "<|>",
        "metadata": {
          "consumer": "projects/764086053860",
          "service": "<|>"
        "reason": "SERVICE_DISABLED"
That project number is not mine weirdly… It also gives me this error message but I don’t think that it’s related to my problem, is it?
Copy code
Error creating Ruleset: googleapi: Error 403: Your application has authenticated using end user credentials from the Google Cloud SDK or Google Cloud Shell which are not supported by the <|>. We recommend configuring the billing/quota_project setting in gcloud or using a service account through the auth/impersonate_service_account setting. For more information about service accounts and how to use them in your application, see <>. If you are getting this error with curl or similar tools, you may need to specify 'X-Goog-User-Project' HTTP header for quota and billing purposes. For more information regarding 'X-Goog-User-Project' header, please check <>.
Is there an additional service to enable that I don’t know about maybe? Has anybody encountered a similar error?
It actually seems to be helpful since authenticating as a service account using
gcloud auth activate-service-account
with a keyfile works well


06/03/2022, 9:23 PM
I'm seeing this same
error when trying to create a new pubsub topic -- it tries to create the resource in a totally different project from the one specified in the code
it turned out the user we were trying to run the deploy with didn't have proper permissions