Michael Pardatscher

> PR above should fix now Cool, thanks! :D Do you already know when this fix will be released for 2.17?

@bcoca is the fix still being worked on? Just noticed the PR seems to be stale since almost a year.

> If there are no objections I'll close this ticket in the next few days. I believe all the variables/settings mentioned in this ticket are now supported, and the surveryed...

Chiming in, I don't even get pings through to `registry-1.docker.io`. Even tried with all v6 addresses I get by doing an `nslookup`: ``` ~$ nslookup registry-1.docker.io Server: 127.0.0.53 Address: 127.0.0.53#53...

> [@MPStudyly](https://github.com/MPStudyly) are you using a VPS? I know some put in blocks at the provider level until we sorted our IPv6 rate limiting Nope, this affects all hosts, be...

> Nvm - we actually disable ping on this endpoint, so this is expected. Damn, then my test was useless :/ any other things I could try to pinpoint this,...

Any progress on this fix? The previous change just blew up our play, as we heavily rely on keep_keys to work as expected. Seeing how breaking code was merged within...

@gaelgatelement @roverflow any update on this? We're still stuck on v5.1.0 of this collection due to this change in behavior :/

> Unfortunately I'm now lacking the time to implement the non-greedy version. Sad to hear :( > Surely it's about keeping both `keep_keys` methods and adding a flag to use...

> Get the lists you want to transform and map the filter > > ```yaml > t: [key_in_list, other] > rl: "{{ testvar | > map(attribute='list_of_dicts') | > map('community.general.keep_keys', target=t)...