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

Right now cutting a new release is a manual action - and we weren’t consistent about the cadence. Apologies for that - I’ll cut a new release today which will have the pipeline resource.

<@UB39JFCKC> do you know if it will also contain activating Anthos Service Mesh for a GKE cluster? E.g the counterpart of:
`gcloud beta container hub mesh enable --project=FLEET_PROJECT_ID`

<@U025LJGGJ1L> I’m getting some odd test failures in CI, the release slips to tomorrow unfortunately

<@UK4HNFLCB> do you know which API creates that resource?

Just went through the gcloud sdk with a debugger. It is a POST with body `{}` to
```<https://serviceusage.googleapis.com/v1/projects/>&lt;projectId&gt;/services/meshconfig.googleapis.com:enable?alt=json'```
For those who want to check it is on `lib/googlecloudsdk/command_lib/container/hub/features/base.py` method `Enable` of class `EnableCommand`
You can put a debug point there to get the entire stack :slightly_smiling_face:

<https://cloud.google.com/service-usage/docs/apis?hl=en>

~I'm not sure if the service management API has a intersection or if one enable products and the other features of those products~
Service Management has nothing to do with this

<@USC68LB3J> looking at that end point, that would mean that we have to activate `<http://meshconfig.googleapis.com|meshconfig.googleapis.com>` on our project. I think we can do that with the following:
• gcp classic provider: <https://www.pulumi.com/registry/packages/gcp/api-docs/projects/service/>
However, I can’t find the corresponding counterpart in the native provider.

FYI: I also googled if this was solved on TF side, bumped into <https://faun.pub/terraform-module-for-kubernetes-cluster-with-google-anthos-5f714ca3e6ff|this article> and navigating via the TF Registry for the `terraform-google-modules` ended up on <https://github.com/terraform-google-modules/terraform-google-project-factory/blob/master/modules/project_services/main.tf#L31-L37|this code snippet>.

It seems enabling services is not possible at the moment with the native provider.
I think given that it is generated from the resources on the APIs it makes sense that it would not support this feature as services do not follow the POST/DELETE same resource with a possible operation like the others.

Both creating and destroying a resource requires a POST, into different URLs and disabling allow some extra parameters

For reference, the classic uses terraform-bridge, so this is the implementation: <https://github.com/hashicorp/terraform-provider-google-beta/blob/master/google-beta/resource_google_project_service.go>

It can be automated, but it would be just for a single module, not sure if it is worth it or if it should be hand-made

But if it is implemented on the native provider I think it should expose the batchEnable and the batchDisable to allow atomic operations :slightly_smiling_face:

There is an issue for that on the provider: <https://github.com/pulumi/pulumi-google-native/issues/59>

The release has finally landed! Sorry for the delay.