%PDF- %PDF-
Direktori : /usr/lib/python2.7/site-packages/salt/renderers/ |
Current File : //usr/lib/python2.7/site-packages/salt/renderers/py.pyc |
� ���^c @@ s` d Z d d l m Z m Z m Z d d l Z d d l m Z d d l Z d d d d � Z d S( u� Pure python state renderer ========================== To use this renderer, the SLS file should contain a function called ``run`` which returns highstate data. The highstate data is a dictionary containing identifiers as keys, and execution dictionaries as values. For example the following state declaration in YAML: .. code-block:: yaml common_packages: pkg.installed: - pkgs: - curl - vim tranlastes to: .. code-block:: python {'common_packages': {'pkg.installed': [{'pkgs': ['curl', 'vim']}]}} In this module, a few objects are defined for you, giving access to Salt's execution functions, grains, pillar, etc. They are: - ``__salt__`` - :ref:`Execution functions <all-salt.modules>` (i.e. ``__salt__['test.echo']('foo')``) - ``__grains__`` - :ref:`Grains <targeting-grains>` (i.e. ``__grains__['os']``) - ``__pillar__`` - :ref:`Pillar data <pillar>` (i.e. ``__pillar__['foo']``) - ``__opts__`` - Minion configuration options - ``__env__`` - The effective salt fileserver environment (i.e. ``base``). Also referred to as a "saltenv". ``__env__`` should not be modified in a pure python SLS file. To use a different environment, the environment should be set when executing the state. This can be done in a couple different ways: - Using the ``saltenv`` argument on the salt CLI (i.e. ``salt '*' state.sls foo.bar.baz saltenv=env_name``). - By adding a ``saltenv`` argument to an individual state within the SLS file. In other words, adding a line like this to the state's data structure: ``{'saltenv': 'env_name'}`` - ``__sls__`` - The SLS path of the file. For example, if the root of the base environment is ``/srv/salt``, and the SLS file is ``/srv/salt/foo/bar/baz.sls``, then ``__sls__`` in that file will be ``foo.bar.baz``. When writing a reactor SLS file the global context ``data`` (same as context ``{{ data }}`` for states written with Jinja + YAML) is available. The following YAML + Jinja state declaration: .. code-block:: jinja {% if data['id'] == 'mysql1' %} highstate_run: local.state.apply: - tgt: mysql1 {% endif %} translates to: .. code-block:: python if data['id'] == 'mysql1': return {'highstate_run': {'local.state.apply': [{'tgt': 'mysql1'}]}} Full Example ------------ .. code-block:: python :linenos: #!py def run(): config = {} if __grains__['os'] == 'Ubuntu': user = 'ubuntu' group = 'ubuntu' home = '/home/{0}'.format(user) else: user = 'root' group = 'root' home = '/root/' config['s3cmd'] = { 'pkg': [ 'installed', {'name': 's3cmd'}, ], } config[home + '/.s3cfg'] = { 'file.managed': [ {'source': 'salt://s3cfg/templates/s3cfg'}, {'template': 'jinja'}, {'user': user}, {'group': group}, {'mode': 600}, {'context': { 'aws_key': __pillar__['AWS_ACCESS_KEY_ID'], 'aws_secret_key': __pillar__['AWS_SECRET_ACCESS_KEY'], }, }, ], } return config i ( t absolute_importt print_functiont unicode_literalsN( t SaltRenderErroru baseu c K@ s� | } t j j | � s0 t d j | � � � n t j j j | t d t d t d t d t d t d t d t d t d | d | d | d | | �} | j d t � s� t | j d d � � � n | d S( uC Render the python module's components :rtype: string u Template {0} is not a file!t __salt__t saltt __grains__t grainst __opts__t optst __pillar__t pillart __env__t saltenvt __sls__t slsu resultu datau# Unknown render error in py renderer( t ost patht isfileR t formatR t utilst templatest pyt TrueR R R R t gett False( t templateR R t tmplpatht kwst tmp_data( ( s5 /usr/lib/python2.7/site-packages/salt/renderers/py.pyt render{ s. ( t __doc__t __future__R R R R t salt.exceptionsR t salt.utils.templatesR t NoneR ( ( ( s5 /usr/lib/python2.7/site-packages/salt/renderers/py.pyt <module>p s