관리-도구
편집 파일: mod_args.cpython-39.opt-1.pyc
a �)g�5 � @ s� d dl mZmZmZ eZd dlmZ d dl m Z m Z m Z d dl mZ d dlmZ d dlmZmZ d dlmZmZ d dlmZ d d lmZ d d lm Z e ej �Z e � ed ��Z!e ed ��Z"G d d� d�Z#dS )� )�absolute_import�division�print_functionN)�AnsibleParserError� AnsibleError�AnsibleAssertionError)� string_types)�to_text)�parse_kv� split_args)� module_loader� action_loader)�Templar)�add_internal_fqcns)�Sentinel) �includeZ include_vars� include_tasks� include_role� import_tasks� import_roleZadd_hostZgroup_byZset_fact�meta)r r r r r r c @ sF e Zd ZdZddd�Zdd� Zddd�Zd d � Zd d � Zddd�Z dS )�ModuleArgsParsera? There are several ways a module and argument set can be expressed: # legacy form (for a shell command) - action: shell echo hi # common shorthand for local actions vs delegate_to - local_action: shell echo hi # most commonly: - copy: src=a dest=b # legacy form - action: copy src=a dest=b # complex args form, for passing structured data - copy: src: a dest: b # gross, but technically legal - action: module: copy args: src: a dest: b # Standard YAML form for command-type modules. In this case, the args specified # will act as 'defaults' and will be overridden by any args specified # in one of the other formats (complex args under the action, or # parsed from the k=v string - command: 'pwd' args: chdir: '/tmp' This class has some of the logic to canonicalize these into the form - module: <module_name> delegate_to: <optional> args: <args> Args may also be munged for certain shell command parameters. Nc C s� |d u r i n|}t |t�s*tdt|� ��|| _|| _ddlm} ddlm } t |j �| _ | j � t |j �� | j � ddg� t| j �| _ d | _d S )Nz3the type of 'task_ds' should be a dict, but is a %sr )�Task)�Handler� local_actionZstatic)� isinstance�dictr �type�_task_ds�_collection_listZansible.playbook.taskr Zansible.playbook.handlerr �setZ fattributes� _task_attrs�update� frozenset�resolved_action)�selfZtask_ds�collection_listr r � r' �</usr/lib/python3.9/site-packages/ansible/parsing/mod_args.py�__init__j s zModuleArgsParser.__init__c C sF t |�}t|�dkr2|d �� d�|dd� �fS |d �� dfS dS )z� when module names are expressed like: action: copy src=a dest=b the first part of the string is the name of the module and the rest are strings pertaining to the arguments. � r � N� )r �len�strip�join)r% Z module_string�tokensr' r' r( �_split_module_string} s z%ModuleArgsParser._split_module_stringc C s |du r i n|}t � }|rjt|t�rLtdd�}|�|�rB||d< qjtd��n t|t �rb|�|� ntd��|dur�| �||�}n@| �|�\}}|r�d|v r�|� d�}t|t�r�t |�}|�|� |r�|t vr�|D ]&}t |�}|� d�r�td||f ��q�|�r|�|� ||fS ) zC arguments can be fuzzy. Deal with all the forms. N��loader�_variable_paramsz�Complex args containing variables cannot use bare variables (without Jinja2 delimiters), and must use the full variable style ('{{var_name}}')zAComplex args must be a dictionary or variable string ("{{var}}").�argsZ _ansible_z1invalid parameter specified for action '%s': '%s')r r r r � is_templater r" �_normalize_new_style_args�_normalize_old_style_args�popr �FREEFORM_ACTIONSr � startswithr ) r% �thing�action�additional_argsZ final_args�templarr5 Ztmp_args�argr' r' r( �_normalize_parameters� s6 z&ModuleArgsParser._normalize_parametersc C sX t |t�r|}nDt |t�r0|tv }t||d�}n$|du r>d}ntdt|� | jd��|S )ak deals with fuzziness in new style module invocations accepting key=value pairs and dictionaries, and returns a dictionary of arguments possible example inputs: 'echo hi', 'shell' {'region': 'xyz'}, 'ec2' standardized outputs like: { _raw_params: 'echo hi', _uses_shell: True } �� check_rawN�'unexpected parameter type in action: %s��obj)r r r r: r r r r )r% r< r= r5 rC r' r' r( r7 � s z*ModuleArgsParser._normalize_new_style_argsc C s� d}d}t |t�r^|�� }d|v r�| �|d �\}}|�� }|tv }|�t||d�� |d= nDt |t�r�| �|�\}}|tv }t||d�}ntdt |� | j d��||fS )a\ deals with fuzziness in old-style (action/local_action) module invocations returns tuple of (module_name, dictionary_args) possible example inputs: { 'shell' : 'echo hi' } 'shell echo hi' {'module': 'ec2', 'x': 1 } standardized outputs like: ('ec2', { 'x': 1} ) N�modulerB rD rE ) r r �copyr1 r: r" r r r r r )r% r< r= r5 Z module_argsrC r' r' r( r8 � s z*ModuleArgsParser._normalize_old_style_argsFc s. d}d}� j �dt�}t� }� j �dt� �}d� j v rT� j d }� j|||d�\}}d� j v r�|durttd� j d��� j �dd �}d }� j|||d�\}}t� fd d �� j �� D ��}|�� D ]�\}} d} d } |tv r�d} nD|r�d} n:tj |� j d�} | j �st j |� j d�} | j �o t | j�} | r�|du�rDtd||f � j d��| du�r^| j �r^| j� _|}| }� j|||d�\}}q�|du �r�|�r�t|�� �d } td�| �� j d��ntd� j d��nb|�dd �d k�r$|tv�r$tdd�} |�d�}| �|��r||d< n td|d�t�f � j d��|||fS )z� Given a task in one of the supported forms, parses and returns returns the action, arguments, and delegate_to values for the task, dealing with all sorts of levels of fuzziness. N� delegate_tor5 r= )r= r> r z.action and local_action are mutually exclusiverE r, Z localhostc 3 s. | ]&\}}|� j vr|�d �s||fV qdS )Zwith_N)r! r; )�.0�k�v�r% r' r( � <genexpr>( � z)ModuleArgsParser.parse.<locals>.<genexpr>FT)r& z%conflicting action statements: %s, %sr zwcouldn't resolve module/action '{0}'. This often indicates a misspelling, missing collection, or incorrect module path.z"no module/action detected in task.Z _raw_paramsr2 r4 zSthis task '%s' has extra params, which is only allowed in the following modules: %sz, )r �getr r rA r �items� BUILTIN_TASKSr Zfind_plugin_with_contextr Zresolvedr �boolZ redirect_listZ resolved_fqcnr$ �list�keys�format�RAW_PARAM_MODULESr r9 r6 r/ )r% Zskip_action_validationr< r= rI r5 r> Z non_task_ds�item�value�contextZis_action_candidateZ bad_actionr? Z raw_paramsr' rM r( �parse sp ��� ��zModuleArgsParser.parse)NN)NN)F) �__name__� __module__� __qualname__�__doc__r) r1 rA r7 r8 r[ r' r' r' r( r ; s - 7&r )$Z __future__r r r r Z __metaclass__Zansible.constantsZ constants�CZansible.errorsr r r Zansible.module_utils.sixr Zansible.module_utils._textr Zansible.parsing.splitterr r Zansible.plugins.loaderr r Zansible.templater Zansible.utils.fqcnr Zansible.utils.sentinelr r# ZMODULE_REQUIRE_ARGSr: �unionrW rR r r' r' r' r( �<module> s