-
Notifications
You must be signed in to change notification settings - Fork 168
chef generate cookbook
should not require elevated privileges on Windows
#109
Comments
Hrmmm.. We might be surfacing a wrong error here @tknerr. Here we are catching all the win32 API errors and surfacing a Can you share the output of |
/cc: @adamedx |
I have this problem too. Here is my output from what was requested.
Running as administrator is successful. This is fine for me at home. At work I'm not sure if that would be an option... |
@sersut error seems appropriate looking at the code you referenced. If you look at the definition of the Assuming |
@sersut @jasonberanek no clue about the windows ACLs, but this is what
|
@sersut confirmed the behavior described and error message on Windows 7 (attached to corporate network) and Windows 8 (default installation in a VM) environments. Default settings for "User Access Policy", which enforces explicit acknowledgement when elevating privileges to execute an protected actions, result in the command failing by default for any user other than I personally don't have a push to get this fixed, just trying to provide information. Understand that addressing this requires either modifying the way the |
I also experienced this issue. Even If this is going to take a while to fix, would it be possible to:
I assume these changes are easier to make than the fix, and would definitely make the experience more 'delightful' in the meantime :) |
I'm looking into fixing the underlying way that we access the files, but the error message seems pretty good to me in the interim:
|
@btm As @ThomWright said, I'd recommend something in the Chef-DK documentation that specifies this is as a known issue. When I first went to test this, I didn't expect the |
|
Utilizing atomic file updates (via Chef, e.g. templates) means needing Administrator permissions to read the SACL from files. While we expect chef-client to be run as Administrator or with equivlanet permissions, we expect chef-dk (chef) to be run as a regular user. Even when logged in as an Administrator, you need to be running your shell with elevated privileges for atomic file updates to work. Fixes #109.
Utilizing atomic file updates (via Chef, e.g. templates) means needing Administrator permissions to read the SACL from files. While we expect chef-client to be run as Administrator or with equivlanet permissions, we expect chef-dk (chef) to be run as a regular user. Even when logged in as an Administrator, you need to be running your shell with elevated privileges for atomic file updates to work. Fixes #109.
installp command on AIX needs an additional parameter
Just tried
chef cookbook generate foo
on my Win7 laptop with ChefDK 0.2.0, but it failed with this error:IMHO generating a cookbook should not require admin privileges.
The text was updated successfully, but these errors were encountered: