Feature Request: ARGs should be able to be specified even if there is a template with blanks

[eloyd]

Imagine a command (call it check_eric) that does this:

Code: Select all

$USER1$/check_dummy $ARG1 $ARG2

Now imagine a service template (call it st_eric) that does this:

Code: Select all

command: check_eric
ARG1: 0
ARG2: <blank>

Lastly, imagine a service that:

Code: Select all

use st_eric
ARG1: <blank>
ARG2: This is my ARG2

ARG2 from the service will never be used because ARG2 from the template is blank. So even though a "more specific" setting is in the service description, it is ignored because it's using a template. This is not consistent with other template settings. We'd like to see the arguments (or the command, actually) allowed to be overridden at the service level even if a template has some of them specified. This would make for a much more powerful templating system.

[lgute]

Hi @eloyd, thanks for reaching out.

I created a feature request for this change.

I agree that it makes sense for values set higher up the inheritance chain (the "more specific"), to override inherited values (or lack there of).

[eloyd]

Groovy. Thanks. We're inching one step closer to me having just one service with a billion options on it to monitor everything!!

[lgute]

Hi @eloyd,

For the sake of tracking, the Github Issue is 986 and internally it is 1286, so it will show up in the XI Changelog as [GL:XI#1268].