* Add 100% test coverage for the kubernetes.secret_absent state
* Add 100% coverage for kubernetes.node_label_present
* Also add 'comment' to kubernetes.node_add_label
* Make the faux test objects more believable in test_kubernetes.py
* Add 100% test coverage for the kubernetes.secret_present state
* Add 100% test coverage for the kubernetes.configmap_absent state
* Add 100% test coverage for the kubernetes.configmap_present state
* Make some fields optional to kubernetes.create_secret and add examples
* Make some fields optional to kubernetes.replace_secret and add examples
* Make some fields optional to kubernetes.create_configmap and add examples
* Make some fields optional to kubernetes.replace_configmap and add examples
* Add 'comment' when a kubernetes configmap or secret is going to be replaced
* Update 'source', 'template', and 'saltenv' kwargs to defaults from the rest of the codebase
* Allow passing empty 'data' to the kubernetes.configmap_present state to remove the existing contents
This commit splits _smartos_zone_data into 3 functions,
- _smartos_zone_data => zoneid, zonename, imageversion
- _smartos_zone_pkgsrc_data => pkgsrc related data for the zone
- _smartos_zone_pkgin_data => pkgin related data for the zone
PR #39103 ("fixes #31393 don't convert the iface to lower case")
change should also be applied for routes.
Fix both Debian and RHEL IP modules.
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
AArch64, ppc64 and ppc64le have network interfaces with uppercase
characters in their names, e.g. enP5p144s0.
PR #39103 ("fixes #31393 don't convert the iface to lower case")
fixed this issue, but only for RHEL systems. The same change is
required on Debian systems as well.
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
This allows the removal of the json module dependancy
NOTE: Not sure how the override of some unavailable smbios grains will
work when they are done in a seperate module. TIAS
At the time being, this engine considers only the events
starting with salt/job. That was a poor design decision,
as the user may have other interesting events on the Salt bus,
that don't necessarily belong to the Salt standard events.
Moreover, this was not in-line with the other TCP/UDP Logstash engine
https://github.com/saltstack/salt/blob/2017.7/salt/engines/logstash.py#L76
I also improved a little the documentation.
As per discussion in https://github.com/saltstack/salt/issues/40208 pchanges should be used for dry-run, it requires proper handling in the output module to correctly report changes to the user
