Feature request: initialize ZITADEL instance from scratch without human interaction about terraform-provider-zitadel

[DavideWalder]

Let me know if a discussion is more appropriate (instead of an issue)

[fforootd]

Thank you for raising this.

To some degree we can already start zitadel in a reproducible fashion with docker compose or something similar. We do this in our e2e GitHub action pipeline.

But I think we should discuss this further. I will try to get my head around this, this week.

[DavideWalder]

Thank you for raising this.

To some degree we can already start zitadel in a reproducible fashion with docker compose or something similar. We do this in our e2e GitHub action pipeline.

But I think we should discuss this further. I will try to get my head around this, this week.

I had a look at it, from what I understood it uses Cypress to get over the initial login and password change. I opted for not using that setup simply because it would need to have one container running Cypress and one running Terraform after that.

I saw in the documentation that it is possible to pass the public key a the system API user in the configuration. I could be useful to have the same thing for an admin machine user having the same permissions as the initial human user. Basically rendering the GUI completely optional.

[stebenz]

At least functionality to create instance level resources is already planned in #5, but I think even this is not fully automated as some credentials have to be provided anyway, I will have to have a look at it again afterward.

[stebenz]

@DavideWalder The functionality to create an instance through zitadel-go is resolved.

But there are several other things unfortunately missing, but not on the side of the terraform provider but ZITADEL directly, planned for sometime in the future but I'm not sure when exactly, do you have any direct need for this functionality right now? Like is it a blocker for you until this issue is resolved?

[DavideWalder]

This is only a blocker for CI pipeline (automated integration tests) and containerized local development, but not for production use.

[hifabienne]

Similar to #13

[stebenz]

Functionality is provided on ZITADEL side as documented here will close this issue for the time being, if any question arise please open it again.