[chef] RE: Re: Re: RE: Re: RE: Re: Chef Server API Call and Docs

[Daniel Klopp < >]

Thanks!  I looked at the 800MB doc directory and was a tad intimidated.

I'll submit an issue with example code in the next day or two.

-Dan

---

From: James Scott
Sent: Tuesday, November 18, 2014 10:25 AM
To:
Subject: [chef] Re: Re: RE: Re: RE: Re: Chef Server API Call and Docs

I added a quick warning yesterday based on this thread. The pivotal user is required for the following endpoints:

/organizations

/users

I would love it if you could send me a usage example for polling the server. Please send it to " target="_blank"> and I'm happy to do the backend work in the chef-docs repo to get it added to the docs collection. A github issue or PR is fine, of course, if you prefer those routes.

james

On Mon, Nov 17, 2014 at 6:53 PM, Julian C. Dunn < " target="_blank"> > wrote:

On Mon, Nov 17, 2014 at 7:28 PM, Daniel Klopp < " target="_blank"> > wrote:

Mark,

Thanks, that worked great.  I was able to create an organization.

Where can I fork the docs or submit a doc update request?  I feel that the pivotal user should be mentioned as a requirement to using the API calls.  Also it might be helpful to have an actual configuration example for polling the server, as for most of the details I was left to finding third party websites for help.  As it stands now, https://docs.getchef.com/api_chef_server.html lacks those details.

Hi Daniel,

The docs are all reStructuredText over at https://github.com/opscode/chef-docs. If you know RST you can submit a patch, otherwise just put in a GitHub issue.

- Julian

--

[ Julian C. Dunn < " target="_blank"> >          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]

This communication is Confidential Information. By using this message and attachments you implicitly consent to terms and conditions set forth at http://www.taos.com/email_disclaimer. If you do not consent or received this message in error, please destroy it.