Issue detecting creation of bigquerydatatransfer v1

[japerry911]

What happened?

After running Pulumi up, it creates successfully but fails to read/detect and will therefore create a new transfer every time up is ran.

google-native:bigquerydatatransfer/v1:TransferConfig (google_ads_bigquery_transfer_config):
    error: object retrieval failure after successful create / read state: googleapi: Error 404: The requested transfer config (projects/fd-development-396922/locations/us/transferConfigs/google_ads_bigquery_transfer_config-7940c19) was not found.

Expected Behavior

To create successfully and detect it in future so it doesn't recreate duplicates.

Steps to reproduce

# --Google Cloud BigQuery Data Transfer Service--
# -Transfer Configs-
google_ads_bigquery_transfer_config = gcp_native.bigquerydatatransfer.v1.TransferConfig(  # noqa: E501
    "google_ads_bigquery_transfer_config",
    display_name="Google Ads BigQuery BQ Transfer",
    data_source_id="google_ads",
    params={
        "customer_id": "2120024652",
        "exclude_removed_items": False,
        "include_googleads_new_tables": True,
        "include_pmax": False,
    },
    data_refresh_window_days=30,
    destination_dataset_id=google_ads_bq_transfer_dataset.dataset_id,
    disabled=False,
    email_preferences={
        "enable_failure_email": False,  # Would send to owner of BQ Transfer entity
    },
    location="US",
    notification_pubsub_topic=google_ads_bigquery_transfer_topic.id,
    schedule="every 24 hours",
    version_info="<REDACTED>",
)

Output of pulumi about

CLI          
Version      3.78.1
Go Version   go1.20.7
Go Compiler  gc

Plugins
NAME           VERSION
gcp            6.64.0
google-native  0.31.1
python         unknown

Host     
OS       darwin
Version  13.5
Arch     arm64

Additional context

I can't use the production-ready Pulumi-GCP version quiet yet due to it missing verision_info parameter, unless there is a way to add it that I missed. That's the only reason I am using pre-release version.

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).