Felix Luthman

Any updates on this? It is currently a blocker for my org, with a hacky workaround being the script below for the time being (essentially running the `helm pull` command...

> > Any updates on this? It is currently a blocker for my org, with a hacky workaround being the script below for the time being (essentially running the `helm...

> What about this? > > `No user exists for uid 1001` > > Maybe `git` or `ssh` have trouble figuring out which/where the current user's home directory is, which...

> @IvanZosimov I understand that the `DOTNET_INSTALL_DIR` can be altered. My original understanding was that this action was a Github owned action. I believe this living in the `Actions` Org...

Just to add to the convo above: Generating the cert directly in helm exacerbates the issue when working in a [GitOps](https://opengitops.dev/) manner with for example [ArgoCD](https://argo-cd.readthedocs.io/en/stable/) (see the image below)....

@ldhenry Thanks for the swift replies the last couple of days, it's been great! Yes I'm very confused on the matter as well, since I too have been using 2.13.x...

@ldhenry any update on this?

Hey @ldhenry. No issues, we found a workaround by using the GitHub releases in this repo directly instead.

@ldhenry the Terraform provider is an alternative that we are considering as well. Currently we're leaning towards either that, or to try and generate our own native Crossplane provider. Our...

For anyone interested how the experimentation went we figured out the following: * Maintaining an in-house provider ourselves proved to be too much work in the end, and the Crossplane...