Closed sekoban closed 5 months ago
Hi Sener,
I was taking a long vacation and just got back to write a reply, sorry for the delay.
You are absolutely correct, it appears that the OTC provider has changed the resource in accordance to the API changes they had around 6 months ago (https://github.com/opentelekomcloud/terraform-provider-opentelekomcloud/commit/56c0290d7ac48656bcab5115c262e3f82b415765) and it became effective for versions >=1.35.5 .
I will update the opentelekomcloud_identity_user_v3 resource and version constraints accordingly and make a release tonight.
Hope that it will solve the problem. Best, Can.
I tested the fixed version and while the ACME terraform provider can still be finicky with OTC DNS, it appears that the problem is fixed and I was able to obtain a wildcard cert.
Please keep in mind that we generally use and recommend cert-manager with HTTP challenge for CCE clusters that do not necessarily need the DNS challenge (e.g. for wildcard certs) since the ACME DNS via terraform has some considerable disadvantages.
Please give it a try with the latest release: v5.8.2
Best, Can.
Dear iits colleagues
Running the ACME example I get an error
default_project_id
inopentelekomcloud_identity_user_v3
(https://registry.terraform.io/providers/opentelekomcloud/opentelekomcloud/1.36.0/docs/resources/identity_user_v3)My code
Regards, Sener