systemd_service: Support for the "machine" parameter

[jimmy-lt]

Summary

When trying to run systemd as another user, the following is advised:

- name: Run a user service when XDG_RUNTIME_DIR is not set on remote login
  ansible.builtin.systemd_service:
    name: myservice
    state: started
    scope: user
  environment:
    XDG_RUNTIME_DIR: "/run/user/{{ myuid }}"

However, this may not always work and can fail in various ways, typically:

Failed to connect to bus: Operation not permitted

Since systemd 248, the --machine option is available to to open a connection to the session bus of a specific user.

Issue Type

Feature Idea

Component Name

systemd_service

Additional Information

- name: Run from within a specific user session
  ansible.builtin.systemd_service:
    name: myservice
    state: started
    scope: user
    machine: myuser@.host

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibot]

Files identified in the description:

• lib/ansible/modules/systemd_service.py

If these files are incorrect, please update the component name section of the description or use the component bot command.

[konstruktoid]

Out of curiosity, wouldn't it be advised to use become_user as well, in order not to trigger the permission issue?

[jimmy-lt]

become_user does overcome the permission denied issue. The --machine option however provides better integration with systemd and simplifies the task definition (no become or environment required).