<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - RFE: EnvironmentExecutable= or EnvironmentOneshot= that provides environment"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=85709">85709</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>RFE: EnvironmentExecutable= or EnvironmentOneshot= that provides environment
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>systemd
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>general
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>rektide@voodoowarez.com
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>This is rapidly becoming standard practice in container-land- a program which
provides Environment for another. This should be supported directly in systemd,
rather than requiring each project to cobble together their own executable
wrapper.

Programs doing this themselves:

<a href="https://github.com/kelseyhightower/confd">https://github.com/kelseyhightower/confd</a>
<a href="https://github.com/hashicorp/envconsul">https://github.com/hashicorp/envconsul</a>
<a href="https://github.com/mattn/etcdenv">https://github.com/mattn/etcdenv</a>
<a href="https://github.com/GoogleCloudPlatform/kubernetes/issues/2068">https://github.com/GoogleCloudPlatform/kubernetes/issues/2068</a>

The actual format suggested- an EnvironmentExecutable- is completely
negotiable, it merely seemed to be the simplest option to me.

Far more interestingly, perhaps an EnvironmentOneshot could specify a oneshot
service whose stdout could be used. This would, to me, be far more complete, as
it solves the question of what execution environment to frame the execution
environment generator in and allows for all the levels of stupidly recursive
one could ever dream.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>