Chanwit Kaewkasi
Chanwit Kaewkasi
Thank you so much @dfreilich !! I'll improve the docs per your suggestions.
Thank you @onedr0p Sorry for the late reply. We'll take a look at this issue shortly.
Hi @marcobarducci Yep, that's the behaviour of Kustomization controller. Please annotate your certain Terraform objects with `kustomize.toolkit.fluxcd.io/substitute: disabled` to avoid substitution. https://fluxcd.io/flux/components/kustomize/kustomization/#variable-substitution
> but why? i could have the need to give some variables in input and grab others from a module. You can also use `$$` to escape the $. Please...
Hi @davidblaisonneau-orange thank you for reporting this. We're aware of this kind of behavior. Adding finalizers to ConfigMaps or Secrets which are not managed by the controller would cause other...
It's from the discussion with the Flux team. They suggested that adding finalizers to those objects would lead to some unforeseen behaviors, for example, it would block the uninstallation process...
Thank you @marcobarducci for reporting this. Could you describe this problem in more details please? Would be great to have steps to reproduce the problem.
I see. Thanks for the input. I'll take a look at it shortly.
> similar problem happens when working with branch planner. > since branch planner creates new flux - GitRepository whenever a PR is created and then creates terraform object. > it...
@hmonsalv thank you for this PR. Would you like to try adding a new field to the CR? Maybe like this: ```yaml kind: Terraform spec: upgrade: false # default to...