headyj

Any news on that issue? It's quite an annoying job as we are still blocked with 4.3 version

For those who have the same problem, I finally found what was the problem. v2.4 introduced a new behaviour concerning variables in application specs, which is documented here: https://argo-cd.readthedocs.io/en/stable/user-guide/config-management-plugins/#environment, which...

@tiwarisanjay Basically I just added `ARGOCD_ENV_` in front of my existing variables. Example bellow for my `helm_args` variable: Before my plugin looked like that: ``` configManagementPlugins: | - name: my-plugin...

Any update on this PR? We also have a lot of components and this pagination force us to to hundreds of calls to retrieve them

/fresh I'm currently facing this issue with a terraform Workspace resource, which is generating terraform workspace name based on the metadata.name or the external-name annotation of the resource. Both of...

same here, seems that sometime the privateKey.pem is empty workaround of @universam1 is working, but I had to switch to another image (alpine) because rm command is not in the...

As with [this issue](https://github.com/kubernetes-sigs/aws-efs-csi-driver/issues/812), it seems on my side that rolling back to v2.4.3 is not sufficient, as some efs-csi-node pods were still having their memory usage growing endlessly (even...

I will not be able to test the memory leak issue, as it's basically breaking our environments. What I can see is despite the `Failed to create registration probe file`...

Actually, we are using this config for almost 3 years now, so I can assure you that the efs is not read only and writes are working on EFS drives....

Exact same issue here using terraform provider: ``` argocd_application.composer: Creating... ╷ │ Error: application test could not be created │ │ with argocd_application.composer, │ on application.tf line 1, in resource...