golden hour

/opt/saltstack/salt/lib/python3.10/site-packages/salt/runners/__pycache__

⬆️ Go Up

Upload

File/Folder	Size	Actions
__init__.cpython-310.pyc	197 B	Del OK
asam.cpython-310.pyc	7.9 KB	Del OK
auth.cpython-310.pyc	1.89 KB	Del OK
bgp.cpython-310.pyc	12.55 KB	Del OK
cache.cpython-310.pyc	10.98 KB	Del OK
cloud.cpython-310.pyc	4.16 KB	Del OK
config.cpython-310.pyc	1.08 KB	Del OK
ddns.cpython-310.pyc	6.7 KB	Del OK
digicertapi.cpython-310.pyc	16.23 KB	Del OK
doc.cpython-310.pyc	1.76 KB	Del OK
drac.cpython-310.pyc	4.15 KB	Del OK
error.cpython-310.pyc	771 B	Del OK
event.cpython-310.pyc	2.32 KB	Del OK
f5.cpython-310.pyc	8.29 KB	Del OK
fileserver.cpython-310.pyc	17.12 KB	Del OK
git_pillar.cpython-310.pyc	3.54 KB	Del OK
http.cpython-310.pyc	2.55 KB	Del OK
jobs.cpython-310.pyc	13.26 KB	Del OK
launchd.cpython-310.pyc	1.49 KB	Del OK
lxc.cpython-310.pyc	13.3 KB	Del OK
manage.cpython-310.pyc	21.71 KB	Del OK
mattermost.cpython-310.pyc	4.21 KB	Del OK
mine.cpython-310.pyc	1.79 KB	Del OK
nacl.cpython-310.pyc	8.46 KB	Del OK
net.cpython-310.pyc	27.7 KB	Del OK
network.cpython-310.pyc	2.59 KB	Del OK
pagerduty.cpython-310.pyc	3.96 KB	Del OK
pillar.cpython-310.pyc	4.25 KB	Del OK
pkg.cpython-310.pyc	1.37 KB	Del OK
queue.cpython-310.pyc	8.14 KB	Del OK
reactor.cpython-310.pyc	4.32 KB	Del OK
salt.cpython-310.pyc	4.58 KB	Del OK
saltutil.cpython-310.pyc	15.88 KB	Del OK
sdb.cpython-310.pyc	2.54 KB	Del OK
smartos_vmadm.cpython-310.pyc	7.99 KB	Del OK
spacewalk.cpython-310.pyc	7.54 KB	Del OK
ssh.cpython-310.pyc	1000 B	Del OK
state.cpython-310.pyc	8.22 KB	Del OK
survey.cpython-310.pyc	5.07 KB	Del OK
test.cpython-310.pyc	2.65 KB	Del OK
thin.cpython-310.pyc	1.81 KB	Del OK
vault.cpython-310.pyc	10.01 KB	Del OK
venafiapi.cpython-310.pyc	5.57 KB	Del OK
virt.cpython-310.pyc	13.15 KB	Del OK
vistara.cpython-310.pyc	4.39 KB	Del OK
winrepo.cpython-310.pyc	5.14 KB	Del OK

Edit: fileserver.cpython-310.pyc

o �����xexE����������������������@���st���d�Z�d
dl
Zddd�
Zddd�
Zdd d �
Zddd�
Zdd d�
Zddd�
Zddd�
Z ddd�
Z ddd�
Zddd�
ZdS�)z- Directly manage the Salt fileserver plugins �����NFc�����������������C���s���t�j
�t�
}t|j|�|
d
��
S�)a��� Return the available fileserver environments. If no backend is provided, then the environments for all configured backends will be returned. backend Narrow fileserver backends to a subset of the enabled ones. .. versionchanged:: 2015.5.0 If all passed backends start with a minus sign (``-``), then these backends will be excluded from the enabled backends. However, if there is a mix of backends with and without a minus sign (ex: ``backend=-roots,git``) then the ones starting with a minus sign will be disregarded. Additionally, fileserver backends can now be passed as a comma-separated list. In earlier versions, they needed to be passed as a python list (ex: ``backend="['roots', 'git']"``) CLI Example: .. code-block:: bash salt-run fileserver.envs salt-run fileserver.envs backend=roots,git salt-run fileserver.envs git )�back�sources)�salt� fileserver� Fileserver�__opts__�sorted�envs)�backendr���r�����r����K/opt/saltstack/salt/lib/python3.10/site-packages/salt/runners/fileserver.pyr ������s���
r ���c�����������������C����"���t�j
�t�
}|�|
d
�}|j|d�
S�)a��� .. versionadded:: 2016.11.0 The Salt fileserver caches the files/directories/symlinks for each fileserver backend and environment as they are requested. This is done to help the fileserver scale better. Without this caching, when hundreds/thousands of minions simultaneously ask the master what files are available, this would cause the master's CPU load to spike as it obtains the same information separately for each minion. saltenv By default, this runner will clear the file list caches for all environments. This argument allows for a list of environments to be passed, to clear more selectively. This list can be passed either as a comma-separated string, or a Python list. backend Similar to the ``saltenv`` parameter, this argument will restrict the cache clearing to specific fileserver backends (the default behavior is to clear from all enabled fileserver backends). This list can be passed either as a comma-separated string, or a Python list. .. note: The maximum age for the cached file lists (i.e. the age at which the cache will be disregarded and rebuilt) is defined by the :conf_master:`fileserver_list_cache_time` configuration parameter. Since the ability to clear these caches is often required by users writing custom runners which add/remove files, this runner can easily be called from within a custom runner using any of the following examples: .. code-block:: python # Clear all file list caches __salt__['fileserver.clear_file_list_cache']() # Clear just the 'base' saltenv file list caches __salt__['fileserver.clear_file_list_cache'](saltenv='base') # Clear just the 'base' saltenv file list caches from just the 'roots' # fileserver backend __salt__['fileserver.clear_file_list_cache'](saltenv='base', backend='roots') # Clear all file list caches from the 'roots' fileserver backend __salt__['fileserver.clear_file_list_cache'](backend='roots') .. note:: In runners, the ``__salt__`` dictionary will likely be renamed to ``__runner__`` in a future Salt release to distinguish runner functions from remote execution functions. See `this GitHub issue`_ for discussion/updates on this. .. _`this GitHub issue`: https://github.com/saltstack/salt/issues/34958 If using Salt's Python API (not a runner), the following examples are equivalent to the ones above: .. code-block:: python import salt.config import salt.runner opts = salt.config.master_config('/etc/salt/master') opts['fun'] = 'fileserver.clear_file_list_cache' # Clear all file list_caches opts['arg'] = [] # No arguments runner = salt.runner.Runner(opts) cleared = runner.run() # Clear just the 'base' saltenv file list caches opts['arg'] = ['base', None] runner = salt.runner.Runner(opts) cleared = runner.run() # Clear just the 'base' saltenv file list caches from just the 'roots' # fileserver backend opts['arg'] = ['base', 'roots'] runner = salt.runner.Runner(opts) cleared = runner.run() # Clear all file list caches from the 'roots' fileserver backend opts['arg'] = [None, 'roots'] runner = salt.runner.Runner(opts) cleared = runner.run() This function will return a dictionary showing a list of environments which were cleared for each backend. An empty return dictionary means that no changes were made. CLI Examples: .. code-block:: bash # Clear all file list caches salt-run fileserver.clear_file_list_cache # Clear just the 'base' saltenv file list caches salt-run fileserver.clear_file_list_cache saltenv=base # Clear just the 'base' saltenv file list caches from just the 'roots' # fileserver backend salt-run fileserver.clear_file_list_cache saltenv=base backend=roots # Clear all file list caches from the 'roots' fileserver backend salt-run fileserver.clear_file_list_cache backend=roots ��saltenvZ fsbackend�
�load)r���r���r���r����clear_file_list_cache�r���r ���r���r���r���r���r���r���'���s���g

r����basec�����������������C���r ���)aA�� Return a list of files from the salt fileserver saltenv : base The salt fileserver environment to be listed backend Narrow fileserver backends to a subset of the enabled ones. If all passed backends start with a minus sign (``-``), then these backends will be excluded from the enabled backends. However, if there is a mix of backends with and without a minus sign (ex: ``backend=-roots,git``) then the ones starting with a minus sign will be disregarded. .. versionadded:: 2015.5.0 .. note: Keep in mind that executing this function spawns a new process, separate from the master. This means that if the fileserver configuration has been changed in some way since the master has been restarted (e.g. if :conf_master:`fileserver_backend`, :conf_master:`gitfs_remotes`, :conf_master:`hgfs_remotes`, etc. have been updated), then the results of this runner will not accurately reflect what files are available to minions. When in doubt, use :py:func:`cp.list_master <salt.modules.cp.list_master>` to see what files the minion can see, and always remember to restart the salt-master daemon when updating the fileserver configuration. CLI Examples: .. code-block:: bash salt-run fileserver.file_list salt-run fileserver.file_list saltenv=prod salt-run fileserver.file_list saltenv=dev backend=git salt-run fileserver.file_list base hg,roots salt-run fileserver.file_list -git r���r���)r���r���r���r���� file_listr���r���r���r���r�����������)

r���c�����������������C���r ���)aa�� Return a list of symlinked files and dirs saltenv : base The salt fileserver environment to be listed backend Narrow fileserver backends to a subset of the enabled ones. If all passed backends start with a minus sign (``-``), then these backends will be excluded from the enabled backends. However, if there is a mix of backends with and without a minus sign (ex: ``backend=-roots,git``) then the ones starting with a minus sign will be disregarded. .. versionadded:: 2015.5.0 .. note: Keep in mind that executing this function spawns a new process, separate from the master. This means that if the fileserver configuration has been changed in some way since the master has been restarted (e.g. if :conf_master:`fileserver_backend`, :conf_master:`gitfs_remotes`, :conf_master:`hgfs_remotes`, etc. have been updated), then the results of this runner will not accurately reflect what symlinks are available to minions. When in doubt, use :py:func:`cp.list_master_symlinks <salt.modules.cp.list_master_symlinks>` to see what symlinks the minion can see, and always remember to restart the salt-master daemon when updating the fileserver configuration. CLI Example: .. code-block:: bash salt-run fileserver.symlink_list salt-run fileserver.symlink_list saltenv=prod salt-run fileserver.symlink_list saltenv=dev backend=git salt-run fileserver.symlink_list base hg,roots salt-run fileserver.symlink_list -git r���r���)r���r���r���r����symlink_listr���r���r���r���r�������r���r���c�����������������C���r ���)aI�� Return a list of directories in the given environment saltenv : base The salt fileserver environment to be listed backend Narrow fileserver backends to a subset of the enabled ones. If all passed backends start with a minus sign (``-``), then these backends will be excluded from the enabled backends. However, if there is a mix of backends with and without a minus sign (ex: ``backend=-roots,git``) then the ones starting with a minus sign will be disregarded. .. versionadded:: 2015.5.0 .. note: Keep in mind that executing this function spawns a new process, separate from the master. This means that if the fileserver configuration has been changed in some way since the master has been restarted (e.g. if :conf_master:`fileserver_backend`, :conf_master:`gitfs_remotes`, :conf_master:`hgfs_remotes`, etc. have been updated), then the results of this runner will not accurately reflect what dirs are available to minions. When in doubt, use :py:func:`cp.list_master_dirs <salt.modules.cp.list_master_dirs>` to see what dirs the minion can see, and always remember to restart the salt-master daemon when updating the fileserver configuration. CLI Example: .. code-block:: bash salt-run fileserver.dir_list salt-run fileserver.dir_list saltenv=prod salt-run fileserver.dir_list saltenv=dev backend=git salt-run fileserver.dir_list base hg,roots salt-run fileserver.dir_list -git r���r���)r���r���r���r����dir_listr���r���r���r���r�������r���r���c�����������������C���r ���)a)�� .. versionadded:: 2015.5.0 Return a list of empty directories in the given environment saltenv : base The salt fileserver environment to be listed backend Narrow fileserver backends to a subset of the enabled ones. If all passed backends start with a minus sign (``-``), then these backends will be excluded from the enabled backends. However, if there is a mix of backends with and without a minus sign (ex: ``backend=-roots,git``) then the ones starting with a minus sign will be disregarded. .. note:: Some backends (such as :mod:`git <salt.fileserver.gitfs>` and :mod:`hg <salt.fileserver.hgfs>`) do not support empty directories. So, passing ``backend=git`` or ``backend=hg`` will result in an empty list being returned. CLI Example: .. code-block:: bash salt-run fileserver.empty_dir_list salt-run fileserver.empty_dir_list saltenv=prod salt-run fileserver.empty_dir_list backend=roots r���r���)r���r���r���r���Zfile_list_emptydirsr���r���r���r����empty_dir_list
��s���

r���c
�����������������K���s$���t�j
�t�
}|jdd
|�i
|
�
�

�dS�)a<�� Update the fileserver cache. If no backend is provided, then the cache for all configured backends will be updated. backend Narrow fileserver backends to a subset of the enabled ones. .. versionchanged:: 2015.5.0 If all passed backends start with a minus sign (``-``), then these backends will be excluded from the enabled backends. However, if there is a mix of backends with and without a minus sign (ex: ``backend=-roots,git``) then the ones starting with a minus sign will be disregarded. Additionally, fileserver backends can now be passed as a comma-separated list. In earlier versions, they needed to be passed as a python list (ex: ``backend="['roots', 'git']"``) kwargs Pass additional arguments to backend. See example below CLI Example: .. code-block:: bash salt-run fileserver.update salt-run fileserver.update backend=roots,git salt-run fileserver.update backend=git remotes=myrepo,yourrepo r���TNr���)r���r���r���r����update)r ����kwargsr���r���r���r���r���B
��s���

r���c
�����������������C���sD���t�j
�t�
}
|
j|�d
�
\}}i�}|r||d<�|r||d<�|s dS�|S�)a��� .. versionadded:: 2015.5.0 Clear the fileserver cache from VCS fileserver backends (:mod:`git <salt.fileserver.gitfs>`, :mod:`hg <salt.fileserver.hgfs>`, :mod:`svn <salt.fileserver.svnfs>`). Executing this runner with no arguments will clear the cache for all enabled VCS fileserver backends, but this can be narrowed using the ``backend`` argument. backend Only clear the update lock for the specified backend(s). If all passed backends start with a minus sign (``-``), then these backends will be excluded from the enabled backends. However, if there is a mix of backends with and without a minus sign (ex: ``backend=-roots,git``) then the ones starting with a minus sign will be disregarded. CLI Example: .. code-block:: bash salt-run fileserver.clear_cache salt-run fileserver.clear_cache backend=git,hg salt-run fileserver.clear_cache hg salt-run fileserver.clear_cache -roots )
r����cleared�errorszNo cache was cleared)r���r���r���r����clear_cache)r ���r���r���r����retr���r���r���r���e
��s���








r���c�����������������C����F���t�j
�t�
}|j|�|
d
�\}}i�}|r||d<�|r||d<�|s!dS�|S�)a]�� .. versionadded:: 2015.5.0 Clear the fileserver update lock from VCS fileserver backends (:mod:`git <salt.fileserver.gitfs>`, :mod:`hg <salt.fileserver.hgfs>`, :mod:`svn <salt.fileserver.svnfs>`). This should only need to be done if a fileserver update was interrupted and a remote is not updating (generating a warning in the Master's log file). Executing this runner with no arguments will remove all update locks from all enabled VCS fileserver backends, but this can be narrowed by using the following arguments: backend Only clear the update lock for the specified backend(s). remote If specified, then any remotes which contain the passed string will have their lock cleared. For example, a ``remote`` value of **github** will remove the lock from all github.com remotes. CLI Example: .. code-block:: bash salt-run fileserver.clear_lock salt-run fileserver.clear_lock backend=git,hg salt-run fileserver.clear_lock backend=git remote=github salt-run fileserver.clear_lock remote=bitbucket �r����remoter���r���zNo locks were removed)r���r���r���r���� clear_lock)r ���r"���r���r���r���r���r���r���r���r#����
��s���








r#���c�����������������C���r ���)a�� .. versionadded:: 2015.5.0 Set a fileserver update lock for VCS fileserver backends (:mod:`git <salt.fileserver.gitfs>`, :mod:`hg <salt.fileserver.hgfs>`, :mod:`svn <salt.fileserver.svnfs>`). .. note:: This will only operate on enabled backends (those configured in :conf_master:`fileserver_backend`). backend Only set the update lock for the specified backend(s). remote If not None, then any remotes which contain the passed string will have their lock cleared. For example, a ``remote`` value of ``*github.com*`` will remove the lock from all github.com remotes. CLI Example: .. code-block:: bash salt-run fileserver.lock salt-run fileserver.lock backend=git,hg salt-run fileserver.lock backend=git remote='*github.com*' salt-run fileserver.lock remote=bitbucket r!����lockedr���zNo locks were set)r���r���r���r����lock)r ���r"���r���r$���r���r���r���r���r���r%����
��s���








r%���)NF)NN)r���N)
N) �__doc__Zsalt.fileserverr���r ���r���r���r���r���r���r���r���r#���r%���r���r���r���r����<module>
���s����   l . . . % # &)
Save