Disabling metron's syslog config doesn't remove the conf file
wfernandes opened this issue · comments
Thanks for your submission!
Here are some guidance for submitting your issue.
Tell us why you are submitting?
- I found a bug - here are some steps to recreate it.
- I have an idea for a new feature - please document as "As a user, I would
like to..." - I am having trouble getting setup, understanding documentation, or using
Loggregator in some way - please highlight any resources you are using. - This is an architecture change that will result in cleaner more efficient
code - Tell us why you think this is a good idea.
We review issues and PR's on a weekly basis and try to schedule and prioritize
items. If you are wondering about status of an item feel free to contact us on
our slack channel.
When we disable the syslog_daemon_config.enable flag it doesn't remove /etc/rsyslog.d/00-syslog_forwarder.conf file and restarting the rsyslog service.
This is similar to this issue on syslog-release.
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/152092044
The labels on this github issue will be updated when the story is started.
Loggregator has cut ties with rsyslog and therefore do not want to add any additional "opinions" about how rsyslog is configured. I think rsyslog-release should be more opinionated about how it is configured and could take responsibility for cleaning up old configs. This would prevent Loggregator from stepping on any toes as rsyslog moves forward.