chef-workstation
chef-workstation copied to clipboard
Chef Workstation gives you everything you need to get started with Chef, so you can automate how you audit, configure, and manage applications end environments.
# Description Policyfiles no longer use the gecode solver, and Berks can optionally use molinillo. The reason we still have the gecode solver is because it's used in the Chef...
## Description After installing chefdk knife command takes more than two minutes to finish run ## Chef Workstation Version ## Platform Version It happens only in windows OS --all
### Describe the Enhancement: We don't want our `chef` top-level wrapper to depend on the system `PATH` to call the underlying sub-binaries. Perhaps we can hard-code the expected omnibus paths...
### Describe the Enhancement: Right now after installing Workstation you get a link on your desktop "CW PowerShell". It has the standard PowerShell icon and indicates in no way it's...
On Workstation 0.12 I get the following error when launching the workstation powershell console on my corp locked down Windows 10 box: ``` Import-Module : File C:\opscode\chef-workstation\modules\chef\chef.psm1 cannot be loaded...
### Describe the Enhancement: Ability to set the starting directory used by CW Workstation. Currently it uses C:\Windows\System32 ### Describe the Need: All users would benefit ### Current Alternative Manually...
## Description Within the policy.lock.json (created during "install .\Policyfile.rb") chef symbols like Time.now.utc are already replaced. If the policy file contains something like this: > default['production']['base']['message'] = "This node was...
# Description Users with custom `~/.gemrc` files may clobber the flags set in `OPERATING_SYSTEM_DEFAULTS`. In [operating_system.rb:6](https://github.com/chef/chef-dk/blob/75ecb686077ba901896f0b77194da94c2830cf2e/omnibus/files/rubygems-customization/default/operating_system.rb#L6-L8) there are the following two lines: ``` rb # Always install and update new...
# Description `chef exec rspec` is not able to function due to it trying to make connections to 127.0.0.1 through our HTTP proxy, because it shouldn't be doing that. It...
We have a great extension, but it doesn't auto install. We should install it as part of the workstation installer