Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Extract loggly::rsyslog::logfile #11
Open
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Are you guys cool with me extracting this class into an independent module? Where I work we're configuring all of our servers with a basic loggly configuration that is baked into a base image. People who use the baked image can further configure rsyslog with infiles that rsyslog will watch and, because of the base configurations they've inherited, those files will end up in loggly.
What we've got now is this requirement to define the loggly puppet module as a dependency for our downstream server puppetry just so we can have access to loggly::rsyslog::logfile. With this dependency comes the requirement of setting the toke yet again (once in the base image, once in the images inheriting from base). Since loggly::rsyslog::logfile is fairly stand-alone as is and could possibly be used for things outside of loggly configurations, I thought it might be good to extract it.
What do you think? Btw, I'm probably going to do it anyway and us it internally where I work, but I wanted to get your thoughts and its usefullness outside my company.