terraform-provider-multy VS gradle-orb

You can use it through a Terraform provider right now. If you're interested, you can get an API key at https://multy.dev, we'd love to get some feedback!

No problem. I'm also quite familiar with implementing a terraform provider so let me know if you need help around that or you can take some examples from https://github.com/multycloud/terraform-provider-multy

Our main repository is https://github.com/multycloud/multy and we also have a terraform provider at https://github.com/multycloud/terraform-provider-multy.

Thanks for reading the post, I’ve really come to prefer the type safety of protobufs and gRPC and it’s made developing Multy all the easier. If you want to look at a real world example of gRPC, take a look at the Multy engine running the gRPC server and a client example in our terraform provider.

Take a look at multy.dev and let us know what you think! Specifically our kubernetes cluster resource might be interesting for you: https://registry.terraform.io/providers/multycloud/multy/latest/docs/resources/kubernetes_cluster

We have a discord channel where we're starting to build a community of developers. Our two main repos are the engine and our Terraform provider. Have a browse and tells us what you think!

Me and a few friends have been working on multy.dev, an open-source[1] cloud agnostic API that makes it easy to deploy the same infrastructure to any cloud provider using native managed services.

Improved upon CircleCI's default Gradle and Maven artifact caching with custom orbs (Gradle / Maven). Load on artifact store is reduced by like 10x, build time is reduced and more predictable.