File manager - Edit - /opt/saltstack/salt/lib/python3.10/site-packages/salt/modules/__pycache__/napalm_formula.cpython-310.pyc
Back
o ;j=- � @ s� d Z ddlZddlZddlZddlZddlZddlmZ ddl m Z dgZ dZ e�e�Zdd� Zddefd d �Zddefd d �Zdefd d�Zdefdd�Zd dd�Zd dd�Zd dd�Zdd� ZdS ) a4 NAPALM Formula helpers ====================== .. versionadded:: 2019.2.0 This is an Execution Module providing helpers for various NAPALM formulas, e.g., napalm-interfaces-formula, napalm-bgp-formula, napalm-ntp-formula etc., meant to provide various helper functions to make the templates more readable. � N)�DEFAULT_TARGET_DELIM)�traverse_dict_and_list�*Znapalm_formulac C s t jj�ttt�S )z+ Available only on NAPALM Minions. )�salt�utilsZnapalmZvirtualZ__opts__�__virtualname__�__file__� r r �O/opt/saltstack/salt/lib/python3.10/site-packages/salt/modules/napalm_formula.py� __virtual__ s r c c sh � |sd}|s d}| � � D ]$\}}|r dj|||d�}n|}||kr&|V q t||||d�E dH q dS )zr Generate all the possible paths within an OpenConfig-like object. This function returns a generator. � Zconfigz{prev_key}{delim}{cur_key})Zprev_key�delimZcur_key)�key� containerr N)�items�format�_container_path)�modelr r r Z model_keyZ model_valueZ key_depthr r r r $ s" ����r c C s t t| ��S )a^ Return the list of all the possible paths in a container, down to the ``config`` container. This function can be used to verify that the ``model`` is a Python object correctly structured and respecting the OpenConfig hierarchy. model The OpenConfig-structured object to inspect. delim: ``:`` The key delimiter. In particular cases, it is indicated to use ``//`` as ``:`` might be already used in various cases, e.g., IPv6 addresses, interface name (e.g., Juniper QFX series), etc. CLI Example: .. code-block:: bash salt '*' napalm_formula.container_path "{'interfaces': {'interface': {'Ethernet1': {'config': {'name': 'Ethernet1'}}}}}" The example above would return a list with the following element: ``interfaces:interface:Ethernet1:config`` which is the only possible path in that hierarchy. Other output examples: .. code-block:: text - interfaces:interface:Ethernet1:config - interfaces:interface:Ethernet1:subinterfaces:subinterface:0:config - interfaces:interface:Ethernet2:config )�listr )r r r r r r r �container_path< s !r c C sV |si }|}| � |�}|dd� D ]}||vri ||< || }qt�|�||d < |S )a} Set a value under the dictionary hierarchy identified under the key. The target 'foo/bar/baz' returns the dictionary hierarchy {'foo': {'bar': {'baz': {}}}}. .. note:: Currently this doesn't work with integers, i.e. cannot build lists dynamically. CLI Example: .. code-block:: bash salt '*' formula.setval foo:baz:bar True N���)�split�copy�deepcopy)r �val�dict_r Z prev_hierZ dict_hierZeachr r r �setval` s r c C s t | |||d�S )a� Traverse a dict or list using a colon-delimited (or otherwise delimited, using the ``delimiter`` param) target string. The target ``foo:bar:0`` will return ``data['foo']['bar'][0]`` if this value exists, and will otherwise return the dict in the default argument. Function will automatically determine the target type. The target ``foo:bar:0`` will return data['foo']['bar'][0] if data like ``{'foo':{'bar':['baz']}}`` , if data like ``{'foo':{'bar':{'0':'baz'}}}`` then ``return data['foo']['bar']['0']`` CLI Example: .. code-block:: bash salt '*' napalm_formula.traverse "{'foo': {'bar': {'baz': True}}}" foo:baz:bar )�default� delimiter)�_traverse_dict_and_list)�datar r r r r r �traverse} s r! TFc C s t jjj| |||d�S )a# Recursive version of the default dict.update Merges upd recursively into dest If recursive_update=False, will use the classic dict.update, or fall back on a manual merge (helpful for non-dict types like ``FunctionWrapper``). If ``merge_lists=True``, will aggregate list object types instead of replace. The list in ``upd`` is added to the list in ``dest``, so the resulting list is ``dest[key] + upd[key]``. This behaviour is only activated when ``recursive_update=True``. By default ``merge_lists=False``. )�recursive_update� merge_lists)r r � dictupdate�update)�destZupdr" r# r r r r$ � s �r$ �//c C s i }t �d� t �|� t �d� t �| � t| |d�D ]=}t||d�D ]4}t �d||� t�||�rAt|�|��t|�|��ksBq$t �d||� t|||d�}t||||d�}q$q t �d� t �|� t �d � t �| � |rxtj j � | |�S tj j � || �S ) aC Apply the defaults to a Python dictionary having the structure as described in the OpenConfig standards. model The OpenConfig model to apply the defaults to. defaults The dictionary of defaults. This argument must equally be structured with respect to the OpenConfig standards. For ease of use, the keys of these support glob matching, therefore we don't have to provide the defaults for each entity but only for the entity type. See an example below. delim: ``//`` The key delimiter to use. Generally, ``//`` should cover all the possible cases, and you don't need to override this value. flipped_merge: ``False`` Whether should merge the model into the defaults, or the defaults into the model. Default: ``False`` (merge the model into the defaults, i.e., any defaults would be overridden by the values from the ``model``). CLI Example: .. code-block:: bash salt '*' napalm_formula.defaults "{'interfaces': {'interface': {'Ethernet1': {'config': {'name': 'Ethernet1'}}}}}" "{'interfaces': {'interface': {'*': {'config': {'enabled': True}}}}}" As one can notice in the example above, the ``*`` corresponds to the interface name, therefore, the defaults will be applied on all the interfaces. zApplying the defaults:zopenconfig like dictionary:)r zComparing %s to %sz %s matches %s)r )r r zComplete default dictionaryzMerging with the model) �log�debugr �fnmatch�lenr r r r r r$ r% )r Z defaults_r Z flipped_mergeZmergedZ model_pathZ default_pathZ devault_valr r r �defaults� s6 # � ��� r, c K sh t | |�}|du r dS |du r|�dd�}|du r$td dv r"d}nd}|r,d|� d�}d j|||d �S ) aZ Render a field found under the ``field`` level of the hierarchy in the ``dictionary`` object. This is useful to render a field in a Jinja template without worrying that the hierarchy might not exist. For example if we do the following in Jinja: ``{{ interfaces.interface.Ethernet5.config.description }}`` for the following object: ``{'interfaces': {'interface': {'Ethernet1': {'config': {'enabled': True}}}}}`` it would error, as the ``Ethernet5`` key does not exist. With this helper, we can skip this and avoid existence checks. This must be however used with care. dictionary The dictionary to traverse. field The key name or part to traverse in the ``dictionary``. prepend: ``None`` The text to prepend in front of the text. Usually, we need to have the name of the field too when generating the configuration. append: ``None`` Text to append at the end. quotes: ``False`` Whether should wrap the text around quotes. CLI Example: .. code-block:: bash salt '*' napalm_formula.render_field "{'enabled': True}" enabled # This would return the value of the ``enabled`` leaf key salt '*' napalm_formula.render_field "{'enabled': True}" description # This would not error Jinja usage example: .. code-block:: jinja {%- set config = {'enabled': True, 'description': 'Interface description'} %} {{ salt.napalm_formula.render_field(config, 'description', quotes=True) }} The example above would be rendered on Arista / Cisco as: .. code-block:: text description "Interface description" While on Junos (the semicolon is important to be added, otherwise the configuration won't be accepted by Junos): .. code-block:: text description "Interface description"; Nr �_�-�os)Zjunos�;�"z{prepend} {value}{append})�prepend�value�append)r! �replaceZ __grains__r )� dictionary�fieldr2 r4 �quotes�optsr3 r r r � render_field� s : �r: c O sl g }|D ]}t | |fi |��}|r|�|� qd|vr d|d< d|vr/djd|d d�|d< |d �|�S )a This function works similarly to :mod:`render_field <salt.modules.napalm_formula.render_field>` but for a list of fields from the same dictionary, rendering, indenting and distributing them on separate lines. dictionary The dictionary to traverse. fields A list of field names or paths in the dictionary. indent: ``0`` The indentation to use, prepended to the rendered field. separator: ``\n`` The separator to use between fields. CLI Example: .. code-block:: bash salt '*' napalm_formula.render_fields "{'mtu': 68, 'description': 'Interface description'}" mtu description Jinja usage example: .. code-block:: jinja {%- set config={'mtu': 68, 'description': 'Interface description'} %} {{ salt.napalm_formula.render_fields(config, 'mtu', 'description', quotes=True) }} The Jinja example above would generate the following configuration: .. code-block:: text mtu "68" description "Interface description" �indentr � separatorz {ind}� )�ind)r: r4 r �join)r6 �fieldsr9 �resultsr7 �resr r r � render_fields- s ' �rC )TF)r' F)NNF)�__doc__r r* �loggingZsalt.utils.dictupdater Zsalt.utils.napalmZ salt.defaultsr Zsalt.utils.datar r Z__proxyenabled__r � getLogger�__name__r( r r r r r! r$ r, r: rC r r r r �<module> s( $ > K
| ver. 1.4 |
Github
|
.
| PHP 8.2.30 | Generation time: 0 |
proxy
|
phpinfo
|
Settings