treydock
treydock
So one reason we have never made these options, is security. We do NOT want OnDemand acting to enforce permissions or access, we rely on other things to do that...
See my comment in Discourse, there is a way to make the "Connect to " go away, we had to implement that change to avoid jobs thinking they could SSH...
Looks like the link I gave plus that Files App Singleton would combine to solve the issue. I'll pass on the documentation link via Discourse. https://osc.github.io/ood-documentation/latest/reference/files/ondemand-d-ymls.html?highlight=files_enable_shell_button
The interactive session was not deleted. I tried a second time and was successful. This was done while trying to reproduce maintenance page issues brought up on discourse so the...
Commits squashed
@chipzoller See https://kubernetes.slack.com/archives/CLGR9BJU9/p1661500830680979, TLDR Set `fullnameOverride` and leave `nameOverride` empty. I'll need to look closer why this is the case.
Not that I'm aware of
I am fairly certain a directory like `/var/www/ood/apps/sys/dashboard/wiki` will persist through RPM upgrades but might get deleted during uninstall or saved with `.rpmsave` suffix.
The environment available to any part of the Ruby code for OnDemand is going to be dictated by nginx_stage as that tool will strip the environment before launching the PUN...
So one possibly ugly solution would be to create some kind of wrapper script that initializes a login environment and just spits out the desired path and call that script...