Calls the master for a fresh pillar and generates the pillar data on the fly Contrast with :py:func:`raw` which returns the pillar data that is currently loaded into the minion. pillar If specified, allows for a dictionary of pillar data to be made available to
(
*args, pillar=None, pillar_enc=None, pillarenv=None, saltenv=None, unmask=None
)
| 207 | |
| 208 | |
| 209 | def items( |
| 210 | *args, pillar=None, pillar_enc=None, pillarenv=None, saltenv=None, unmask=None |
| 211 | ): |
| 212 | """ |
| 213 | Calls the master for a fresh pillar and generates the pillar data on the |
| 214 | fly |
| 215 | |
| 216 | Contrast with :py:func:`raw` which returns the pillar data that is |
| 217 | currently loaded into the minion. |
| 218 | |
| 219 | pillar |
| 220 | If specified, allows for a dictionary of pillar data to be made |
| 221 | available to pillar and ext_pillar rendering. these pillar variables |
| 222 | will also override any variables of the same name in pillar or |
| 223 | ext_pillar. |
| 224 | |
| 225 | .. versionadded:: 2015.5.0 |
| 226 | |
| 227 | pillar_enc |
| 228 | If specified, the data passed in the ``pillar`` argument will be passed |
| 229 | through this renderer to decrypt it. |
| 230 | |
| 231 | .. note:: |
| 232 | This will decrypt on the minion side, so the specified renderer |
| 233 | must be set up on the minion for this to work. Alternatively, |
| 234 | pillar data can be decrypted master-side. For more information, see |
| 235 | the :ref:`Pillar Encryption <pillar-encryption>` documentation. |
| 236 | Pillar data that is decrypted master-side, is not decrypted until |
| 237 | the end of pillar compilation though, so minion-side decryption |
| 238 | will be necessary if the encrypted pillar data must be made |
| 239 | available in an decrypted state pillar/ext_pillar rendering. |
| 240 | |
| 241 | .. versionadded:: 2017.7.0 |
| 242 | |
| 243 | pillarenv |
| 244 | Pass a specific pillar environment from which to compile pillar data. |
| 245 | If not specified, then the minion's :conf_minion:`pillarenv` option is |
| 246 | not used, and if that also is not specified then all configured pillar |
| 247 | environments will be merged into a single pillar dictionary and |
| 248 | returned. |
| 249 | |
| 250 | .. versionadded:: 2016.11.2 |
| 251 | |
| 252 | saltenv |
| 253 | Included only for compatibility with |
| 254 | :conf_minion:`pillarenv_from_saltenv`, and is otherwise ignored. |
| 255 | |
| 256 | unmask |
| 257 | If set to ``True``, the pillar data will be unmasked. |
| 258 | |
| 259 | .. versionadded:: 3008.0 |
| 260 | |
| 261 | CLI Example: |
| 262 | |
| 263 | .. code-block:: bash |
| 264 | |
| 265 | salt '*' pillar.items |
| 266 | """ |
no test coverage detected