Fix(plugins): Prevent deprecation warnings when deprecated filters are not used #4199
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Summary
in 4.9.0 3 filters have been deprecated to be removed in 5.0.0
When running AVD and not using the filters in the playbook, users sees the deprecation warnings and they cannot do anything about it. This is because of the way ansible loads filters. A workaround has been found in this PR where all the deprecated filters are grouped in the same python file and the documentation is kept on the side.
Related Issue(s)
Fixes issue reported on slack and in the field
Component(s) name
plugins
Proposed changes
cf summary +
How to test
when running in molecule no more warnings.
Checklist
Repository Checklist