having some issues with a number of resources deploying (or attempting to deploy) in the wrong project:

mysql-instance:
    type: gcp:sql:DatabaseInstance
    properties:
      region: us-east4
      databaseVersion: MYSQL_5_7
      settings:
        ipConfiguration:
          authorizedNetworks:
            - value: 0.0.0.0/0
        tier: ${mysqlTier}
      deletionProtection: ${dbProtection}

All resources of that same type have this issue

gcp:sql:DatabaseInstance

I know I can force the project adding that to the resource config, but I shouldn't need to specify it on everything? My pulumi config is set correctly:

config:
  ...
  gcp:project: my-new-proj
  ...

gcloud config list:

[core]
account = <mailto:eph-deployer@old-proj.iam.gserviceaccount.com|eph-deployer@old-proj.iam.gserviceaccount.com>
disable_usage_reporting = True
project = my-new-proj

Your active configuration is: [default]

SA "eph-deployer" is Owner of "my-new-proj" Also in bash env:

GOOGLE_PROJECT=my-new-proj

This sounds really weird. I've created instances correctly to correct project. You are using yaml for configuration? This is just a wild guess but it might be a bug in the yaml implementation which is brand new