Bojan Kalicanin

Is it possible in the current implementation of `self_managed_node_groups` to define `desired_size`? I haven't seen it, just `min_size` and `max_size`.

Just for the record. Additional warning: Warning: Redundant ignore_changes element │ │ on .terraform/modules/eks.aws_eks/main.tf line 298, in resource "aws_eks_addon" "this": │ 298: resource "aws_eks_addon" "this" {

Will this see light of the day in new release? This is very important, as there are oportunity to refine alerting strategy instead of enforcing the workflow pattern by simple...

I am experiencing the same error in newrelic provider version `2.46.2`

Just an update on this. This happens only when you use `count` or `for_each` on the resource (creating multiple `newrelic_entity_tags resources`). Apparently, creating multiple tags using a single `newrelic_entity_tags` resource...

I have a similar folder structure in the `live/` dir with multiple levels of `terragrunt.hcl` files. The issue was that my higher level `.hcl` file was not named `terragrunt.hcl`, instead...

As I can see this issue is mostly happening with Apple Silicon M1&M2. As I may see it is because of `.terraform.lock.hcl` does not contain provider selection for the target...

I know you do not have intention of supporting additional registries, but it would be great if you start support OCI compliant registries which are easily becoming standard for registries,...

Will this be implemented in the near future?

+1 This is very important feature, as it is crucial when enabling external checks. It should be given higher priority. Also check if feasible implementation of support for [EKS Pod...