-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add staged_root to submit.yml.erb's rendering context #864
Comments
If staged_root is available we could also write the connection YAML in regular template ERB scripts like the regular HPC batch connect apps do. There is no need to use init containers since the main container can do it just the same if $HOME is mounted into the pod. |
Yea. #605 means that folks can't use In any case, yea I'm thinking we should fix #948 with a more simple change and pick up #605 at some other point. |
enable staged_root to be present in submit.yml.erb fixing #864
A discourse topic about error paths came in, and while folks are able to set
script.error_path
in their submit yml, they have no way of using the staged_root where everything else is.So my thinking is we may want to add
staged_root
to the app#submit_opts context's so that folks can do something like this in theirsubmit.yml.erb
.Incidentally - this is why the k8s adapter has to use a special way of passing back connection information. If the staged root is known up front in the
submit.yml.erb
then we may be able to write the connection.yml in an init container (if the $HOME directory is being mounted which is not a guarantee).The text was updated successfully, but these errors were encountered: