No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@U025LJGGJ1L> any resource missing from a "native" provider is because it doesn't exist in the upstream cloud providers exposed API

It looks like the tf provider which we use to build pulumi-gcp has some logic to expand the template:

<https://github.com/hashicorp/terraform-provider-google/blob/main/google/resource_data_catalog_tag.go#L140>

You can mix and match providers happily, so I'd just use the gcp provider for that one resource

thanks <@UCWG26BH7> I tried that but got some `gcp:datacatalog:Tag o40_pii_tags creating error: expected non-nil error with nil state during Create of urn:pulumi:prod::astro::gcp:datacatalog/tag:Tag::o40_pii_tags`  which I understand often is due to upstream bugs, i.e. terraform in this case?

Maybe I just end up creating my own dynamic resource provider instead :man-shrugging:

yeah that's unfortunate :disappointed: seems like a dynamic provider might be the only way

It looks like there is an api to create tags in gcp <https://cloud.google.com/data-catalog/docs/reference/rpc/google.cloud.datacatalog.v1#google.cloud.datacatalog.v1.CreateTagRequest>

it doesn't appear in the discvoery API

<https://github.com/pulumi/pulumi-google-native/blob/master/discovery/datacatalog_v1beta1.json>
<https://github.com/pulumi/pulumi-google-native/blob/master/discovery/datacatalog_v1.json>

It is there but tied to either entries or entryGroup <https://github.com/pulumi/pulumi-google-native/blob/0cc776d05b04a2829cd91afacd9b24c413d8b359/discovery/datacatalog_v1.json#L754>

unfortunately there's not a whole bunch we can do without Google fixing the schema, but if you could open an issue we'll take a look