-
Notifications
You must be signed in to change notification settings - Fork 19
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
ChefDK gets installed on every Chef run #56
Comments
for debian/ubuntu anyway, you can pass the --skip-same-version option to dpkg. Just gotta find similar settings for others... |
or have the remote_file resource notify the package resource so it only runs the package install when remote_file is run for a new download. |
this is really a nasty issue. |
I just ended up doing this:
|
We've just encountered this too. The one side-effect of this is that /usr/bin/chef disappears and then re-appears every time chef runs:
|
To chime in, sometimes the installation fails randomly, causing all the binary symlinks to disappear... Does anyone have a proper workaround for this without fixing the version? |
I am trying this, which seems like it does the right thing (but it's a little bit fragile), basically:
|
I like the idea! I tried something similar, but with ruby code instead because it feels a bit more right to me:
I tried to pass Regardless, this seems to achieve what's needed. |
The cookbook currently installs ChefDK on every Chef run. In our env where chef runs as a daemon, this means a
dpkg -i /var/chef/cache/chefdk_0.10.0-1_amd64.deb
every half hour. The cookbook needs a check to see if the requested version is already installed, or if latest > installed version.The text was updated successfully, but these errors were encountered: