chef-resource 0.2.2

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: a27971d67bec23229aaee17383b7e44a965a92b3
+  data.tar.gz: 804df782696fee0a92b2c3ff67497f65b12c88ea
+SHA512:
+  metadata.gz: b922d78fda97186c833ec62ac4ddf8bdce5bbdf9b8b94d1971381ca12c18e4a2e93073ccbad51aeea50b52208be78eb9c0a657a14dd655e3adc0ac7e8fb656b8
+  data.tar.gz: 35d4b22cc5c8b1df343e87fa6dc5cb9a5cbdbb3b836cbd769530e58414e68c6c3d28299b125f945f69a02324afb7f98c1b5034687ca46e7a78817fdb3f63ed6c

data/CHANGELOG.md

@@ -0,0 +1,23 @@
+Resource Cookbook CHANGELOG
+===========================
+
+0.2.2 (4/1/2015)
+-----------------
+
+- Fix issue with uploading via berks (@damascus)
+
+0.2.1 (2/19/2015)
+-----------------
+
+- Rename ChefResource.resource -> Chef.resource
+- Get cookbook include working again
+
+0.2 (2/19/2015)
+---------------
+
+- Initial publication
+- Single-file resources
+- depends "resource" is how you use it
+- Read/write resources with load/converge
+- define, defaults, resource keywords
+- strongly typed properties and coercion

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 [yyyy] [name of copyright owner]
+
+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,264 @@
+ [![Stories in Ready](https://badge.waffle.io/chef-cookbooks/resource.png?label=ready&title=Ready)](https://waffle.io/chef-cookbooks/resource)[![Build Status](https://travis-ci.org/chef-cookbooks/resource.svg?branch=master)](https://travis-ci.org/chef-cookbooks/resource)[![Gitter chat](https://badges.gitter.im/chef-cookbooks/resource.png)](https://gitter.im/chef-cookbooks/resource)
+
+The Resource Cookbook
+=====================
+
+Chef Resources are incredibly important to creating good, useful, reusable cookbooks.  Yet people often don't create them because it's too hard.  The resource cookbook aims to change that.
+
+The resource cookbook is an attempt to make Chef Resources significantly easier and more fun to create, while being even more powerful.  It does this by:
+
+- Vastly simplifying resource writing so you just make a "resource" and "recipe" in a single file.
+- Making good primitive resources easier to build with builtin test-and-set support.
+- Allowing users to *read* data from resources, making them significantly more useful.
+- Allowing users to easily customize resource definitions in-place, adding defaults and tweaks.
+
+I am looking for people to try this out and give feedback.  IT IS EXPERIMENTAL.  There are bugs (though I generally don't know what they are).  Things will change.  There is a lot of feedback to gather and that will affect what it does.  But this has been revised many, many times in an attempt to produce something close enough to right that I hope it won't change *much,* or in fundamental ways.
+
+This is also unfinished in that there are more features to be added: chief among them are nested properties (Hash, Array, Set and Struct), nested resources (github.organization.repository) and recipe semantics (immediate mode and parallel recipes).  0.1 is a stop along the way, but a very significant one that defines the basis for Resources.
+
+For an in-depth comparison of Chef Resources and ChefResource Resources, see the [0.1 release notes](docs/0.1-release.md).
+
+Getting Started
+---------------
+To get started, upload the resource cookbook and add this to your `metadata.rb`:
+
+```ruby
+depends "resource"
+```
+
+ChefResource is now loaded in, and the following features are available:
+- `Chef.resource`, `ChefResource.define` and `ChefResource.defaults` will define and customize resources
+- All recipes everywhere can call ChefResource resources
+- The `resources` directory in your cookbook now creates ChefResource resources (via `Chef.resource`).
+- Recipes in your cookbook have `resource`, `define` and `defaults` available (which call the `ChefResource.` equivalent)
+
+NOTE: cookbooks that depend on your cookbook will *not* automatically be ChefResourceed.  Only cookbooks that explicitly depend on the resource cookbook will be transformed.
+
+Compatibility
+-------------
+
+ChefResource works with Chef 12.  It also does not change *anything* about existing cookbook behavior, and only affects cookbooks who have `depends "resource"` in their metadata.  Resources you create with ChefResource are available to all cookbooks, including existing cookbooks which do not directly depend on the "resource" cookbook.
+
+Define: Dashing Off a Quick Resource
+------------------------------------
+
+Say you noticed that you're creating a series of "user home directories," like this:
+
+```ruby
+# Old recipe
+user 'jkeiser' do
+  group 'users'
+end
+
+directory "/home/jkeiser" do
+  owner 'jkeiser'
+  group 'users'
+  mode 0700
+end
+
+file "/home/jkeiser/.bashrc" do
+  owner 'jkeiser'
+  group 'users'
+  mode 0700
+  content "sh /sys/global_bashrc"
+end
+
+user 'fnichol' do
+  group 'users'
+end
+
+directory "/home/fnichol" do
+  owner 'fnichol'
+  group 'users'
+  mode 0700
+end
+
+file "/home/fnichol/.bashrc" do
+  owner 'fnichol'
+  group 'users'
+  mode 0700
+  content "sh /sys/global_bashrc"
+end
+
+...
+```
+
+That's a lot of repetition!  How do you make repetition better in Chef?  A resource!  Just write this in your recipe:
+
+```ruby
+define :user_bundle, :username, primary_group: 'users' do
+  user username do
+    group primary_group
+  end
+
+  directory "/home/#{username}" do
+    owner username
+    group primary_group
+    mode 0700
+  end
+
+  file "/home/#{username}/.bashrc" do
+    content "sh /sys/global_bashrc"
+
+    owner username
+    group primary_group
+    mode 0700
+  end
+end
+
+# Now let's use our resource!
+user_bundle 'jkeiser' do
+end
+user_bundle 'fnichol' do
+end
+user_bundle 'blargh' do
+end
+```
+
+Much more concise, much more readable, much easier to change!
+
+Creating a Simple Resource
+--------------------------
+If you want to really customize the properties of a resource, or want to do more interesting things, you can always create a `resources` file.  ChefResource appropriates the LWRP `resources` directory, so you create a `resources/user_bundle.rb`:
+
+```ruby
+# resources/user_bundle.rb
+property :username, String, identity: true
+property :primary_group, String
+property :home_dir, Path, relative_to: '/home' do
+  default { username }
+end
+
+recipe do
+  user username do
+    group primary_group
+  end
+
+  directory home_dir do
+    owner username
+    group primary_group
+    mode 0700
+  end
+
+  file "#{home_dir}/.bashrc" do
+    content "sh /sys/global_bashrc"
+
+    owner username
+    group primary_group
+    mode 0700
+  end
+end
+```
+
+```ruby
+# recipes/default.rb
+test_user_bundle 'jkeiser' do
+end
+test_user_bundle 'fnichol' do
+end
+test_user_bundle 'blargh' do
+end
+```
+
+Some features here:
+- `property` is how you define a named thing
+- `identity: true` means that when you write `user_bundle 'jkeiser'`, `username` will be set to `jkeiser`.
+- `String` and `Path` are property *types*.  It means the resource will not allow the user to set the property to something else, like 1 or false, which isn't a valid path or username.
+- `relative_to: '/home'` is a modifier for `Path` saying "when the user says `home_dir 'jkeiser2'`, set `home_dir` to `/home/jkeiser2`."
+- `default { username }` is a *computed default*: if the user does not set `home_dir`, `home_dir` will be `/home/<username>`
+
+NOTE: you can define a resource *anywhere* by writing `Chef.resource :name do ... end`, and writing `property` and `recipe` statements inside.  You can do this in `libraries`, `recipes` or even outside Chef.
+
+Building Primitive Resources: Load and Converge
+-----------------------------------------------
+
+Up until now, we've been showing "compound" resources whose primary job is to wrap other resources like `file`, `package` and `service`.  This is enough for huge numbers of people, and the primitive resources handle the work of "test-and-set," showing the "(up to date)" if nothing needs to change, or the green text when a change occurs.
+
+Sometimes you need to build a real primitive resource, when `file` `package` and `service` aren't enough.  When this comes up, ChefResource handles the work of test-and-set for you with the `load` and `converge` methods.
+
+Consider a simple file resource:
+
+```ruby
+# resources/file.rb
+property :path, Path, identity: true
+property :mode, Integer
+property :content, String
+
+recipe do
+  converge do
+    File.chmod(mode, path)
+    IO.write(path, content)
+  end
+end
+
+def load
+  mode File.stat(path).mode
+  content IO.read(path)
+end
+```
+
+The The resource cookbook things here:
+
+- `converge do ...` handles test-and-set.  It will check to see if the user has changed `mode` or `content` from its real value (as read in by `load`).  If so, it will print an appropriate message in green text showing what's changed, and mark the resource as updated.
+- `def load` loads the *current values* of the actual resource.  This is called when `converge` happens, or when the user asks for a value that hasn't been filled in (like if they ask for `mode` and haven't set it yet).
+
+What's also interesting is you have now defined a *read API*.  If the user does `file('/x.txt').content`, then it will show you the file contents of `/x.txt`.
+
+Customizing Resources in Cookbooks: Defaults
+--------------------------------------------
+
+As a *user* of a resource, there are a number of times where you're repeating something over and over.  How many of us have typed this:
+
+```ruby
+file '/x.txt' do
+  owner 'jkeiser'
+  group 'users'
+  mode 0755
+  content 'x'
+end
+file '/y.txt' do
+  owner 'jkeiser'
+  group 'users'
+  mode 0755
+  content 'y'
+end
+file '/z.txt' do
+  owner 'jkeiser'
+  group 'users'
+  mode 0755
+  content 'z'
+end
+```
+
+ChefResource gives you a quick way to redefine the defaults of a resource:
+
+```ruby
+defaults :my_file, :file, owner: 'jkeiser', group: 'users', mode: 0755
+my_file '/x.txt' do
+  content 'x'
+end
+my_file '/y.txt' do
+  content 'y'
+end
+my_file '/z.txt' do
+  content 'z'
+end
+```
+
+You can also specialize resources with more complex behavior:
+
+```ruby
+# A version of "file" that assumes the group == the username
+resource :my_file, :file do
+  attribute :group, String do
+    default { username }
+  end
+end
+```
+
+Contributing
+------------
+
+PRs are welcome at [github](https://github.com/chef-cookbooks/resource)!
+
+To give feedback, file issues in [github](https://github.com/chef-cookbooks/resource/issues) or chat on [Gitter](https://gitter.im/chef-cookbooks/resource).