After reading through the code of Kustomize and this plugin here, I found it hard to find a reason why the binary plugins hidden behind the --enable-alpha-plugins should be hidden. Any pointers to a rationale would be highly welcomed.
Yet when this didn't work, I built my own fork of this with the following patch:
The output of terraform init right after make build could also be implanted into a third-party repository's lock file, and together with a little correction in versions.tf (where the provider was defined) and manual dropping of the newly generated binary into the 1.0.0 folder even allowed for the custom provider to run.
Until I saw that the code path that I had copied from the enable_helm feature is already available there.
So the secret way to --enable-alpha-plugins is to merely use enable_helm = true, which works fine with KSOPS and also SopsSecretsGenerator.
*g*
This way we can manage Kustomizations from Terraform, and from ArgoCD, which is nice.
After reading through the code of Kustomize and this plugin here, I found it hard to find a reason why the binary plugins hidden behind the
--enable-alpha-plugins
should be hidden. Any pointers to a rationale would be highly welcomed.Yet when this didn't work, I built my own fork of this with the following patch:
The output of
terraform init
right aftermake build
could also be implanted into a third-party repository's lock file, and together with a little correction inversions.tf
(where the provider was defined) and manual dropping of the newly generated binary into the1.0.0
folder even allowed for the custom provider to run.Until I saw that the code path that I had copied from the
enable_helm
feature is already available there.So the secret way to
--enable-alpha-plugins
is to merely useenable_helm = true
, which works fine with KSOPS and also SopsSecretsGenerator.*g*
This way we can manage Kustomizations from Terraform, and from ArgoCD, which is nice.