Kirill Shirinkin
Kirill Shirinkin
No interest in this feature still? For larger installations pulling all of the hosts every time is very slow. Filtering is a must in such cases.
More broad question: how good is chef-provisioning(-aws) at handling changes in resources? It is pretty clear how it works with normal chef resources (files, templates, directories), but here we are...
Okay, I see, so this feature is not implemented :) I guess you could add on a roadmap tasks to add "update" action to all resources, machien_image would be first...
@tyler-ball is it being worked on?
@tyler-ball I'd like to work on it then. Should I do it with aws dk v1 or v2? What is master branch targeted to?
@tyler-ball I've created a PR, currently still work in progress, but roles and instance profiles are there: https://github.com/chef/chef-provisioning-aws/pull/343
`-l debug` sounds like a reasonable solution in my situation. There is even a simpler (but less useful than full log) solution: to use chef reports. Then you will get...
@keen99 what I meant was this: https://docs.chef.io/reporting.html Still good to have this reporting
@jkeiser awesome, thanks!
@keen99 @jkeiser So, actually neither of two solutions work: 1. `-l debug` on provisioner node shows lots of, well, debug information, but still doesn't output any logs from clients that...