Conor Mongey

@travisjeffery 👋 I had a look at implementing this [here](https://github.com/travisjeffery/jocko/compare/master...Mongey:master) but didn't get too far. The CommitLog can't currently delete a range, so the tests (that I copied from `raft-boltdb`)...

Thanks for reporting @BnMcG This is actually more of an issue with `terraform-provider-kafka`. I fixed the crash, but actually didn't fix the problem with supporting lazy-provider initiation😅

lazy initiation is needed to run provision the cluster and topic in one run, but, if break it into two different runs ... it should work. main.tf ```tf terraform {...

@Zico56 Can you post some logs with `TF_LOG=debug terraform apply` Thanks

`TF_LOG=debug terraform plan` for debug information. Sorry you're running into issues, I haven't really had a chance to give this provider much attention.

This is a know issue (#18) ... I have started to look at it in #37

@ryandutton Yeah I believe there's a similar issue with API Keys.... they aren't ready to be used immediately after creation. I'm experimenting with having the provider wait until the key...

There's so many caveats to the "wait for cluster to be healthy" (introduced in #37) feature -- that I think adding the ability to disable it, is a good idea....

@nbommu1 What version of the provider are you using? can you try `0.0.3`, it should fix this.

I think this is actually supported now 🤔 ```tf resource "confluentcloud_kafka_cluster" "test" { name = "provider-test" service_provider = "aws" region = "eu-west-1" availability = "LOW" environment_id = confluentcloud_environment.environment.id network_egress =...