Skip to content
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

configuration of task execution user #7

Open
1 task
jesteria opened this issue Jan 17, 2023 · 0 comments
Open
1 task

configuration of task execution user #7

jesteria opened this issue Jan 17, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@jesteria
Copy link
Member

As a configurer of Fate, I should be able to specify the OS user under which scheduled tasks are executed.

In detail:

  • Task configuration's user key should allow interpolation, to support e.g.:

    user: "{{ env.TASK_USER }}"

And perhaps:

  • User configuration might also support a global default value in the defaults file.

  • Though unlikely, also conceivable that I might want introduced new identifiers to indicate an expression which must not be cast to string, say to allow a non-interpolating expression like:

    user: "{~ env.TASK_UID | int ~}"

Note:

  • subprocess.Popen(…, user=None, …): string is converted to UID and int is passed through. (And such keywords may be passed through plumbum.machines.local.LocalCommand.run_bg(user=…).)
    • A generic task helper property for such keywords might be named mods_.
    • (plumbum does offer local.as_user() [doc]; however, this appears thread-unsafe. Though this is not a current concern, perhaps better to use run_bg() keywords.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant