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

<@U05Q2KFH60P> we generate these examples from the upstream provider, and that’s the only code provided.

it does seem to work though, you’ll just need to look at the inputs for spec

not sure i follow -- there is no `spec` in the example provided. looking at <https://github.com/pulumi/pulumi-gcp/blob/master/sdk/python/pulumi_gcp/gkehub/feature.py|the provider code>, i don't see any class i could conceivably offer as the `spec` to enable MCS.

<https://www.pulumi.com/registry/packages/gcp/api-docs/gkehub/feature/#spec_python>

This?

yeah -- <https://www.pulumi.com/registry/packages/gcp/api-docs/gkehub/feature/#featurespec|the >`FeatureSpecArgs`<https://www.pulumi.com/registry/packages/gcp/api-docs/gkehub/feature/#featurespec| docs> indicate that it can accept `fleetobservability` or `multiclusteringress` , but nothing for MCS. it says `spec` is optional, but in that case it's unclear to me how Pulumi determines that you want to enable MCS (and not, say, service mesh, which *also* has no spec). is `name` a magical field? i.e., do I need to use `gcp.gkehub.Feature("multi-cluster-services", ...)` (which is the name of the feature as used in the CLI)? if so that's certainly not indicated in the docs

ahhh sorry, now I understand. No, that might not be supported yet.

Maybe try this google native resource: <https://www.pulumi.com/registry/packages/google-native/api-docs/gkehub/v1alpha/feature/>

that might work? `feature_id` seems promising, at least