관리-도구
편집 파일: __init__.cpython-39.pyc
a �)gf � @ sh d dl mZmZmZ eZd dlmZ d dlm Z d dl m Z d dl m Z e � ZdgZG dd� de �ZdS ) � )�absolute_import�division�print_function)�abstractmethod)�AnsibleFileNotFound)� AnsiblePlugin)�Display� LookupBasec sj e Zd Zd� fdd� Zdd� Zedd� �Zedd � �Zed d � �Ze dd d ��Z ddd�Z dd� Z � Z S )r Nc s$ t t| ��� || _|| _t| _d S �N)�superr �__init__�_loaderZ_templar�display�_display)�self�loaderZtemplar�kwargs�� __class__� �C/usr/lib/python3.9/site-packages/ansible/plugins/lookup/__init__.pyr # s zLookupBase.__init__c C s d|v r|d S | j �� S d S )NZ role_path)r � get_basedir)r � variablesr r r r - s zLookupBase.get_basedirc C s6 g }| D ](}t |ttf�r&|�|� q|�|� q|S r )� isinstance�list�tuple�extend�append)�terms�retZtermr r r �_flatten3 s zLookupBase._flattenc C s0 g }| D ]"}|D ]}|� t�||g�� qq|S r )r r r )�a�b�results�x�yr r r �_combine= s zLookupBase._combinec C s& g }| D ]}|� || | d�� q|S )N)�key�value)r )r r r' r r r �_flatten_hash_to_listE s z LookupBase._flatten_hash_to_listc K s dS )a� When the playbook specifies a lookup, this method is run. The arguments to the lookup become the arguments to this method. One additional keyword argument named ``variables`` is added to the method call. It contains the variables available to ansible at the time the lookup is templated. For instance:: "{{ lookup('url', 'https://toshio.fedorapeople.org/one.txt', validate_certs=True) }}" would end up calling the lookup plugin named url's run method like this:: run(['https://toshio.fedorapeople.org/one.txt'], variables=available_variables, validate_certs=True) Lookup plugins can be used within playbooks for looping. When this happens, the first argument is a list containing the terms. Lookup plugins can also be called from within playbooks to return their values into a variable or parameter. If the user passes a string in this case, it is converted into a list. Errors encountered during execution should be returned by raising AnsibleError() with a message describing the error. Any strings returned by this method that could ever contain non-ascii must be converted into python's unicode type as the strings will be run through jinja2 which has this requirement. You can use:: from ansible.module_utils._text import to_text result_string = to_text(result_string) Nr )r r r r r r r �runL s zLookupBase.runFc C sb d|v r|d }n | � |�g}d}z| j�|||�}W n& ty\ |sX| j�d| � Y n0 |S )zL Return a file (needle) in the task's expected search path. Zansible_search_pathNz?Unable to find '%s' in expected paths (use -vvvvv to see paths))r r Zpath_dwim_relative_stackr r Zwarning)r ZmyvarsZsubdirZneedleZignore_missing�paths�resultr r r �find_file_in_search_pathl s z#LookupBase.find_file_in_search_pathc C s d S r r )r r r r �_deprecate_inline_kv s z LookupBase._deprecate_inline_kv)NN)N)F)�__name__� __module__� __qualname__r r � staticmethodr r& r) r r* r- r. � __classcell__r r r r r ! s N)Z __future__r r r �typeZ __metaclass__�abcr Zansible.errorsr Zansible.pluginsr Zansible.utils.displayr r �__all__r r r r r �<module> s