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

fedora-mock (2) Versions 0.1.0

Installs Fedora Mock

Policyfile
Berkshelf
Knife
cookbook 'fedora-mock', '= 0.1.0', :supermarket
cookbook 'fedora-mock', '= 0.1.0'
knife supermarket install fedora-mock
knife supermarket download fedora-mock
README
Dependencies
Changelog
Quality 0%

fedora-mock Cookbook

Build Status
Chef Cookbook

Installs Fedora Mock

Requirements

  • Chef 11 or higher
  • Ruby 1.9 or higher (preferably from the Chef full-stack installer)
  • Network accessible package repositories
  • Fedora Mock is only accessible on Fedora & RHEL platform families
  • yum-epel Cookbook (only executed on RHEL platforms families)

Attributes

fedora-mock::default

<table>
<tr>
<th>Key</th>
<th>Type</th>
<th>Description</th>
<th>Default</th>
</tr>
<tr>
<td><tt>['fedora-mock']['include-epel']</tt></td>
<td>Boolean</td>
<td>
Does this cookbook automatically include the EPEL respository?
</td>
<td><tt>true if a RHEL platform family; false if Fedora</tt></td>
</tr>
<tr>
<td><tt>['fedora-mock']['plugins']</tt></td>
<td>Hash</td>
<td>
Additional Fedora Mock plugins to install. The hash key is the plugin.
If the hash value evaluates to true, the plugin will be installed.
</td>
<td><tt>empty</tt></td>
</tr>
<tr>
<td><tt>['fedora-mock']['users']</tt></td>
<td>Hash</td>
<td>
Users of Fedora Mock. The hash key is the user. If the hash value
evaluates to true, the user will be a managed group of Fedora Mock.
</td>
<td><tt>empty</tt></td>
</tr>
</table>

Usage

fedora-mock::default

Just include fedora-mock in your node's run_list:

{
  "name":"my_node",
  "run_list": [
    "recipe[fedora-mock]"
  ]
}

Contributing

  1. Fork the repository on GitHub
  2. Create a named feature branch (like add_component_x)
  3. Write your change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using GitHub

Development Environment

This repository contains a Vagrantfile which can be used to spin up a
fully configured development environment in Vagrant.

Vagrant requires the following:
* VirtualBox
* Vagrant

The Vagrant environment for this repository is based on:
* st-isidore-de-seville/trusty64-rvm-docker

The Vagrant environment will initialize itself to:
* install required Ruby gems
* run integration testing via kitchen-docker when calling kitchen

The Vagrant environment can be spun up by performing the following commands:

  1. vagrant up
  2. vagrant ssh
  3. cd /vagrant

Authors

License

The MIT License (MIT)

Copyright (c) 2015 St. Isidore de Seville (st.isidore.de.seville@gmail.com)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Dependent cookbooks

yum-epel ~> 0.6.2

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

fedora-mock CHANGELOG

This file is used to list changes made in each version of the fedora-mock
cookbook.

0.1.0


Check the Markdown Syntax Guide
for help with Markdown.

The GitHub Flavored Markdown page
describes the differences between markdown on GitHub and standard markdown.

Foodcritic Metric
            

0.1.0 failed this metric

FC031: Cookbook without metadata file: /tmp/cook/7d2c55e470a54adcfc822a09/fedora-mock/metadata.rb:1
FC045: Consider setting cookbook name in metadata: /tmp/cook/7d2c55e470a54adcfc822a09/fedora-mock/metadata.rb:1