Garry

+1 for this. Trying to set up a dedicated cluster with VPC peering but can't do it with the provider yet.

I can provide `sku = "DEDICATED"` and that works, but the cluster is set to be public and that is an immutable property once the cluster is created. I want...

I guess the TF provider isn't yet implementing the `ClusterDeploymentNetworkAccess` struct? https://github.com/cgroschupp/go-client-confluent-cloud/blob/master/confluentcloud/cluster.go#L36-L41

> Is there any workaround in the meantime while the PR is merged & released? Workaround is just to set the version of the provider, so as not to use...

Can confirm, we're using `4.22.0` and the branch protection error doesn't appear.

+1 I'd love to use Argo Tunnel to expose the UI for Hashicorp Vault, but it's failing due to HTTPS.

Is the intention that it runs once, on initial setup, but then not again on future helm upgrades? In which case, wouldn't the `post-install` helm hook be a better fit...

Have raised a PR with the fix: https://github.com/mastodon/mastodon/pull/20690

From my understanding, adding a hook means that the ConfigMap will be removed once the helm install completes? https://helm.sh/docs/topics/charts_hooks/#hook-deletion-policies In which case, either we need to pass everything the Job...

Are you sure that your Laravel Horizon process is running and processing all of the queues?