-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skip 403 Forbidden exception when getting node acl #519
base: master
Are you sure you want to change the base?
Conversation
…de_acl_forbidden_excp is true.
I was asked to confirm (on chef-success slack) that line 174 would still raise errors if it hit exception that wasn't 403. Unfortunately no test specs for chef-provisioning core gem right now (as I'd add a test here if there was a base of tests). I was however able to trigger a 404 error (using pry) on line 174 and the exception still raised.
|
I'm not sure why we need to fix the acls on enterprise/hosted chef in the first place. Is this because the default or global permissions are set to restrict read and update? Having said that, I'm averse to having a config flag for ignoring a 403. What about instead moving the flag to line 164 and not attempting to change permissions at all? My thought then is that when the node is initially created it can be done by a client with permissions. Then further resource invocations performed by a a restricted client with that config flag set. What do you think about that? |
Allows possibility that 2nd machine convergence could be done by a user that does not have grant permission on node object.