This state allows for grains to be set.
Grains set or altered with this module are stored in the 'grains'
file on the minions, By default, this file is located at: /etc/salt/grains
Note
This does NOT override any grains set in the minion config file.
New in version 2014.7.0.
Delete a grain from the grains config file
The grain name
If destructive is True, delete the entire grain. If destructive is False, set the grain's value to None. Defaults to False.
If force is True, the existing grain will be overwritten regardless of its existing or provided value type. Defaults to False
New in version 2015.8.2.
A delimiter different from the default can be provided.
New in version 2015.8.2.
Changed in version 2015.8.2.
This state now support nested grains and complex values. It is also more conservative: if a grain has a value that is a list or a dict, it will not be removed unless the force parameter is True.
grain_name:
grains.absent
New in version 2014.7.0.
Append a value to a list in the grains config file. The grain that is being appended to (name) must exist before the new value can be added.
The grain name
The value to append
If convert is True, convert non-list contents into a list. If convert is False and the grain contains non-list contents, an error is given. Defaults to False.
A delimiter different from the default can be provided.
New in version 2015.8.2.
grain_name:
grains.append:
- value: to_be_appended
Ensure that a grain is set
The grain name
A delimiter different from the default can be provided.
Check whether a grain exists. Does not attempt to check or set the value.
Delete a value from a grain formed as a list.
New in version 2014.1.0.
The grain name.
The value to delete from the grain list.
A delimiter different from the default :
can be provided.
New in version 2015.8.2.
The grain should be list type
roles:
grains.list_absent:
- value: db
For multiple grains, the syntax looks like:
roles:
grains.list_absent:
- value:
- web
- dev
New in version 2014.1.0.
Ensure the value is present in the list-type grain. Note: If the grain that is
provided in name
is not present on the system, this new grain will be created
with the corresponding provided value.
The grain name.
The value is present in the list type grain.
A delimiter different from the default :
can be provided.
New in version 2015.8.2.
The grain should be list type
roles:
grains.list_present:
- value: web
For multiple grains, the syntax looks like:
roles:
grains.list_present:
- value:
- web
- dev
Ensure that a list grain is hashable.
The list grain that should be hashable
This function is recursive, so it must be possible to use a sublist as parameter to the function. Should not be used by a caller outside of the function.
Make it possible to compare two list grains to each other if the list contains complex objects.
Ensure that a grain is set
Changed in version 2015.8.2.
The grain name
The value to set on the grain
If force is True, the existing grain will be overwritten regardless of its existing or provided value type. Defaults to False
New in version 2015.8.2.
A delimiter different from the default can be provided.
New in version 2015.8.2.
It is now capable to set a grain to a complex value (ie. lists and dicts) and supports nested grains as well.
If the grain does not yet exist, a new grain is set to the given value. For a nested grain, the necessary keys are created if they don't exist. If a given key is an existing value, it will be converted, but an existing value different from the given key will fail the state.
If the grain with the given name exists, its value is updated to the new value unless its existing or provided value is complex (list or dict). Use force: True to overwrite.
cheese:
grains.present:
- value: edam
nested_grain_with_complex_value:
grains.present:
- name: icinga:Apache SSL
- value:
- command: check_https
- params: -H localhost -p 443 -S
with,a,custom,delimiter:
grains.present:
- value: yay
- delimiter: ','