Add ACL support to Objects

[reset]

OHC/OPC supports ACLs for

• clients
• groups
• containers
• data
• nodes
• roles
• cookbooks
• sandboxes
• environments

We should allow read/writing of these ACLs on the ChefObject level. The API seems to be undocumented but here is a Knife plugin which implements the API.

[sethvargo]

From Steven:

Not that I know of. I remember finding some design docs on the internal wiki when writing the knife acl subcommands, but for the most part I just used the merb router and lb configs as my documentation. The pedant tests might be a good place to start if someone was going to write them:

https://github.com/opscode/oc-chef-pedant/tree/master/spec/api/account

There are a few more endpoints that are used in knife-opc, but I don't think those would be too useful to the ridley.

[bmhatfield]

Bump on this by any chance? The ACL system in Chef 12 is causing lots of problems, and I'd like to fix them on-demand with Ridley :-)

[thommay]

@bmhatfield can you define what you actually need? Just the ability to manage ACls with ridley, or is there something deeper?

[bmhatfield]

Sorry for the delay. Just looking for the ability to manage ACLs with Ridley.

[lamont-granquist]

I think the reality is that ridley is becoming community supported at this point, and without a PR to implement some of these features, we're more likely to be spending time on fixing Chef::HTTP bugs than improving ridley. I can't see where the time comes from anyone who is currently keeping ridley running to implement these features, I can certainly think of several Chef RFCs I need to implement and several dozen chef/chef features and bugs that would take priority. The best way to get us to reassess our priorities here will be to give us a green merge button to mash.

[lamont-granquist]

We're also mostly trying to address berkshelf-related issues in ridley. Since berks doesn't need any of these APIs their priority in implementing is so low as to be queue starved.