Andy Roth
More possible suggestions: * Implement different log levels such as DEBUG, TRACE, ERROR, WARNING, etc, and only log that data if the log level is set to debug+ * Modify...
Happy to submit a PR for this if any of these suggestions gains traction.
It's pretty hacky but we wrote up this and it seems to work. Still testing. Still would prefer for the module to handle this itself rather than backdooring it. ```...
correct, we have the above code in our root module, next to our `module "eks"` block
It should handle checking that the EKS cluster is ready to accept connections before it tries to do stuff with it. the above code is an ugly hack to get...
This very module used to do it 2 different ways. Most recently it did it using the HTTP Provider: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/v17.24.0/data.tf#L92 Or by using a null_resource: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/v15.2.0/cluster.tf#L67 EKS Blueprints uses the...
> Got it. Let's chat about this again in about a month 😬 Any update?
What changes?
I don't love being kept in the dark. Is there any nugget of insight you can give as to what is coming?