log4j config needs update about puppet-rundeck HOT 5 CLOSED

@wcooley option 4 is also my preference. However, would a template override be the most straightforward way to do this?

from puppet-rundeck.

@jyaworski The template override would be the easiest, although I generally prefer to edit package-installed files rather than replace -- that way, if improvements are made upstream, you can get them automatically (depending on how they're packaged).

Rather than re-inventing log4j management, however, it might be worth looking into danielgil/log4j to see if it fits.

(When I first posted this, I was intending to implement this myself, but my role has changed at work making Puppet no longer my immediate duty, so I rescind that intention.)

from puppet-rundeck.

@wcooley all right. I'm not entirely familiar with log4j, but I think I can refactor it to produce the same output at the very least.

I agree with the use of an upstream module, but we need to find out what the most common log4j solution is. I'm hesitant to introduce dependencies when I don't need to.

I may look at this.

from puppet-rundeck.

Proposed solution: #161, @jyaworski , your solution I believe is more elegant, but this may be a bit less intrusive to address @liamjbennett 's concerns, even if it is an intermediate solution.

from puppet-rundeck.

thank y'all! i'll close this issue for now

from puppet-rundeck.