Support forfiles.

[oremj]

Support for [email protected] files.

[nikicat]

👍

[jsdir]

👍

[skorfmann]

👍

[skorfmann]

Is there any workaround to pass arguments to the units file?

[bcwaldon]

@skorfmann Currently, no. I was hoping we could use the @ syntax without the unit deduplication, but something isn't working correctly:

$ cat foo\@1.service
[Service]
ExecStart=/usr/bin/echo foo %i
$ fleetctl start foo\@1.service
$ fleetctl list-units
UNIT        LOAD    ACTIVE  SUB DESC    MACHINE
[email protected]   -   -   -   -   -
$ systemctl status foo\@1.service
[email protected]
   Loaded: loaded (/run/systemd/system/[email protected]; enabled-runtime)
   Active: inactive (dead)

Mar 27 14:10:41 core-01 systemd[1]: Starting [email protected]...
Mar 27 14:10:41 core-01 systemd[1]: Started [email protected].
Mar 27 14:10:41 core-01 echo[3061]: foo 1

So fleet is getting as far as starting the units, but apparently there's an issue getting the state updates over DBus.

[skorfmann]

@bcwaldon thanks, however I'm looking more for the syntax @oremj was using:

fleetctl submit [email protected]
fleetctl start [email protected]
open [email protected]: no such file or directory

Here's my use-case:

I'm going to build and tag a docker container with the short-ref of a git commit.

docker build -t bar/foo:48bd4b3 .

I want to pass this git ref to the unit file as argument like this:

fleetctl start [email protected]

This works with systemd. However, when I can't get this to work I would just fallback to generate & submit new unit files on each deployment.

Other ideas?

[bcwaldon]

@skorfmann I understand what you're looking for. Trust me, I want it to. I was trying to illustrate what I had hoped was possible today.

[skorfmann]

I was trying to illustrate what I had hoped was possible today.

Oh, alright then :)

[bcwaldon]

Working on this here: #244

[bcwaldon]

Closed in favor of #303