it works , the file is mounted but when i deploy it i go this error
{“timestamp”:“2022-05-23 12:00:50.372 Z”,“level”:“error”,“msg”:“Unable to move plugin from temporary directory to final destination. Another plugin may be using the same directory name.”,“caller”:“web/context.go:105”,“path”:“/api/v4/plugins/marketplace”,“request_id”:“53rw596ctpf3pqrqpqhfqu1gha”,“ip_addr”:",“user_id”:“jei45ycqufr55gd7usqknyyoio”,“method”:“POST”,“err_where”:“installExtractedPlugin”,“http_code”:500,“err_details”:“destination already exists”}
Hi @sarce666, thanks for bringing this to our attention! I checked with some of our engineers (here’s the conversation) and this appears to be a known problem, and isn’t something we have plans to support.
However, you should be able to work around this issue with mmctl which has a config command to get and set configurations for Mattermost and any plugins you have installed.
For example, you can use the command mmctl config get PluginSettings.Plugins.com.mattermost.welcomebot to get welcomebot’s current configuration and change “get” to “set” to modify it. Here’s some more info about the config command.
but how to sent this command in the first installation yaml file:
apiVersion: installation.mattermost.com/v1beta1
kind: Mattermost
command is not recognize there
If I understand your question, you’re asking how to do this when you first install Mattermost? If so, you should be able to do it by installing mmctl to any host that is capable of communicating with your Kubernetes cluster. You can then trigger the mmctl command manually or automate it with a bash script or something similar.
this is a bit what i though , but i would prefer an automate possibilities in the deployment
that means if i redeploy or one of my pods restart i lose everyhting and i have to do it manually
so i loose all the good point of kubernetes
or is there a way to have the the /mattermost/plugins in presistence mode so i keep it when restarting my pods
i dont see any options in the spec in the orchestrator either ?