Closed kyokley closed 2 months ago
Thank you very much. I will have a look later this day. Most likely, I will adjust the code so as to handle both Ansible >= 2.17 and Ansible < 2.17 (we cannot assume that everyone is always running the latest version of Ansible).
However, I'm guessing that since Ansible moved proxy_display under Display and renamed it to _proxy, it may not be safe to depend on it 🤷
Indeed, the leading _
reflects this decorator should be considered private. We can still use it though, provided we accept the burden of updating Moulti each time this private decorator changes in a breaking way.
Thank you very much. I will have a look later this day. Most likely, I will adjust the code so as to handle both Ansible >= 2.17 and Ansible < 2.17 (we cannot assume that everyone is always running the latest version of Ansible).
Ah, right, of course. Feel free to close this.
By the way, the output looks really nice. Thanks for the plugin!
I am going to squash, edit and merge your changes manually and close this pull request. My changes are merely boilerplate (changelog, documentation, comments). Of course, you remain the author of the resulting commit.
This issue prompted me to test Moulti against multiple versions of ansible. Here are the results:
ERROR! Unexpected Exception, this is probably a bug: type object 'Display' has no attribute '_proxy'
ERROR! Unexpected Exception, this is probably a bug: type object 'Display' has no attribute '_proxy'
I will check later whether Moulti can afford to support ansible-core 2.14 (even though it is EOL) and 2.15.
I think this fixes #7. At the very least, I was able to get it to run. However, I'm guessing that since Ansible moved
proxy_display
underDisplay
and renamed it to_proxy
, it may not be safe to depend on it 🤷