chef_fixie_shahid 0.5.2

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 7a3dfd490674a4bdfe48472718b21f40cc29dd1c969e095cfa20493d6120e068
+  data.tar.gz: 9b3e69d524edcfae3c3a41adee8a9f740a0136bf5b8092d8cf4e20fb2c552661
+SHA512:
+  metadata.gz: 2e81318f05760594c75c4a6eda5df1c9336891da31796ca99f27a6d24281d589c10b356e53dda1000dc8138a8557ff416fa462d632549ee522a8727573f1d565
+  data.tar.gz: 69cb244f8f561e19f203d7e1dd22b1f2265925a854d9603489e962d56abbb44544ba43edf59b609eb0937f00416985c82b1882dec30cc373313fa01b39814774

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,69 @@
+fixie
+=====
+
+Low level manipulation tool for Chef Server 12 and later.
+
+This tool is in its very early stages, and should be used with great care.
+
+## Purpose
+
+Provide a tool to debug and fix low level problems with chef server, especially those surrounding ACLs and
+groups. This tool works at an extremely low level, and provides minimal protection against data loss and
+corruption. If a problem can be fixed using the API, that should be done instead. This exists for those use
+cases where the API can't be used.
+
+## History
+
+For many years orgmapper has been a useful, if somewhat frustrating tool to debug and fix low level problems
+with chef server, especially those surrounding ACLs and groups. The tool has never been stable, and has
+suffered from somewhat arcane syntax. 
+
+Orgmapper became increasingly broken with the move to use sql instead of couchdb, and the obsolescence of
+mixlib-authorization, opscode-account and the rest of the ruby based chef, and became completely useless with
+the migration of organizations to SQL. Yet the need for a low level editing tool remains.
+
+## Goals
+
+* Allow the repair of common problems such as organization lockouts, broken ACLs and the like.
+
+* Tests: All functionality should be part of CI, and run as part of nightly tests. We should treat breakage
+  of fixie as a issue to be addressed like any other CI failure. 
+
+* Scriptability: We have a collection of scripts for diagnosing and fixing user problems written against
+  orgamapper; these scripts should be ported and enhanced to make them more generally useful.
+
+
+## Documentation
+
+Documentation can be found in in the doc directory, especially the
+[doc/GETTING_STARTED.md](doc/GETTING_STARTED.md) file.
+
+## Bugs/Issues/Pull Requests
+
+Please file bugs/issues/pull requests against the [fixie](https://github.com/chef/fixie) repository in
+github. 
+
+## License
+
+|                      |                                          |
+|:---------------------|:-----------------------------------------|
+| **Copyright:**       | Copyright (c) 2014-2015 Chef Software, Inc.
+| **License:**         | Apache License, Version 2.0
+
+
+All files in the repository are licensed under the Apache 2.0 license. If any file is missing the License
+header it should assume the following is attached;
+
+Copyright 2014 Chef Software Inc.
+
+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/bin/chef_fixie

@@ -0,0 +1,5 @@
+#!/usr/bin/env ruby
+
+require_relative "../lib/chef_fixie/console"
+
+ChefFixie::Console.start

data/doc/AccessingSQL.md

@@ -0,0 +1,68 @@
+
+Basics:
+-------
+
+Underneath everything is the Ruby Sequel library; there are a number
+of ways to access it.
+
+Check out http://ricostacruz.com/cheatsheets/sequel.html or the Sequel
+gem docs for details of the sequel library.
+
+Many objects in fixie have the accessor inner, which exposes the
+Sequel selector. This includes:
+* The constants ORGS, USERS, ASSOCIATIONS, and INVITES
+```ruby
+ORGS.inner.first
+#< @values={:id=>"7ddaee6b42e8f6a0a8e9d5d5efe644f8", :authz_id=>"f46b2e53869968ce115b97d2fd8bfee0", :name=>"ponyville", :full_name=>"ponyville", :assigned_at=>2015-07-21 18:22:34 UTC, :last_updated_by=>"08076ed32f7d5c62721607dd2c309c55", :created_at=>2015-07-21 18:22:34 UTC, :updated_at=>2015-07-21 18:22:34 UTC}>
+```
+* Any of the by_XXXX accessors
+```ruby
+ORGS['
+
+
+```
+
+
+
+
+
+fixie:0 > o.groups.by_name(cl.id).inner.count
+1
+fixie:0 > o.groups.by_name(cl.id).inner.delete
+1
+fixie:0 > o.groups.by_name(cl.id).inner.count     
+
+
+* Changing email for user in fixie
+
+USERS.by_username('anujbiyani').inner.update(:email=>"anujbiyani01@gmail.com")
+
+
+
+* Adding a record
+```ruby
+u=USERS['a_username']
+o=ORGS['an_org']
+pivotal = USERS['pivotal']
+now = Sequel.function(:NOW)
+
+ASSOCS.inner.insert(:org_id=>o.id, :user_id=>u.id, :last_updated_by=>pivotal.authz_id,
+	:created_at=>now, :updated_at=>now )
+```
+
+
+* Fixing a group that lost its authz object.
+We've seen the users group in hosted loose it's authz entry
+
+```ruby
+a = Fixie::AuthzApi.new
+# create a new authz group
+g = a.post("groups",{})
+# check that only one group is returned
+ORGS['acme'].groups.by_name('users').inner.all
+# alter the group and insert the new authz id
+ORGS['acme'].groups.by_name('users').inner.update(:authz_id=>g.id)
+```
+
+This does not add the users back to the usergs group, or re-add users
+all the acls that used to have the users group in them.

data/doc/BulkFixup.md

@@ -0,0 +1,33 @@
+Restoring acl permissions globally
+============
+
+If a key group is deleted (such as users)
+
+* Verify that the org has issues
+
+* Create/restore the group
+(TBW)
+
+* Add the users/groups back to the group
+(TBW)
+
+* Set the group ACL appropriately
+```ruby
+users_group.ace_add([:create,:read,:update,:delete], org.groups['admins'])
+users_group.ace_add([:create,:read,:update,:delete], USERS['pivotal'])
+```
+
+* Restore users to the appropriate container ACLs
+```ruby
+org = ORGS[THE_ORG]
+cl = %w(cookbooks data nodes roles environments policies policy_groups cookbook_artifacts)
+cl.each {|c| o.containers[c].ace_add([:create,:read,:update,:delete], org.groups['users']) }
+%w(clients).each { |c| org.containers[c].ace_add([:read,:delete], org.groups['users']) }
+%w(groups containers).each { |c| org.containers[c].ace_add([:read], org.groups['users']) }
+%w(sandboxes).each { |c| org.containers[c].ace_add([:create], org.groups['users']) }
+```
+
+* Then update the objects from the containers:
+```ruby
+Fixie::BulkEditPermissions::copy_from_containers(org)
+```

data/doc/CommonTasks.md

@@ -0,0 +1,31 @@
+
+
+
+Automated organization checkup
+----------
+
+If you don't know what's up with an org, there are a few easy starting
+points
+
+First of all, run the automated org association checker:
+
+    fixie:0 > Fixie::CheckOrgAssociations.check_associations("acme")
+    Org acme is ok (6 users)
+
+If it reports a problem with a user, you may be able to fix it
+automatically:
+
+    fixie:0 > Fixie::CheckOrgAssociations.fix_association("acme", "mary")
+
+This might need to be run multiple times to fix all of the errors.
+
+
+Removing a user completely from an org
+-----------
+
+    [1] fixie(main)> ChefFixie::CheckOrgAssociations.remove_association('the_org', 'the_user')
+
+This removes the user from the org, and removes them from all org
+groups. However, if the user has been individually added to an ACL we
+don't fix that up; it would require enumeration of the whole org, and
+that hasn't been implemented.

data/doc/GETTING_STARTED.md

@@ -0,0 +1,228 @@
+
+Installing fixie 
+-------
+In the fixie directory, run `bundle install --binstubs`
+
+Configuring fixie
+-------
+
+On chef server installs, fixie can read configuration information out
+of /etc/opscode, specifically the chef-server-running.json file.
+
+Otherwise, you will need a fixie.conf file with the appropriate URIs and secrets for
+accessing postgres and bifrost.
+
+The fixie.conf.example file contains examples from a instance of
+private chef.
+
+| Attribute | Description | Example |
+|-----------|-------------|---------|
+| authz_uri | The URI for the bifrost/authz service | http://localhost:9463 |
+| superuser\_id | The authz superuser id | fa84f0f5524a06baaa10b0f988ff2d8f |
+| sql\_database | A Ruby Sequel compatible database URI with user and password | postgres://opscode_chef:3b2bb8affc0b87233130f820443aecca2061fadc6c0df16828233e433877ca1c552d1b9d40d3971f0e8c21fc4b7ff9471d91@localhost/opscode_chef |
+
+Running fixie
+------
+
+Start fixie with
+```shell
+bin/fixie fixie.conf
+```
+The config file is optional, leaving it out will attempt to read
+/etc/opscode for configuration.
+
+Inspecting objects
+------
+
+There are two core class hierarchies in fixie, one corresponding to a
+table (e.g. Orgs), and another corresponding to a row in the table
+(e.g. Org). The naming convention is that the plural refers to the
+table and the singular refers to the row. These are tightly coupled,
+and generally if one exists the other will too.
+
+The table class (e.g. Orgs) provides access to the raw Sequel
+objects. There are several constants in the REPL containing
+pre-initialized instances of the commonly accessed table classes,
+including ORGS, USERS, ASSOCIATIONS, and INVITES.
+
+#### Standard accessors
+
+Each of these have accessors to search by various columns. These use the naming pattern #by\_XXXX, where XXX is the column name in the database. For example ORGS.by\_name('ponyville') searches for the org named 'ponyville'. The return value from this accessor is a new instance of the object that can be further refined. In many cases aliases have been added to hide naming quirks. For example groups use the 'groupname' column, but they can also be accessed using the #by\_name function. 
+
+The REPL supports method completion, so the list of supported filters can be found by typing `ORGS.by_` and hitting the tab key. 
+
+To get a list of all objects selected use the #all method. To list the names of the objects use the #list
+method:
+
+```ruby
+fixie:0 > ORGS.list
+["acme", "ponyville", "wonderbolts"]
+fixie:0 > ORGS.all
+[#<Fixie::Sql::Org:0x00000003886fa0 @data=#< @values={:id=>"ca0542c21119786fd4d2ddeb5c920ecf", :authz_id=>"baefe78d2fdab7d31fce7f4bdd6feda8", :name=>"ponyville", :full_name=>"ponyville", :assigned_at=>2015-02-05 03:06:33 UTC, :last_updated_by=>"9f6f823739fe6417b1c247ca0d2afdfc", :created_at=>2015-02-05 03:06:33 UTC, :updated_at=>2015-02-05 03:06:33 UTC}>>, #<Fixie::Sql::Org:0x00000003886f50 @data=#< @values={:id=>"2742f6f01ae95aa5998fd7ad94e0d383", :authz_id=>"52064f4a67a2b6c0243051e9f855699a", :name=>"wonderbolts", :full_name=>"wonderbolts", :assigned_at=>2015-02-05 03:07:05 UTC, :last_updated_by=>"9f6f823739fe6417b1c247ca0d2afdfc", :created_at=>2015-02-05 03:07:05 UTC, :updated_at=>2015-02-05 03:07:05 UTC}>>, #<Fixie::Sql::Org:0x00000003886f28 @data=#< @values={:id=>"0434803f600f1688707081921cf92721", :authz_id=>"b9a9dee90b6c2ab31cf4350aeba59460", :name=>"acme", :full_name=>"acme", :assigned_at=>2015-02-05 03:07:32 UTC, :last_updated_by=>"9f6f823739fe6417b1c247ca0d2afdfc", :created_at=>2015-02-05 03:07:32 UTC, :updated_at=>2015-02-05 03:07:32 UTC}>>]
+```
+
+The #all and #list functions have protection against accidentally grabbing the entire table; if too many
+results are included (currently 10), it returns `:too_many_results` instead. Providing a parameter to the #all
+and #list function adjusts the limit.
+
+Any object that has a well defined 'name' has the index ('[]') accessor provided; this takes a string and
+returns a single exact match for it if it exists.
+
+#### Predefined objects
+* USERS
+
+This allows access to the users table in sql. 
+
+To get the user named 'rainbowdash'
+```ruby
+> u = USERS['rainbowdash']
+#<Fixie::Sql::User:0x00000002afea18 @data=#< @values={:id=>"0000000000004d3eac4cc85b2bdddd0f", :authz_id=>"070dc1cd727a6b71e48d5e16f8d7b137", :username=>"rainbowdash", :email=>"rainbowdash@ponyville.com", :pubkey_version=>0, :public_key=>"-----BEGIN PUBLIC KEY-----\nMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAr0ZeWeIuU+rO2m1Pe8Nk\n7kzkqmk+CbaP8CVc0OlPZZITgoW2NEseCg1N3FVrCGIIY8vhDkyPST7ZKNva/hOo\nltC8inN695wRchQ1EDpVityL7EIuu7haXBib2WA2HQezlRWKMdrMGGRq0bMa3lD4\nV/YfEXSBtkE8W7QaanbtpgipWC1VGorj0MLR+++JYGd9kqGp49DiC7FH+DChE6pj\nRD9d25/chclD+svZy7RW0s2Q0/H/qRjhOdHoBGljJohVF64CsfqhDCr02zytbKDy\n6sOFjFneSqDZhlx81uVtQ0l+H+0bx77zbwLtp/WjpUFjw/yA8V92/WCjvwMTUaRN\nxQIDAQAB\n-----END PUBLIC KEY-----\n\n", :serialized_object=>"{\"display_name\":\"rainbowdash pony\",\"first_name\":\"rainbowdash\",\"last_name\":\"pony\",\"middle_name\":\"\"}", :last_updated_by=>"c8bd48b83f61031c29ab4ff5168fccd2", :created_at=>2014-10-31 16:59:37 UTC, :updated_at=>2014-10-31 16:59:37 UTC, :external_authentication_uid=>nil, :recovery_authentication_enabled=>false, :admin=>false, :hashed_password=>"$2a$12$FZMrxfVxWLpj8xPiBXG6SO2YxqGMp3zAj7I4w7cr50y1VbCbgIrUe", :salt=>"$2a$12$FZMrxfVxWLpj8xPiBXG6SO", :hash_type=>"bcrypt"}>>
+```
+
+
+To see just the name of that user: 
+```ruby
+> u.name
+"rainbowdash"
+```
+
+To find all users with ponyville in their name:
+```ruby
+> USERS.by_email(/ponyville/)
+#<Fixie::Sql::Users:0x00000003514200 @inner=#<Sequel::Postgres::Dataset: "SELECT * FROM \"users\" WHERE (\"email\" ~ 'ponyville')">>
+```
+
+Note this returns a users table object which can be refined
+further. To process the list of users selected, use the #all method:
+```ruby
+> USERS.by_email(/ponyville/).all.map {|x| x.name }
+["rainbowdash", "fluttershy", "applejack", "pinkiepie", "twilightsparkle", "rarity"]
+```
+
+To further refine the set of objects further selectors can be applied:
+```ruby
+fixie:0 > USERS.by_email(/ponyville/).by_username(/apple/).all.first.name
+"applejack"
+```
+
+The #all method has a hidden limit (which may be changed in future versions). It has takes a paramenter max\_count (defaults to 10). If it will return more than max\_count elements it returns :too\_many\_results instead; this is to prevent filling the screen or slammming the database by accident.
+```ruby
+fixie:0 > USERS.all
+:too_many_results
+```
+* ORGS
+
+ORGS work very similarly to USERS, but the org object return also adds accessors for org scoped objects such as nodes, roles, groups, containers, etc.
+
+```ruby
+fixie:0 > ORGS['ponyville'].full_name
+"ponyville"
+
+fixie:0 > ORGS['ponyville'].groups.all.map {|x| x.name}
+["admins", "billing-admins", "clients", "0000000000004d3eac4cc85b2bdddd0f", "000000000000506ccf528a2844e81838", "000000000000808da6731453e12eb2bb", "000000000000dfccddd011ce219caaf0", "00000000000036639a19f27527b29a3e", "000000000000224a1c0e395b112c1d20", "users"]
+```
+
+* ASSOCS
+* INVITES
+* GLOBAL\_GROUPS
+* GLOBAL\_CONTAINERS
+
+Altering ACLs and Groups
+-----------
+
+
+#### Editing ACLs
+
+The objects returned by the above selectors have accessors to allow editing of acl and group membership.
+
+ACLs can be viewed for any object
+```ruby
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].acl
+{"create"=>{"actors"=>[[:global, "pivotal"]], "groups"=>[["ponyville", "admins"]]}, "read"=>{"actors"=>[[:global, "pivotal"]], "groups"=>[["ponyville", "admins"], ["ponyville", "users"]]}, "update"=>{"actors"=>[[:global, "pivotal"]], "groups"=>[["ponyville", "admins"]]}, "delete"=>{"actors"=>[[:global, "pivotal"]], "groups"=>[["ponyville", "admins"], ["ponyville", "users"]]}, "grant"=>{"actors"=>[[:global, "pivotal"]], "groups"=>[["ponyville", "admins"]]}}
+```
+
+Individual ACEs can be viewed
+
+```ruby
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].ace(:read)
+{"actors"=>[[:global, "pivotal"], [:global, "fluttershy"]], "groups"=>[["ponyville", "admins"], ["ponyville", "users"]]}
+```
+
+Users and groups can be added to an ACE. The APIs are 'magic' in the sense that they can take an object and figure out if it is an actor or group and add it appropriately.
+
+```ruby
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].ace_add(:read, USERS['fluttershy'])
+    {}
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].ace_add(:read, GLOBAL_GROUPS['ponyville_global_admins'])
+{}
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].ace(:read)
+{"actors"=>[[:global, "pivotal"], [:global, "fluttershy"]], "groups"=>[["ponyville", "admins"], ["ponyville", "users"], ["unknown-00000000000000000000000000000000", "ponyville_global_admins"]]}
+```
+
+And removed:
+```ruby
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].ace_delete(:read, GLOBAL_GROUPS['ponyville_global_admins'])
+{}
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].ace(:read)
+{"actors"=>[[:global, "pivotal"], [:global, "fluttershy"]], "groups"=>[["ponyville", "admins"], ["ponyville", "users"]]}
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].ace_delete(:read, USERS['fluttershy'])
+{}
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].ace(:read)
+{"actors"=>[[:global, "pivotal"]], "groups"=>[["ponyville", "admins"], ["ponyville", "users"]]}
+```
+
+The ace\_add and ace\_delete functions take the symbols :create, :read, :update, :delete and :grant in
+the action field. The user can also provide an array of those symbols for bulk operations, or
+specify :all to edit all of the actions.
+
+```ruby
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].ace_add(:all, USERS['pivotal'])
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].ace_add([:read,:update], USERS['fluttershy'])
+```
+
+
+##### Copying ACLs
+
+Sometimes it is useful to copy permisons from one object to another. For example, if an object has
+had a catastrophic permission edit, you'd like to at least restore the permissions it would have
+inherited from the container. This command *adds* permissions from another object, but does not
+remove any permisions already there.
+
+```ruby
+fixie:0 > clients_container = ORGS['ponyville'].containers['clients']
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].acl_add_from_object(clients_container)
+```
+
+##### Raw access
+
+
+
+There are also _raw versions of these functions that work on the raw authz ids
+```ruby
+fixie:0 > ORGS['ponyville'].clients['ponyville-validator'].acl_raw
+{"create"=>{"actors"=>["c8bd48b83f61031c29ab4ff5168fccd2"], "groups"=>["ca0a8cabaafaae658edd298ddd4266cd"]}, "read"=>{"actors"=>["c8bd48b83f61031c29ab4ff5168fccd2"], "groups"=>["ca0a8cabaafaae658edd298ddd4266cd", "690063dd87f110eabfa5ba387b8e280f"]}, "update"=>{"actors"=>["c8bd48b83f61031c29ab4ff5168fccd2"], "groups"=>["ca0a8cabaafaae658edd298ddd4266cd"]}, "delete"=>{"actors"=>["c8bd48b83f61031c29ab4ff5168fccd2"], "groups"=>["ca0a8cabaafaae658edd298ddd4266cd", "690063dd87f110eabfa5ba387b8e280f"]}, "grant"=>{"actors"=>["c8bd48b83f61031c29ab4ff5168fccd2"], "groups"=>["ca0a8cabaafaae658edd298ddd4266cd"]}}
+```
+
+#### Editing groups
+
+Groups can be viewed:
+```ruby
+fixie:0 > ORGS['ponyville'].groups['admins'].group
+{"actors"=>[[:global, "pivotal"]], "groups"=>[]}
+```
+
+Members can be added/removed from groups:
+```ruby
+fixie:0 > ORGS['ponyville'].groups['admins'].group_add(USERS['fluttershy'])
+{}
+fixie:0 > ORGS['ponyville'].groups['admins'].group_delete(USERS['fluttershy'])
+{}
+```
+
+Again there are raw functions that take raw authz ids.
+```ruby
+fixie:0 > ORGS['ponyville'].groups['admins'].group_raw
+{"actors"=>["c8bd48b83f61031c29ab4ff5168fccd2"], "groups"=>[]}
+```
+
+