KsqlDB app creation with terraform ? about terraform-provider-confluent HOT 11 CLOSED

We've just released version 1.3.0 of TF Provider where we added new

• confluent_ksql_cluster resource
• confluent_ksql_cluster data source

in an Open Preview lifecycle stage.

We're very excited to hear your feedback about it!

cc @tfindlay-au @SebaLG @sourabhkrishna @mattyev87 @ssemyonov @javiervelamindcurv @AlexVasiukov @simonschmidt @miguelaferreira @de1et3d

from terraform-provider-confluent.

This worked perfectly for me. It does take time to provision KSQL, in my case Terraform took 9m29s

module.ksql_cluster.confluent_ksql_cluster.ksql-cluster: Creation complete after 9m29s [id=lksqlc-12o5zj]

... but aside from the time, it works perfectly. Thank you so much.

from terraform-provider-confluent.

Thanks for opening an issue @sourabhkrishna!

It's in our future plan but we don't have any details yet.

from terraform-provider-confluent.

Any details about it? Thanks!

from terraform-provider-confluent.

So excited for this. I'm happy to build the provider from source and beta test anything.

from terraform-provider-confluent.

@tfindlay-au would you be open to sharing more about your use cases and why the KSQL resource is important for you? Would love to have a discussion on our community slack channel:
https://confluentcommunity.slack.com/archives/C02JJ23HZD3

from terraform-provider-confluent.

Just one thought - after creation, there seems to be no data block/output variable to determine the cluster endpoint ?
eg. https://pksqlc-d0gw1.ap-southeast-2.aws.confluent.cloud

This does appear in the state file as http_endpoint, but does not seem to be available to use ?

  "instances": [
    {
      "schema_version": 0,
      "attributes": {
        "api_version": "ksqldbcm/v2",
        "credential_identity": [
          {
            "id": "sa-<account>>"
          }
        ],
        "csu": 1,
        "display_name": "InputToOutput",
        "environment": [
          {
            "id": "env-<environment>"
          }
        ],
        "http_endpoint": "https://pksqlc-d0gw1.ap-southeast-2.aws.confluent.cloud:443",
        "id": "lksqlc-81jj3m",
        "kafka_cluster": [
          {
            "id": "lkc-<cluster>"
          }
        ]
      }
    }
  ]

I think this might be useful to have available ?

from terraform-provider-confluent.

I'm not sure I got the question right. http_endpoint is a computed attribute:

that you can reference as confluent_ksql_cluster.example.http_endpoint or

output "foo" {
  value = confluent_ksql_cluster.example.http_endpoint
}

from terraform-provider-confluent.

cc @tfindlay-au

from terraform-provider-confluent.

Thanks for following up, I did see it in the documentation, but it just shows as red in IntelliJ, I think its just an IDE issue.

I confirmed the output is indeed populated when running in terraform.

from terraform-provider-confluent.

That's right, I don't think IntelliJ "recognizes" computed property by default 😕

from terraform-provider-confluent.