Normal
ˆ
ƒ‹_•I|¥‰ÓMdœv ©ƒ&íK<óo¬ÁÀ Ø
Index of /FSS-BCZ/root/proc/1492/attr
Index of /FSS-BCZ/root/proc/1492/attr
$ ˆl–äY>”ÊC]ŠqAãB¸'Å£Ä
„YeßÃÂÁ ,I a
ì)g€B ã @ s d dl mZmZmZ eZd dlmZ d dlZd dl Z d dl
Z
d dlZd dlZd dl
Z
d dlZd dlZd dlZd dlmZ d dlmZ d dlmZ d dlmZ d dlmZmZ d d lmZ d d
lm Z d dl!m"Z" e"ƒ Z#G dd
„ d
eƒZ$ddd„Z%e&dk�r e%ƒ dS )é )Úabsolute_importÚdivisionÚprint_function)ÚCLIN)Ú constants)Úcontext)Úoption_helpers)ÚAnsibleOptionsError)Ú to_nativeÚto_text)Ú
module_loader)Úrun_cmd)ÚDisplayc s‚ e Zd ZdZdZdZdZdZdddœZd d
iZ dZ
edd
„ ƒZ‡ fdd„Z
‡ fdd„Z‡ fdd„Zedd„ ƒZedd„ ƒZ‡ ZS )ÚPullCLIaO Used to pull a remote copy of ansible on each managed node,
each set to run via cron and update playbook source via a source repository.
This inverts the default *push* architecture of ansible into a *pull* architecture,
which has near-limitless scaling potential.
None of the CLI tools are designed to run concurrently with themselves,
you should use an external scheduler and/or locking to ensure there are no clashing operations.
The setup playbook can be tuned to change the cron frequency, logging locations, and parameters to ansible-pull.
This is useful both for extreme scale-out as well as periodic remediation.
Usage of the 'fetch' module to retrieve logs from ansible-pull runs would be an
excellent way to gather and analyze remote logs from ansible-pull.
zansible-pullÚgitz local.yml)r Ú
subversionÚhgÚbzrzFile does not existzFile is not readable)é é úplaybook.ymla The name of one the YAML format files to run as an Ansible playbook.This can be a relative path within the checkout. By default, Ansible willlook for a playbook based on the host's fully-qualified domain name,on the host hostname and finally a playbook named *local.yml*.Tc C sd d} t j dd¡r`t jd D ]B}t|tƒr>| dd |¡ 7 } qd|v sRtj |¡r| d| 7 } q| S )NÚ Z inventoryFz -i '%s' ú,z -i %s ) r ÚCLIARGSÚgetÚ
isinstanceÚlistÚjoinÚosÚpathÚexists)Úinv_optsÚinv© r# ú4/usr/lib/python3.9/site-packages/ansible/cli/pull.pyÚ_