Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

RSS

remote_syslog2 (4) Versions 0.3.0

Installs/Configures remote_syslog2

Berkshelf/Librarian
Policyfile
Knife
cookbook 'remote_syslog2', '~> 0.3.0'
cookbook 'remote_syslog2', '~> 0.3.0', :supermarket
knife cookbook site install remote_syslog2
knife cookbook site download remote_syslog2
README
Dependencies
Changelog
Quality

remote_syslog2 cookbook

Installs and configures remote_syslog2

Requirements

Platforms

  • Ubuntu (tested using 14.04)

Attributes

remote_syslog2 runtime configuration

The main configuration of remote_syslog2 is done using a hash which mirrors the structure of the remote_syslog2 config yaml file...

node['remote_syslog2']['config'] = {
  files: [],
  exclude_files: [],
  exclude_patterns: [],
  hostname: node['hostname'],
  destination: {
    host: 'logs.papertrailapp.com',
    port: 12345
  }
}

Since this is rendered directly to YAML, you can theoretically configure any value which is normally configurable. For more information please reference the remote_syslog2 examples

Additional remote_syslog2 command line settings can be specfified in the extra_options attribute

node['remote_syslog2']['extra_options'] = '--facility=local6'

For the sake of clarity this cookbook saves the config file to /etc/remote_syslog2.yml rather than the normal /etc/log_files.yml by default

Note about updates

As of version 0.3.0 of this cookbook the binary for remote_syslog2 will include the binary's version number after it - for example "/usr/local/bin/remote_syslog_0.17". This is because remote_syslog2 has no command line flag to find out a binary's version, and this cookbook needs some way of detecting old versions that need to be updated. If you are directly using this binary outside of chef, you will need to make sure you're using the correctly updated binary path.

Recipes

default

Include the default recipe in a run list to have remote_syslog2 installed and configured

install

Installs remote_syslog2

configure

Generates config file for remote_syslog2

service

Installs remote_syslog2 as an init.d service and starts/enables it

Usage

Generally all you have to do to use this cookbook is add the default recipe to your run_list and configure the node['remote_syslog2']['config'] hash.

License and Authors

Author:: Jeff Way (jeff.way@me.com)

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

remote_syslog2 Cookbook CHANGELOG

This file is used to list changes made in each version of the remote_syslog2 cookbook.

v0.3.0 (2016-05-02)

  • Add remote_syslog2 binary update functionality - see "Note about updates" in readme
  • Update remote_syslog binary version to 0.17 (Andy Thompson)
  • Allow configuration of command line options (Rudolf Vriend)
  • Fix generated config file on Chef 11.14 (Hendy Tanata)
  • Fix invalid config file when non-integer ports are specified
  • Add test for non-integer ports
  • Add chefignore

v0.2.3 (2014-11-13)

  • Fix service management not deleting pid file when stop is called

v0.2.2 (2014-11-13)

  • Fixed more places where "remote_syslog" was used rather than "remote_syslog2"

v0.2.1 (2014-11-10)

  • Change name of extract resource to be less generic
  • Have extract resource clean up temp files
  • Fix up some language in tests
  • Use direct file tests rather than ls in tests
  • Add tests for file cleanup

v0.2.0 (2014-11-09)

  • Update the project to more closely follow community standards
  • Install process now downloads/extracts a release directly from here
  • Configuration is now completely procedural
  • Renamed to remote_syslog2 for clarity since that's what Papertrail calls their repository even though they still call their binaries "remote_syslog"
  • Added BATS tests
  • Added better documentation
  • Changed init script to be a template so that some values in it can be dynamic

v0.1.0

  • Initial release of remote_syslog2

Collaborator Number Metric
            

0.3.0 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

0.3.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.3.0 failed this metric

FC064: Ensure issues_url is set in metadata: remote_syslog2/metadata.rb:1
FC065: Ensure source_url is set in metadata: remote_syslog2/metadata.rb:1
FC066: Ensure chef_version is set in metadata: remote_syslog2/metadata.rb:1
FC069: Ensure standardized license defined in metadata: remote_syslog2/metadata.rb:1
Run with Foodcritic Version 11.1.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

0.3.0 passed this metric

No Binaries Metric
            

0.3.0 passed this metric

Publish Metric
            

0.3.0 passed this metric

Supported Platforms Metric
            

0.3.0 passed this metric

Testing File Metric
            

0.3.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.3.0 passed this metric