Open MasinAD opened 1 month ago
Is there an explicit list which settings do support specifiers? All I could find is
Many settings resolve specifiers which may be used to write generic unit files referring to runtime or unit parameters that are replaced when the unit files are loaded. Specifiers must be known and resolvable for the setting to be valid.
@TheMeier I asked in the systemd IRC channel yesterday but all they came up with was something along the lines of "specifiers are allowed everywhere, maybe not where boolean values are expected". I think integer values might also use some special handling as there are specifiers for integers, e.g. %U for user ID, %G for user GID. But I assume it's safe to say their use is limited to a handful of options that expect integer values. Everywhere where strings are expected, they don't cause trouble.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
I see the puppet agent reporting the server complaining about not being able to compile the catalog for the client because
ConditionPathExists
doesn't match the configured type.What behaviour did you expect instead
Basically, I want the module to support what systemd itself supports, i.e. to accept specifiers where specifiers are allowed. I worked around the type definition of
by changing it to
Output log
Before my hack
After my hack
Any additional information you'd like to impart
I haven't mentioned the other attributes but there are several with similar limitations.