Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
See issue #47590 for the original behavior. After this PR, the subject commands (
I do not believe this is eligible for backporting as it is removing module parameters which would break existing playbooks.
to solve the initial bug on the stable release you could make this code conditional such that if the remote does not support the non-standard features we give the user a nice error that says that these parameters cannot be used with this host.
It would also be nice for the users if you added a deprecation warning when they specify the parameters which are going away. That way they can start preparing to change their playbooks in the next release. (via module.deprecate(msg)).
I will work on a new PR that emits the suggested deprecation warning and a nice error in the case that the non-standard feature is not available.
Is the best/standard practice in this type of scenario to (1) keep this PR open and update it or (2) close this one and open a new one?