* create zone state, zone.running, and zone.stopped
* renamed zone.running and zone.stopped, minor lint fixes
* cleanup message in zonecfg to make it clear for the zone state
* zone.property_present state
* zonecfg.set_property - should handle true/false parsed as boolean
* zonecfg module should be more consistant with message
* zone.property_absent implemented
* fix more minor issues in zonecfg when values get parsed as bool
* zonecfg fix spelling error
* improved zonecfg error message handling
* zonecfg parser should also do the reverse
* more improvements in zonecfg for parsing values
* small tweak to zonecfg simplyfy code for the zone state
* Add resource_present to zone state
* zonecfg lint fixes
* resource_absent state, lint fixed, test support
* zonecfg should be a bit more careful when removing the exported config
* zone.export state
* zone.import state
* zone.absent implemented
* zone.attached and zone.detached implemented
* very minor consistency fixes
* added zone.installed and zone.uninstalled, made zone.detached and zone.halted not fail on missing zone
* handle bool values in _parse_value
* add useful cleanup internal function to zonecfg
* zonecfg - cleaned up _parse_value, added _sanitize_value and _dump_cfg for debugging
* zone.absent - uninstall would sometimes not do the right thing. some work on zone.present
* zone.present implemented path for when config does not yet exist
* zone.present supports updating properties
* zonecfg should support resources that do not have selectors
* zonecfg should also debug log remove_resource its config
* zone.present - implemented, after 2 refactors
* Finish documentation
* Apply fix from #38705 to 2016.3 branch
This is a better fix and covers more use cases than the sudo_user one.
* Remove saltenv param from internal state func call
This was probably redundant in the first place, but since state.sls,
state.highstate, etc. accept a saltenv param and the actual state
functions do not, this results in multiple values passed for the saltenv
param.
Remove this argument and let file.get_managed reference __env__
internally.
* Update archive tests to match 2016.11 branch
The IDE entry needs to be a dictionary entry. Without this, it is seen
as a string. This is probably done this way so that in the future,
configurations can be added to the IDE device.
needed to be made. The /etc/selinux/config file could have a different value, and it would not be changed. This commit
enhances idempotency of the state in regards to both the in-memory and configuration file enforcement of SELinux.
This keeps trimmed output from failing the test. We are still testing
with a specific module lower down in the test, so this doesn't reduce
our test coverage.
This test fails often due to being trimmed, thanks to
salt.utils.dicttrim trimming values > max_event_size.
This commit changes this test so that it runs sys.doc twice, ensuring
that the return from sys.doc (for now) is not trimmed.
Stabilizes these tests by avoiding errors when cheese, crackers
order changes in the comment and gives errors like:
- 'comment': 'Kernel modules crackers, cheese are already present',
? --------
+ 'comment': 'Kernel modules cheese, crackers are already present',
? ++++++++
