hi @limited-rainbow-51650 👋, thanks so much for your recent PR to Pulumi Zitadel! currently, pulumi zitadel is not very usable: it lacks support for some critical apis, and there have been a lot of changes in their terraform provider. for example, the smtp configuration in pulumi doesn’t support

set_active

, while the terraform provider does. i understand that pulumi universe is a community-driven effort, but unfortunately, i don’t have the expertise or capacity to contribute to pulumi zitadel at this time. that said, as you mentioned in the PR: > more automation in place to make almost synchronous releases when you create new Terraform provider releases this sounds really promising. I wonder what the roadmap is and how eventually the synchronization process will be in the future?

The people from Zitadel are involved in this effort. I will make sure they know how all the automations work.

🙏

@bored-monitor-99026 a PR contributing a fix for that TF issue would be golden!

hi Ringo, what's the following steps after that issue is resolved? could you expand a bit more on how such almost synchronized release between terraform and pulumi provider would work?

@bored-monitor-99026 the

upgrade-provider

workflow normally checks daily if there are newer TF provider releases and would automatically prepare a pull request taking the new version in. For newer TF releases within the same major version, this all becomes quite automatic. There might be some manual work to cover breaking changes done in a new major release of the upstream TF provider. At the moment, given this upstream problem, I disabled this daily check: https://github.com/pulumiverse/pulumi-zitadel/commit/0094d02653563e66722a34694624ac3388520cf6

thanks for the info! i will keep you posted once that issue is resolved.