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

Select Status

RSS

logentries_ng (1) Versions 0.2.1

LWRP for Installing and managing Logentries.

Policyfile
Berkshelf
Knife
cookbook 'logentries_ng', '~> 0.2.1', :supermarket
cookbook 'logentries_ng', '~> 0.2.1'
knife supermarket install logentries_ng
knife supermarket download logentries_ng
README
Dependencies
Changelog
Quality 17%

logentries_ng

Description

LWRP for logentries

Requirements

Supported Platforms

The following platforms are supported by this cookbook, meaning that the recipes run on these platforms without error:

  • Ubuntu
  • Debian
  • Amazon Linux

Usage

Look in fixtures cookbook for usage examples

Notes

Logentries is split into two packages, logentries and logentries-daemon, the former contains the command-line tools and the latter is the reporting agent. Unfortunately, when you install the logentries-daemon package it immediately tries to start the agent and will fail if you haven't pre-configured your host settings; this is problematic in a Chef script, because we haven't had an opportunity to set things up yet.

To solve this problem, the commandline tools are installed immediately, then the logentries-daemon package will only be installed at the end of your chef run; it will be triggered by the use of any of the logentries definitions.

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

License

logentries_ng

Dependent cookbooks

apt >= 0.0.0
yum >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

0.2.1

  • Re-factor: move :follow action to subresource
  • Fix: error with duplicated logs
  • Add: testing that logs are not duplicated

0.2.0

  • Add :remove alias for :rm action
  • Add: integration tests for the cookbook
  • Modify: rewrite the definition to the LWRPs.

0.1.9

  • Add: test-kitchen setup

0.1.8

  • Add: restart logentries after adding new log

0.1.7

  • Add: Check that logentries service was installed before tring to restart/start it.

0.1.6

  • Add: test-kitchen config

0.1.5

  • Add: Debian linux support

Collaborator Number Metric
            

0.2.1 failed this metric

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

Contributing File Metric
            

0.2.1 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.2.1 failed this metric

FC064: Ensure issues_url is set in metadata: logentries_ng/metadata.rb:1
FC065: Ensure source_url is set in metadata: logentries_ng/metadata.rb:1
FC066: Ensure chef_version is set in metadata: logentries_ng/metadata.rb:1
Run with Foodcritic Version 16.3.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

No Binaries Metric
            

0.2.1 passed this metric

Testing File Metric
            

0.2.1 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.2.1 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 include a tag that matches this cookbook version number