Thanks! I did include user “Jenkins” in the admin group, but liked this solution better so that is what I ended up doing. It is actually documented here
https://docs.chef.io/server_orgs.html, but I wish it was also documented here
https://docs.chef.io/server_orgs.html#push-jobs-title-groups Chris From: Mark Anderson [mailto:
Hi there.
So you will need to create the special group 'pushy_job_writers' and add your jenkins user to that group to get access. To examine the state of jobs you will need 'pushy_job_readers' membership. You can use either the manage console or the knife-acl plugin (https://github.com/chef/knife-acl) to create a group and add users. On Wed, Jan 28, 2015 at 12:15 PM, Fouts, Chris <
" target="_blank">
> wrote:
I got further along with setting up push job. Now when I try the start a push job on a node, I get this. How can I grant user “jenkins” access to this object? User “Jenkins” is not in the admins group, which is intentional.
NOTE: I can do other knife commands.
knife job start 'chef-client'
mynode.domain.com
ERROR: You authenticated successfully to
https://chef-server.domain.com/organizations/arq-dev as jenkins but you are not authorized for this action
Response: User or client 'jenkins' does not have access to that action on this server. From: Fouts, Chris [mailto:
" target="_blank">
]
https://docs.chef.io/install_push_jobs.html I’m trying to use Chef push for orchestrating my node configurations, and the best information I can find is in the above link. However, it’s still lack-luster. Is there a better
tutorial somewhere? (I’ve looked) For example, what does item #3 in above link mean? · Add the following default attributes on all nodes that are managed by Chef push jobs: "push_jobs": { "package_url": "<package_url>", "package_checksum": "<checksum>" } What is <package_url> and <checksum>, or where do I get those? Chris
--
Mark Anderson - Community Engineering |
Archive powered by MHonArc 2.6.16.