Populate user email address in the forms from REMOTE_USER

[travert (Travis Ravert)]

@GKlouse

Is there a way I can pull the current user’s email address to automatically populate a field in the form.yml and submit.yml files for an interactive vnc submit?

I’m not entirely sure to be honest. There is a previous thread around some questions about how the emailing works, with a suggestion of how to set headers with this information in the cluster config here:

Global email setting

To verify, the goal is to set the email argument for each user, for each interactive app, in a single place. What resource manager are you using? Out of the box we don’t support this, but we have discussed adding support for this type of thing, as we would find it very useful as well. These are some related issues we have currently opened up: https://github.com/OSC/ood_core/issues/97 - want the ability to add default submission arguments in the cluster config for every job submitted through…

Which is a bit older and was linked form another conversation around getting emails for jobs here:

E-mail to user at job start,

There has been some discussion earlier on different sites implementing e-mail alerts when OOD jobs start, via the bc_email_on_started attribute. For the user to get the e-mail, the scheduler needs to also have the e-mail address of the user and turn on the option to feed in that e-mail (in SLURM –mail-user). I can put this in each app’s submit.yml.erb (e.g., in our case –mail-user=$USER@utah.edu), but, given the amount of apps we have it’d be easier if this could be a global option for all jobs…

In short, I’m not sure of a way to pull this to populate the form and submit unless you can glean something from those posts.