win_reg_stat: Clean up parameter handling

[dagwieers]

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

win_reg_stat

ANSIBLE VERSION

v2.3

SUMMARY

Only minor changes.

[ansibot]

cc @jborean93
click here for bot help

[jborean93]

I take it you don't need to add the warnings to the return result?

shipit

[dagwieers]

I didn't see any warnings. But if you would need to "escalate" warnings, we now have Add-Warning and Add-DeprecationWarning functions that will add the required entry as part of the call. So it shouldn't be needed in the standard $result hash.

PS We also ensured that empty warnings in the output is properly cleaned up, so it's not a real problem anymore ;-)

[ansibot]

@SamLiu79 @timothyvandenbrande @blakfeld @brianlloyd @chrishoffman @jborean93 @joshludwig @petemounce @schwartzmx @smadam813 @WHenrik

The win_reg_stat module has only one maintainer and this request needs 2 shipits. As a maintainer of a module in the same namespace, you can add a shipit to help move this request along.

click here for bot help

[jhawkesworth]

shipit

[jhawkesworth]

bot_status

[ansibot]

waiting_on: maintainer
module: win_reg_stat
supported_by: community
maintainers: jborean93
changes_requested_by: null
needs_info: False
needs_revision: False
needs_rebase: False
merge_commits: []
mergeable_state: clean
shippable_status: success
maintainer_shipits: 1
community_shipits: 0
ansible_shipits: 1
shipit_actors: jborean93 jhawkesworth

click here for bot help

[dagwieers]

ready_for_review