Hi from the other terraform-provider-keycloak about terraform-provider-keycloak HOT 3 CLOSED

Hi @phillipj. I did see that provider in my initial search for a Keycloak provider. I ended up starting my own repo instead of contributing to that one after seeing tazjin/terraform-provider-keycloak#24, where the owner said they weren't maintaining that project.

I'd be happy to have more contributors to this project 😄 please feel free to submit issues or PRs for anything you'd like to see added or changed.

The company I work at uses this provider in production, and it's been working well for us. I'll probably be adding new resources in the coming weeks as we continue to use other features of Keycloak.

from terraform-provider-keycloak.

Sounds great, appreciate the quick response! I definitively understand your initial concerns as you described in #34 that made you create a new provider project instead 👍

I'd love if we could collaborate on creating one good Keycloak provider, rather than developing two different providers with the same intention in parallel. Surely will give this provider a shot at work as it seems to have more resources mapped already and better quality overall (ref tests).

I'll get back with an update on how that turned out within a couple of weeks or so. Closing this issue in the meantime.

from terraform-provider-keycloak.

Just wanted to close this properly instead of leaving it here without no visible progress or us contributing to the project.

After a long process internally at work, we've decided to transition from using a self-hosted Keycloak solution to a managed alternative.

Long story short, we've have a handful of challenges scaling Keycloak properly and generally running it as a cluster inside Kubernetes. We don't have enough developers on our team that we can spend the amount of time we have done on keeping such a critical piece of infrastructure working flawlessly at all times.

from terraform-provider-keycloak.