Open TomKemperNL opened 7 years ago
Nope, it wasn't gone. I just retested with Chef Client 13.2.20 while it was still commented out.
Furthermore a colleague of mine has the same problem on Ubuntu 16.
This is probably caused by the fact that notify :before triggers a why-run. However action :put will call set_put_paths during both the real and the why-run, joining the resource name onto the path twice.
I'm somewhat concerned by the complete silence. Is there something wrong with the issue? Is there anything I can do to help? Is everyone just on summer vacation?
I just faced the very same issue on one of my projects, corrected it and saw this 2-year old ticket. I submitted a PR with modifications to support the why-run mode and correct the problem described here. Hopefully it will be accepted...
I'm also affected by exactly this bug.
I'm notifying another resource with the :before timing which seems to confuse ark and have the root dictionary doubled. Without the notify it works as expected.
Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs.
Closing due to inactivity. If this is still an issue please reopen or open another issue. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs.
I need to check if this is still a bug, but I highly suspect it is!
Cookbook version
3.1.0
Chef-client version
12.19.36
Platform Details
Windows 10 (15063)
Scenario:
Combining the ark resource :put action with notifies
Steps to Reproduce:
My resource is declared like
Expected Result:
I would expect the zip to be expanded to C:/Temp/app_test
Actual Result:
The zip is expanded to C:/Temp/app_test/app_test. If I comment out the notifies property, it works correctly. If I only use notified :immediate or :delayed, it works correctly