This feature adds the Terraform resources zitadel_org_metadata and zitadel_user_metadata.
One resource instance manages exactly one metadata key-value pair in ZITADEL. This enables having some keys managed by Terraform and others outside of Terraform.
If the value for the key or the user_id property changes, the old key-value pair is deleted and a new key-value pair is created.
Closes #29
Closes #132
Definition of Ready
[x] Short description of the feature/issue is added in the pr description
[x] PR is linked to the corresponding user story
[x] Acceptance criteria are met
[x] All open todos and follow ups are defined in a new ticket and justified
[x] Deviations from the acceptance criteria and design are agreed with the PO and documented.
[x] No debug or dead code
[x] My code has no repetitions
[x] All non-functional requirements are met
[x] The generic lifecycle acceptance test passes for affected resources.
[x] Examples are up-to-date and meaningful. The provider version is incremented.
This feature adds the Terraform resources zitadel_org_metadata and zitadel_user_metadata. One resource instance manages exactly one metadata key-value pair in ZITADEL. This enables having some keys managed by Terraform and others outside of Terraform. If the value for the key or the user_id property changes, the old key-value pair is deleted and a new key-value pair is created.
Closes #29 Closes #132
Definition of Ready