Differences

This shows you the differences between two versions of the page.

--- devops:ansible [2018/10/18 10:29] – [Importing and Including] skipidar
+++ devops:ansible [2023/11/01 07:15] (current) – ↷ Page moved from camunda:devops:ansible to devops:ansible skipidar
@@ Line 398: / Line 398: @@
 ==== Read remote files ====
+To read remote file do use slurp
 <code>
@@ Line 419: / Line 421: @@
 </code>
+==== Execute a shell script, as a user with a valid environment ====
+Sometimes you face the issues, that the environment variables defined by some tool, installed for a special user - are not defined, when you execute the tool.
+To execute some installed software in a valid environment, \\
+with /home/bashrc \\
+with /etc/profile.d \\
+etc
+use the following approach.
+<code>
+      # unfortunately the environment defined by tool in /etc/profile.d - is not taken up by ansible. Explicitely requesting the interactive shell is necessary here
+      - name: processing step
+        shell:
+          sudo -iu ubuntu yourtool.sh   > /tmp/logs/yourtool.log 2>&1
+        args:
+          executable: /bin/bash
+       -i [command]
+                   The -i (simulate initial login) option runs the shell specified in the passwd(5) entry of the target user as a login shell.  This means that login-specific
+                   resource files such as .profile or .login will be read by the shell.  If a command is specified, it is passed to the shell for execution.  Otherwise, an
+                   interactive shell is executed.  sudo attempts to change to that user's home directory before running the shell.  It also initializes the environment, leaving
+                   DISPLAY and TERM unchanged, setting HOME, MAIL, SHELL, USER, LOGNAME, and PATH, as well as the contents of /etc/environment on Linux and AIX systems.  All other
+                   environment variables are removed.
+</code>
+See https://github.com/ansible/ansible/issues/4854
+UNfortunately the aproach with become_user - does not have the same result