stackablectl has hard coded temporary file paths, which cause concurrent operation to fail

[pipern]

I ran stackablectl as one user, and then later as another user, and found that it leaves (maybe only when overall the operation failed) files in /tmp, which then causes subsequent invocations of stackablectl to fail if the owner of these files/folders is different:

panic: open /tmp/.helmcache/stackable-stable-index.yaml: permission denied

panic: open /tmp/.helmrepo: permission denied

Might it be that stackablectl can instead use unique filenames for these temporary files?

[sbernauer]

Hi @pipern sorry for not responding so long, i just saw your issue. I set up a notification for the future.
stackablectl itself does not create these files, that's helm that we internally use to install the operators.
These files are meant for keeping an index of available helm-charts not as intermediate results. They are used across multiple helm calls. You can think of them like a maven cache or something similar.
I searched out a little bit and found out there is a env var HELM_REPOSITORY_CACHE (see https://helm.sh/docs/helm/helm/)

I fear there is not much stackablectl can do here, as this is a helm functionality.
Does using the HELM_REPOSITORY_CACHE setting work for you?

[lfrancke]

We are going to close this issue for now as we've migrated to https://github.com/stackabletech/stackable-cockpit/

If this is still an issue please feel free to open a new issue over there.