This repository has been archived by the owner on Jul 14, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 170
Chef diff trying to use native endpoints in compatability mode #367
Comments
Enabling debug output, it looks like it is trying to use the native API even though I have compatibility mode enabled.
|
tyler-ball
changed the title
Chef diff fails to diff two policy groups that are on the chef server
Chef diff trying to use native endpoints in compatability mode
Apr 30, 2015
Closing as wont-fix. Diffing is only supported on native endpoints. |
I've run into the similar issue, with the same output. But the reason was the fact that I haven't specified organization name in It was: chef_server_url "https://chef.example.com/" But it should be: chef_server_url "https://chef.example.com/organizations/my_org_name" I hope it will help somebody :) P.s. However, all other endpoints (nodes, cookbooks) worked fine without organization mentioning. Only policy-related queries failed. |
ksubrama
pushed a commit
that referenced
this issue
Jan 11, 2016
Updated Test Kitchen with first-class Windows support
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I successfully uploaded my local policyfile (in compatablity mode) with
chef push one
. Then I modified the Policyfile.rb, updated the lock and uploaded it again withchef push two
. Runningchef diff one...two
raises the following errors:This is the bug I'm filing for the issue that my policyfile was successfully uploaded twice, but the diff command fails to find the groups. It fails in the same way if I run
chef diff one
and try to diff the local lock to theone
policy group.The text was updated successfully, but these errors were encountered: