-
Notifications
You must be signed in to change notification settings - Fork 64
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
use_dns_ea_inheritance breaks versions <= 2.12.2 #288
Comments
Hi @commonism,
|
Why use use_dns_ea_inheritance when wapi version 2.12 is defined? |
Thanks for your question! For fields that need specific WAPI versions, make sure to specify the required WAPI version in your Ansible playbooks. As per the current design, we don't support backward compatibility to exclude fields that are not compatible with lower versions, so please ensure you're using the appropriate WAPI version. |
Having to specfiy the version number of the wapi version yields the expectation there is some compatibility with lower versions. For me, the required WAPI version is defined by the InfoBlox appliance. use_dns_ea_inheritance was introduced in v1.7.0 (https://github.com/infobloxopen/infoblox-ansible/releases/tag/v1.7.0) of this collection. Breaking backwards compatibility should be a major version when incrementing release numbers. |
Currently there is no workaround for the use of use_dns_ea_inheritance but downgrading to a version which does not use it.
infoblox-ansible/README.md
Line 248 in dcd53cf
It's a version dependent feature, would it be possible to limit the use to a wapi version >= 2.12.3?
The text was updated successfully, but these errors were encountered: