File manager - Edit - /opt/saltstack/salt/lib/python3.10/site-packages/salt/modules/__pycache__/jira_mod.cpython-310.pyc
Back
o ;jG � @ s� d Z ddlZddlZzddlZdZW n ey dZY nw e�e�Z dZ dgZ da dd� Z dd d �Zdd d �Z ddd�Zddd�Z ddd�Zddd�ZdS ) aG JIRA Execution module ===================== .. versionadded:: 2019.2.0 Execution module to manipulate JIRA tickets via Salt. This module requires the ``jira`` Python library to be installed. Configuration example: .. code-block:: yaml jira: server: https://jira.atlassian.org username: salt password: pass � NTF�jira�*c C s t rtS dS )N)Fz0Please install the jira Python library from PyPI)�HAS_JIRA�__virtualname__� r r �I/opt/saltstack/salt/lib/python3.10/site-packages/salt/modules/jira_mod.py� __virtual__( s ���r c C sD t d di d�}| s|�d�} |s|�d�}|s |�d�}| ||fS )zN Returns the credentials merged with the config data (opts + pillar). z config.merger )�default�server�username�password)�__salt__�get)r r r Zjira_cfgr r r �_get_credentials0 s r c C s0 t st| ||d�\} }}tj ||f| dd�a t S )N�r r r T)Z basic_authr �logging)�JIRAr r r r r r � _get_jira> s � �r �jinja�base�Bug�Normalc K s� |rt d |||||d�}t d |||||d�}t| | | d�}| s#g } d| i||d|id|i| d�}|�tjjjdi |��� |�|�}t|�}| rOt || � |S ) a� Create a JIRA issue using the named settings. Return the JIRA ticket ID. project The name of the project to attach the JIRA ticket to. summary The summary (title) of the JIRA ticket. When the ``template_engine`` argument is set to a proper value of an existing Salt template engine (e.g., ``jinja``, ``mako``, etc.) it will render the ``summary`` before creating the ticket. description The full body description of the JIRA ticket. When the ``template_engine`` argument is set to a proper value of an existing Salt template engine (e.g., ``jinja``, ``mako``, etc.) it will render the ``description`` before creating the ticket. template_engine: ``jinja`` The name of the template engine to be used to render the values of the ``summary`` and ``description`` arguments. Default: ``jinja``. context: ``None`` The context to pass when rendering the ``summary`` and ``description``. This argument is ignored when ``template_engine`` is set as ``None`` defaults: ``None`` Default values to pass to the Salt rendering pipeline for the ``summary`` and ``description`` arguments. This argument is ignored when ``template_engine`` is set as ``None``. saltenv: ``base`` The Salt environment name (for the rendering system). issuetype: ``Bug`` The type of the JIRA ticket. Default: ``Bug``. priority: ``Normal`` The priority of the JIRA ticket. Default: ``Normal``. labels: ``None`` A list of labels to add to the ticket. assignee: ``None`` The name of the person to assign the ticket to. CLI Examples: .. code-block:: bash salt '*' jira.create_issue NET 'Ticket title' 'Ticket description' salt '*' jira.create_issue NET 'Issue on {{ opts.id }}' 'Error detected on {{ opts.id }}' template_engine=jinja z file.apply_template_on_contents)�template�context�defaults�saltenvr �key�name)�project�summary� description� issuetype�priority�labelsNr ) r r �update�salt�utils�argsZ clean_kwargs� create_issue�str� assign_issue)r r r Ztemplate_enginer r r r! r" r# �assigneer r r �kwargs�jira_�data�issue� issue_keyr r r r( J s> F��� r( c C s t |||d�}|�| |�}|S )aW Assign the issue to an existing user. Return ``True`` when the issue has been properly assigned. issue_key The JIRA ID of the ticket to manipulate. assignee The name of the user to assign the ticket to. CLI Example: .. code-block:: bash salt '*' jira.assign_issue NET-123 example_user r )r r* )r0 r+ r r r r- �assignedr r r r* � s r* c C s$ t |||d�}|j| |||d�}dS )a� Add a comment to an existing ticket. Return ``True`` when it successfully added the comment. issue_key The issue ID to add the comment to. comment The body of the comment to be added. visibility: ``None`` A dictionary having two keys: - ``type``: is ``role`` (or ``group`` if the JIRA server has configured comment visibility for groups). - ``value``: the name of the role (or group) to which viewing of this comment will be restricted. is_internal: ``False`` Whether a comment has to be marked as ``Internal`` in Jira Service Desk. CLI Example: .. code-block:: bash salt '*' jira.add_comment NE-123 'This is a comment' r )� visibility� is_internalT)r � add_comment) r0 Zcommentr2 r3 r r r r- Zcommr r r r4 � s $�r4 c C sN | sdS t |||d�}z|�| �}W n tjjy Y dS w |�� jjdkS )af Check if the issue is closed. issue_key The JIRA iD of the ticket to close. Returns: - ``True``: the ticket exists and it is closed. - ``False``: the ticket exists and it has not been closed. - ``None``: the ticket does not exist. CLI Example: .. code-block:: bash salt '*' jira.issue_closed NE-123 Nr ZClosed)r r/ r � exceptionsZ JIRAError�fields�statusr )r0 r r r r- Zticketr r r � issue_closed� s �r8 )NNN) r NNr r r NNNNN)NFNNN)�__doc__r Zsalt.utils.argsr% r r � ImportError� getLogger�__name__�logr Z__proxyenabled__r r r r r( r* r4 r8 r r r r �<module> sH � � h �+
| ver. 1.4 |
Github
|
.
| PHP 8.2.30 | Generation time: 0 |
proxy
|
phpinfo
|
Settings