o

�N�gF�@s�dZd
dl
Z
d
dlZzd
dlZdZWney


dZYn
we
�e�
Z	dZ
dg
Zdadd�Z
dd	d
�
Zddd�
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
Cstrt
Sd
S)N)Fz0Please install the jira Python library from PyPI)�HAS_JIRA�__virtualname__�rr�I/opt/saltstack/salt/lib/python3.10/site-packages/salt/modules/jira_mod.py�__virtual__(s
���rcCsDtd
did�}|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
rrZjira_cfgrrr�_get_credentials0s










rcCs0tst
||
|d
�\}}
}tj|
|f|dd�atS)N�r
rrT)Z
basic_authr
�logging)�JIRArrrrrr�	_get_jira>s

�

�r�jinja�base�Bug�NormalcKs�|rtd
|
||||d�}
td
|||||d�}t
|||
d�}|	s#g}	d|i
|
|d|i
d|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
    zfile.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)rrr Ztemplate_enginerrrr!r"r#�assigneer
rr�kwargs�jira_�data�issue�	issue_keyrrrr(Js>F





�




�






�






r(cCst|||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)rr*)r0r+r
rrr-�assignedrrrr*�s

r*c	Cs$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)	r0Zcommentr2r3r
rrr-Zcommrrrr4�s
$

�r4cCsN|sd
St|
||d�}z|�
|�
}Wntjjy


Yd
Sw|��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
    NrZClosed)rr/r�
exceptionsZ	JIRAError�fields�statusr)r0r
rrr-Zticketrrr�issue_closed�s




�r8)NNN)rNNrrrNNNNN)NFNNN)�__doc__rZsalt.utils.argsr%rr�ImportError�	getLogger�__name__�logrZ__proxyenabled__rrrrr(r*r4r8rrrr�<module>
sH


�














�
h




�+