Closed ngapaillard closed 2 years ago
Thanks for reporting the issue @ngapaillard and sharing the root cause!
We'll address it in our next release.
Hi do you have any idea of the due date of the next release ? In order to anticipate in our side...
@ngapaillard I'd expect it to happen in about 2-3 weeks but can't promise anything.
@ngapaillard we're very excited to let you know we've just published a new version of TF Provider that includes a fix for this issue among other very exciting improvements: it enables fully automated provisioning of our key Kafka workflows (see the demo) with no more manual intervention and makes it our biggest and most impactful release.
The only gotcha we've renamed it from confluentinc/confluentcloud
to confluentinc/confluent
but we published a migration guide so it should be fairly straightforward. The existing confluentinc/confluentcloud
will be deprecated soon so we'd recommend switching as soon as possible.
New confluentinc/confluent
provider also includes a lot of sample configurations so you won't need to write them from scratch. You can find them here, find a full list of changes here.
Hi,
When using: data "confluentcloud_service_account" "service_accounts_confluent" and display_name on an existing sa name (verified with confluent cli). The provider doesn't find the sa. After having a look to the sources it seems the provider call the api that has a paginated result with 100 elements max by page... It seems in the provider the cursor of the pagination is not handled and search the service account only on the 100st service account.