Fix #10287 network.ip_address don't recognize interfaces with dashes in it's name
Add option in reg state and module to disable reflection on Windows 64-bit.
lint fixes
postgres_users: report changes when user is created
rename map.py to diff.py, sort minions within a pool, more clear output format
Add comment about importance of empty line
Remove extraneous UTF8 coding line
[salt] add a state to make sure the system is uptodate
[salt] clean up and document

clean up for pep8 and document uptodate
Be more explicit in the pacman module

If we are going to be more explicit, we should be more explicit
throughout the entire thing.  From issue 10519.
Minor tweaks to new pkg.uptodate state

2 minor changes:

1. Moved state function up above mod_init(). This is just for
   consistency across the codebase, mod_init() typically just appears at
   the bottom of the .py file (and if it's not there it probably should
   be).

2. Used a versionadded RST directive to note that this state is not yet
   available, as our automated docs builds will otherwise make it seem
   like this state is available for immediate use once your pull request
   is merged upstream.
More mac_user tests
Update diff.py
Solaris/SmartOS: Handle services in maintenance

SMF has a concept of the maintenance state where the
system knows the service is broken which requires an
explicit "svcadm clear <service>"

"svcadm enable -s <service>" returns code 3 when the service
is in maintenance (-s means wait to see how enabling went)

Salt should notice a return code of 3, attempt to clear
the service and try to enable one more time.

Common use case is a broken configuration file.
The user pushes a fix to the config file with salt which should
clear the maintenance state and attempt to enable the service
again.
modules/smf.py: pylint fixes / cleanup
SmartOS/Solaris: fix SMF service management

fixes saltstack/salt#10702

The functions previously named get_enabled and get_disabled
actually only queried what services were running or not

This caused breakages where a state that both requested
"enabled" and "running" could cause salt to start the
service which would make it appear in the list of
enabled services, but not actually get enabled
and thus not actually come back up on reboot

Those functions have been renamed to get_running
and get_stopped

An accurate enabled function has been written
which queries the true property that determines
if a service will come up at boot
and disabled returns its negation.

New get_enabled and get_disabled functions have
also been written which accurately return the
list of enabled or disabled services
Those functions return full FMRIs (rather than the
much shorter 'SVC' column) because that's how
SMF actually works internally.
Not verbose by default

Removing the tar verbose (`-v`) by default, still could be used if wanted on `tar_options`.
Support multiline cron comments

This fixes #10721.
integration stuff
Merge pull request #10708 from otrempe/develop

Add option in reg state and module to disable reflection on Windows 64-b...