ridley 0.0.1

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/.travis.yml

@@ -0,0 +1,5 @@
+script: "bundle exec thor spec:unit"
+language: ruby
+rvm:
+  - 1.9.2
+  - 1.9.3

data/Gemfile

@@ -0,0 +1,3 @@
+source 'https://rubygems.org'
+
+gemspec

data/Guardfile

@@ -0,0 +1,20 @@
+guard 'spork' do
+  watch('Gemfile')
+  watch('spec/spec_helper.rb')     { :rspec }
+  watch(%r{^spec/support/.+\.rb$}) { :rspec }
+end
+
+guard 'yard', stdout: '/dev/null', stderr: '/dev/null' do
+  watch(%r{app/.+\.rb})
+  watch(%r{lib/.+\.rb})
+  watch(%r{ext/.+\.c})
+end
+
+guard 'rspec', version: 2, cli: "--color --drb --format Fuubar", all_on_start: false, all_after_pass: false, notification: false do
+  watch(%r{^spec/unit/.+_spec\.rb$})
+  watch(%r{^spec/acceptance/.+_spec\.rb$})
+  
+  watch(%r{^lib/(.+)\.rb$})          { |m| "spec/unit/#{m[1]}_spec.rb" }
+  watch('spec/spec_helper.rb')       { "spec" }
+  watch(%r{^spec/support/.+\.rb$})   { "spec" }
+end

data/LICENSE

@@ -0,0 +1,201 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright 2012, Jamie Winsor
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/README.md

@@ -0,0 +1,273 @@
+# Ridley
+[![Build Status](https://secure.travis-ci.org/reset/ridley.png?branch=master)](http://travis-ci.org/reset/ridley)
+[![Code Climate](https://codeclimate.com/badge.png)](https://codeclimate.com/github/reset/ridley)
+
+A reliable Chef API client with a clean syntax
+
+## Installation
+
+    $ gem install ridley
+
+## Known Issues
+
+* Search has not been implemented
+* Sandboxes has not been implemented
+* Full support for Cookbooks is not included
+* Acceptance test suite needs to be refactored
+
+## Usage
+
+Require Ridley into your application
+
+    require 'ridley'
+
+## Creating a new connection
+
+    conn = Ridley::Connection.new(
+      server_url: "https://api.opscode.com",
+      client_name: "reset",
+      client_key: "/Users/reset/.chef/reset.pem",
+      organization: "ridley"
+    )
+
+Creating a new connection requires you to specify at minimum:
+
+* server_url
+* client_name
+* client_key
+
+An optional organization option can be specified if you are working with Hosted or Private Chef (OHC/OPC). For a full list of available options see the [yard documentation](http://rubydoc.info/gems/ridley).
+
+__NOTE: You do not want to specify an `organization` if you are connecting to an Open Source Chef server.__
+
+Connections can also be instantiated by a helper function: `Ridley.connection`
+
+    Ridley.connection(
+      server_url: "https://api.opscode.com",
+      client_name: "reset",
+      client_key: "/Users/reset/.chef/reset.pem",
+      organization: "ridley"
+    )
+
+Using a connection object you can interact with collections of resources on a Chef server. Resources are:
+
+* Nodes
+* Roles
+* Environments
+* Clients
+* Cookbooks
+* Data Bags
+
+Here is a simple example of instantiating a new connection and listing all of the roles on a Chef server.
+
+    conn = Ridley.connection(...)
+    conn.role.all => []
+
+For more information scroll down to the Manipulating Chef Resources section of this README.
+
+### Synchronous execution
+
+An alternative syntax is provided if you want to perform multiple requests, in order, on a connection.
+
+    conn = Ridley.connection(...)
+
+    conn.sync do
+      role.all
+      role.find("reset")
+      role.create(name: "ridley-test")
+      role.delete("reset")
+    end
+
+The `sync` function on the connection object takes a block with no arguments and allows you to access the DSL within the block. You can address any one of the resources within the sync block:
+
+    conn.sync do
+      environment.all
+      node.all
+      ...
+    end
+
+A helper function exists to allow you to express yourself in a one-liner: `Ridley.sync`
+
+    Ridley.sync(server_url: "https://api.opscode.com", ...) do
+      role.all => []
+    end
+
+### Asynchronous execution
+
+__COMING SOON__
+
+## Manipulating Chef Resources
+
+All resource can be listed, created, retrieved, updated, or destroyed. Some resources have additional functionality described in [their documentation](http://rubydoc.info/gems/ridley).
+
+### Listing all resources
+
+You use a connection to interact with the resources on the remote Chef server it is pointing to. For example, if you wanted to get a list of all of the roles on your Chef server:
+
+    conn = Ridley.connection(...)
+    conn.role.all           => []
+
+Calling `role.all` on the connection object will return an array of Ridley::Role objects. All of the resources can be listed, not just Roles:
+
+    conn = Ridley.connection(...)
+    conn.node.all           => [<#Ridley::Node>]
+    conn.role.all           => [<#Ridley::Role>]
+    conn.environment.all    => [<#Ridley::Environment>]
+    conn.client.all         => [<#Ridley::Client>]
+    conn.cookbook.all       => [<#Ridley::Cookbook>]
+    conn.data_bag.all       => [<#Ridley::DataBag>]
+
+### Creating a resource
+
+A new resource can be created in a few ways
+
+_Create by instantiate and save_
+
+    conn = Ridley.connection(...)
+    obj = conn.role.new
+
+    obj.name = "reset"
+    obj.save => <#Ridley::Role: @name="reset">
+
+_Create by the `create` function with attribute hash_
+
+    conn = Ridley.connection(...)
+    conn.role.create(name: "reset") => <#Ridley::Role: @name="reset">
+
+_Create by the `create` function with a resource object_
+
+    conn = Ridley.connection(...)
+    obj = conn.role.new
+
+    obj.name = "reset"
+    conn.role.create(obj) => <#Ridley::Role: @name="reset">
+
+Each of these methods is identical, it is up to you on how you'd like to create new resources.
+
+### Retrieving a resource
+
+There are two functions for retrieving a resource. `find` and `find!`. If you are familiar with ActiveRecord; these are the functions used to pull records out of the database.
+
+Both `find` and `find!` will return a resource but if the resource is not found on the Chef server `find!` will raise an exception while `find` will return `nil`.
+
+If you were following allong in the previous section we created a role named `reset`. We'll assume that role has been created in this next example.
+
+    conn = Ridley.connection(...)
+
+    conn.role.find("reset") => <#Ridley::Role: @name="reset">
+    conn.role.find!("reset") => <#Ridley::Role: @name="reset">
+
+Now if we attempt to find a role that does not exist on the Chef server
+
+    conn = Ridley.connection(...)
+
+    conn.role.find("not_there") => nil
+    conn.role.find!("not_there") =>
+    Ridley::Errors::HTTPNotFound: errors: 'Cannot load role reset'
+      from /Users/reset/code/ridley/lib/ridley/middleware/chef_response.rb:11:in `on_complete'
+      from /Users/reset/.rbenv/versions/1.9.3-p194/lib/ruby/gems/1.9.1/gems/faraday-0.8.1/lib/faraday/response.rb:9:in `block in call'
+      from /Users/reset/.rbenv/versions/1.9.3-p194/lib/ruby/gems/1.9.1/gems/faraday-0.8.1/lib/faraday/response.rb:63:in `on_complete'
+      from /Users/reset/.rbenv/versions/1.9.3-p194/lib/ruby/gems/1.9.1/gems/faraday-0.8.1/lib/faraday/response.rb:8:in `call'
+      from /Users/reset/code/ridley/lib/ridley/middleware/chef_auth.rb:31:in `call'
+      from /Users/reset/.rbenv/versions/1.9.3-p194/lib/ruby/gems/1.9.1/gems/faraday-0.8.1/lib/faraday/connection.rb:226:in `run_request'
+      from /Users/reset/.rbenv/versions/1.9.3-p194/lib/ruby/gems/1.9.1/gems/faraday-0.8.1/lib/faraday/connection.rb:87:in `get'
+      from /Users/reset/code/ridley/lib/ridley/resource.rb:115:in `find!'
+      from /Users/reset/code/ridley/lib/ridley/context.rb:22:in `method_missing'
+      from (irb):6
+      from /Users/reset/.rbenv/versions/1.9.3-p194/bin/irb:12:in `<main>'
+
+### Updating a resource
+
+Like creating a resource, updating a resource can also be expressed a few different ways
+
+_Update by the `update` function with an id and attribute hash_
+
+    conn = Ridley.connection(...)
+    conn.role.update("reset", description: "testing updates!") => <#Ridley::Role: @name="reset", @description="testing updates!">
+
+_Update by the `update` function with a resource object_
+
+    conn = Ridley.connection(...)
+    obj = conn.role.find("reset")
+    obj.description = "resource object!"
+
+    conn.role.update(obj) => <#Ridley::Role: @name="reset", @description="resource object!">
+
+_Update by saving a resource object_
+
+    conn = Ridley.connection(...)
+    obj = conn.role.find("reset")
+
+    obj.description = "saving an object!"
+    obj.save => <#Ridley::Role: @name="reset", @description="saving an object!">
+
+### Deleting a resource
+
+Like creating or updating a resource, there are a few ways deleting a resource can be expressed
+
+_Delete by the `delete` function with an id_
+
+    conn = Ridley.connection(...)
+    conn.role.delete("reset") => <#Ridley::Role: @name="reset">
+
+_Delete by the `delete` function with a resource object_
+
+    conn = Ridley.connection(...)
+    obj = conn.role.find("reset")
+
+    conn.role.delete(obj) => <#Ridley::Role: @name="reset">
+
+_Delete by the `destroy` function on a resource object_
+
+    conn = Ridley.connection(...)
+    obj = conn.role.find("reset")
+
+    obj.destroy => true
+
+### Regenerating a client's private key
+
+_Regenerate function on a context with an id_
+
+    conn = Ridley.connection(...)
+    conn.client.regenerate_key("jwinsor") => <#Ridley::Client: @name="jwinsor", @private_key="HIDDEN">
+
+_Regenerate function on an instantiated resource object_
+
+    conn = Ridley.connection(...)
+    obj = conn.client.find("jwinsor")
+
+    obj.regenerate_key => <#Ridley::Client: @name="jwinsor", @private_key="HIDDEN">
+
+## Manipulating Data Bags and Data Bag Items
+
+A data bag is managed exactly the same as any other Chef resource
+
+    conn = Ridley.connection(...)
+    conn.data_bag.create("ridley-test")
+
+You can create, delete, update, or retrieve a data bag exactly how you would expect if you read through the
+Manipulating Chef Resources portion of this document.
+
+Unlike a role, node, client, or environment, a data bag is a container for other resources. These other resources are Data Bag Items. Data Bag Items behave slightly different than other resources. Data Bag Items can have an abritrary attribute hash filled with any key values that you would like. The one exception is that every Data Bag Item __requires__ an 'id' key and value. This identifier is the name of the Data Bag Item.
+
+### Creating a Data Bag Item
+
+    conn = Ridley.connection(...)
+    data_bag = conn.data_bag.create("ridley-test")
+
+    data_bag.item.create(id: "appconfig", host: "reset.local", user: "jwinsor") => 
+      <#Ridley::DataBagItem: @id="appconfig", @host="reset.local", @user="jwinsor">
+
+### Saving a Data Bag Item
+
+    conn = Ridley.connection(...)
+    data_bag = conn.data_bag.create("ridley-test")
+
+    dbi = data_bag.item.new
+    dbi[:id] = "appconfig"
+    dbi[:host] = "reset.local"
+    dbi.save => true
+
+# Authors and Contributors
+
+* Jamie Winsor (<jamie@vialstudios.com>)