iurii.pro

> Hi @iuriipro, > we encountered the same issue. The problem is, that the generated kubernetes resources of `data.flux_install` include the flux-system namespace. This isn't necessary, because the namespace is...

> @iuriipro Terraform should not remove the namespace when updating the version of Flux. Could you please post the version of the provider you are using and the specific HCL...

@phillebaba Could you please clarify, did you faced with this issue, when using flux terraform provider with version 0.0.11? ``` Error: Invalid for_each argument on ../../modules/flux_v2/main.tf line 60, in resource...

@phillebaba Thank you. I understand that it is just terraform core error and behavior of "for_each", but I am following by example from the documentation. ``` data "flux_install" "main" {...

> Could you follow this guide and see if you get the same issues? > https://registry.terraform.io/providers/fluxcd/flux/latest/docs/guides/github @phillebaba Thank you, I have tried it before, will try one more time, but...

@phillebaba have tried it, doesn't work. Have you any suggestions? Or need to try 0.0.10?https://www.terraform.io/docs/language/meta-arguments/for_each.html#limitations-on-values-used-in-for_each

> I dont understand? I ran the guide from a clean state right now without any issues, I even tested it with Terraform 0.13 to make sure that was not...

@phillebaba Found that usage of depends_on from some module in the flux_v2 module section caused the issue. Now after the last retry, version 0.0.11 works fine and looks good for...

@linuxbsdfreak Hi, could you please clarify, what issue do you have? For the first look, your config is ok.

> I also had problem with namespace being stuck terminated, after all other resources were destroyed by Terraform, namespace was stuck, I solved by removing the only finalizer in list:...