Christian Weber

Hi @sumitpurandare, the fix would need to come from the repository maintainers. As far as I can tell, the work isn't prioritized. My suggestion would be to fork the repository...

Is there a mechanism during the apply to retrieve the gossip key from the config file output, to share with other terrraform resources during the same run? From the feedback...

After digging around, here's an example of pulling the gossip key, looks like I may have swapped my json/base64 decoding. Oops! https://github.com/hashicorp/terraform-aws-hcp-consul/blob/80e714415874e11b949869b00691eeaa6dbd0791/examples/hcp-eks-demo/main.tf#L93 ```terraform gossip_encryption_key = jsondecode(base64decode(hcp_consul_cluster.main.consul_config_file))["encrypt"] ``` Examples like this...