File manager - Edit - /opt/saltstack/salt/lib/python3.10/site-packages/salt/pillar/__pycache__/consul_pillar.cpython-310.pyc
Back
o ;jl. � @ s� d Z ddlZddlZddlZddlZddlmZ ddlm Z zddl Z e e d�s+de _ W n ey7 dZ Y nw dZe�e�Zdd � Zd d � Zd d � Zdd� Zdd� Zdd� Zdd� ZdS )a7 Use Consul K/V as a Pillar source with values parsed as YAML :depends: - python-consul In order to use an consul server, a profile must be created in the master configuration file: .. code-block:: yaml my_consul_config: consul.host: 127.0.0.1 consul.port: 8500 consul.token: b6376760-a8bb-edd5-fcda-33bc13bfc556 consul.scheme: http consul.consistency: default consul.dc: dev consul.verify: True All parameters are optional. The ``consul.token`` requires python-consul >= 0.4.7. If you have a multi-datacenter Consul cluster you can map your ``pillarenv`` entries to your data centers by providing a dictionary of mappings in ``consul.dc`` field: .. code-block:: yaml my_consul_config: consul.dc: dev: us-east-1 prod: us-west-1 In the example above we specifying static mapping between Pillar environments and data centers: the data for ``dev`` and ``prod`` Pillar environments will be fetched from ``us-east-1`` and ``us-west-1`` datacenter respectively. In fact when ``consul.dc`` is set to dictionary keys are processed as regular expressions (that can capture named parameters) and values are processed as string templates as per PEP 3101. .. code-block:: yaml my_consul_config: consul.dc: ^dev-.*$: dev-datacenter ^(?P<region>.*)-prod$: prod-datacenter-{region} This example maps all Pillar environments starting with ``dev-`` to ``dev-datacenter`` whereas Pillar environment like ``eu-prod`` will be mapped to ``prod-datacenter-eu``. Before evaluation patterns are sorted by length in descending order. If Pillar environment names correspond to data center names a single pattern can be used: .. code-block:: yaml my_consul_config: consul.dc: ^(?P<env>.*)$: '{env}' After the profile is created, configure the external pillar system to use it. Optionally, a root may be specified. .. code-block:: yaml ext_pillar: - consul: my_consul_config ext_pillar: - consul: my_consul_config root=salt Using these configuration profiles, multiple consul sources may also be used: .. code-block:: yaml ext_pillar: - consul: my_consul_config - consul: my_other_consul_config Either the ``minion_id``, or the ``role``, or the ``environment`` grain may be used in the ``root`` path to expose minion-specific information stored in consul. .. code-block:: yaml ext_pillar: - consul: my_consul_config root=salt/%(minion_id)s - consul: my_consul_config root=salt/%(role)s - consul: my_consul_config root=salt/%(environment)s Minion-specific values may override shared values when the minion-specific root appears after the shared root: .. code-block:: yaml ext_pillar: - consul: my_consul_config root=salt-shared - consul: my_other_consul_config root=salt-private/%(minion_id)s If using the ``role`` or ``environment`` grain in the consul key path, be sure to define it using `/etc/salt/grains`, or similar: .. code-block:: yaml role: my-minion-role environment: dev It's possible to lock down where the pillar values are shared through minion targeting. Note that double quotes ``"`` are required around the target value and cannot be used inside the matching statement. See the section on Compound Matchers for more examples. .. code-block:: yaml ext_pillar: - consul: my_consul_config root=salt target="L@salt.example.com and G@osarch:x86_64" The data from Consul can be merged into a nested key in Pillar. .. code-block:: yaml ext_pillar: - consul: my_consul_config pillar_root=consul_data By default, keys containing YAML data will be deserialized before being merged into Pillar. This behavior can be disabled by setting ``expand_keys`` to ``false``. .. code-block:: yaml ext_pillar: - consul: my_consul_config expand_keys=false � N)�CommandExecutionError)�update� __version__z0.1�consulc C s t durtS dS )z3 Only return if python-consul is installed NF)r �__virtualname__� r r �M/opt/saltstack/salt/lib/python3.10/site-packages/salt/pillar/consul_pillar.py� __virtual__� s r c C s� i }|}t �d�}|�|�}|r?|�d�|d< |�|�d�d�}tjj�t �}|� |d d�}|d } t � d| � | | vr?i S t �d �} | �|�}|r_|�d�� d �|d < |�|�d�d�}nd|d < t �d �} | �|�}|r�|�d�� d �|d < |�|�d�d�}nd|d < t �d�} | �|�}|r�|�d�|d< |�|�d�d�}nd|d< t �dt j�} | �|�}|r�d|d< |�|�d�d�}nd|d< tt |d �}td dd�}td dd�}|d | ||d�; < zNt||d |d �}|d �r3t � d|d |d � i }|}|d �d �}t|�D ] \}}|t|�d k�r&|||< �qi ||< || }�qW |S |}W |S t�yO t �d|d |d � i }Y |S w )z# Check consul for all data ztarget="(.*?)"� �targetr � Zcompound�minionszTargeted minions: %rz(?<!_)root=(\S*)�/�rootzpillar_root=(\S*)Z pillar_rootz(?:profile=)?(\S+)�profileNzexpand_keys=FalseF� expand_keysTz grains.get�role� environment)� minion_idr r z*Merging consul path %s/ into pillar at %s/z$No such key in consul profile %s: %s)�re�compile�search�group�replace�salt�utilsr Z CkMinionsZ__opts__Z check_minions�log�debug�rstrip� IGNORECASE�get_connZ__salt__� fetch_tree�split� enumerate�len�KeyError�error)r �pillar�conf�optsZtempZ target_re�matchZcheckerZ_resr Zroot_reZpillar_root_reZ profile_reZexpand_keys_re�clientr r Z pillar_tree�branch�keys�i�kr r r � ext_pillar� s� � � � ���r0 c C s( | j j|s ddd�S |�d�d dd�S )z; Query consul for all keys/values within base path r r T)Zrecurse)Zkv�getr )r+ �pathr r r � consul_fetch s (r3 c C s� t | |�\}}i }t�d�}t�d|� |du r|S t|�D ]?}t�dt�|� d d|d �}|dkrDt�d||� t�d |�|�� |�|�du r]t ||� d �|d |�}t�d |� q |S ) z� Grab data from consul, trim base path and remove any keys which are folders. Take the remaining data and send it to be formatted in such a way as to be used as pillar data. z/$zFetched items: %rN�^z/?r ZKeyzpath/key - %s: %szhas_children? %rr ZValuez Fetching subkeys for key: %r) r3 r r r r �reversed�sub�escaper � pillar_formatr" ) r+ r2 r �_�items�retZ has_children�item�keyr r r r! s �r! c C sX |du r| S |rt jj�|�}n|}|�� }||i}|�� |D ]}||i}q t| |�S )zi Perform data formatting to be used as pillar data and merge it with the current pillar data N)r r ZyamlZ safe_load�pop�reverse� dict_merge)r; r- �valuer Z pillar_valueZkeyvalueZpilr/ r r r r8 # s r8 c C s� | � di �}|� di �}i }|�|� |�|� |�| � |r&|� |i �}n|}i }|D ]}|�d�r>|| ||�d�d < q,d|v rS|� d�pId}t|d |�|d< trltjd k rd|� d �rd|�d � tjd i |��S t d ��)z5 Return a client object for accessing consul r' Zmasterzconsul.�.r �dc� pillarenv�basez0.4.7r zw(unable to import consul, module most likely not installed. Download python-consul module and be sure to import consul)Nr ) r1 r � startswithr" �_resolve_datacenterr r r> ZConsulr ) r) r Z opts_pillarZ opts_masterZ opts_mergedr( �paramsr= rD r r r r = s0 � �r c C s� t �d| � z| �� }W n ty t �d| � | Y S w t �dt|�� t �d|� t|dd� d�}|D ]&\}}t�||�}|r\t �d|� |jdi |� � ��}t �d |� | S q6t �d |d � d d � |D ��� dS )a� If ``dc`` is a string - return it as is. If it's a dict then sort it in descending order by key length and try to use keys as RegEx patterns to match against ``pillarenv``. The value for matched pattern should be a string (that can use ``str.format`` syntax togetehr with captured variables from pattern) pointing to targe data center to use. If none patterns matched return ``None`` which meanse us datacenter of conencted Consul agent. z(Resolving Consul datacenter based on: %szUsing pre-defined DC: '%s'z3Selecting DC based on pillarenv using %d pattern(s)zPillarenv set to '%s'c S s t | d � | d fS )Nr )r$ )�mr r r �<lambda>~ s z%_resolve_datacenter.<locals>.<lambda>)r= zMatched pattern: '%s'zResolved datacenter: '%s'z3None of following patterns matched pillarenv=%s: %sz, c s s � | ]}t |�V qd S )N)�repr)�.0�xr r r � <genexpr>� s � z&_resolve_datacenter.<locals>.<genexpr>Nr ) r r r: �AttributeErrorr$ �sortedr r* �format� groupdict�join)rC rD ZmappingsZsorted_mappings�patternr r* �resultr r r rG d s. � ��rG )�__doc__�loggingr Zsalt.utils.minionsr Zsalt.utils.yamlZsalt.exceptionsr Zsalt.utils.dictupdater r@ r �hasattrr � ImportErrorr � getLogger�__name__r r r0 r3 r! r8 r rG r r r r �<module> s4 �� � W '
| ver. 1.4 |
Github
|
.
| PHP 8.2.30 | Generation time: 0 |
proxy
|
phpinfo
|
Settings