File manager - Edit - /opt/saltstack/salt/lib/python3.10/site-packages/salt/modules/__pycache__/pagerduty_util.cpython-310.pyc
Back
o ;j6 � @ s� d Z ddlZddlZdd� Zd!dd�Zd!dd �Zd!d d �Zd!d d �Zd"dd�Z d#dd�Z dd� Z d!dd�Z d$dd�Z d!dd �Z d$d d �Z d!d d �ZdS )%a� Module for manageing PagerDuty resource :configuration: This module can be used by specifying the name of a configuration profile in the minion config, minion pillar, or master config. The default configuration profile name is 'pagerduty.' For example: .. code-block:: yaml pagerduty: pagerduty.api_key: F3Rbyjbve43rfFWf2214 pagerduty.subdomain: mysubdomain For PagerDuty API details, see https://developer.pagerduty.com/documentation/rest � Nc C s dS )z> No dependencies outside of what Salt itself requires T� r r r �O/opt/saltstack/salt/lib/python3.10/site-packages/salt/modules/pagerduty_util.py� __virtual__ s r � pagerdutyc C � t dd| ||d�S )z� List users belonging to this account CLI Example: .. code-block:: bash salt myminion pagerduty.get_users Zusers�id��profile� subdomain�api_key�� _list_itemsr r r r � get_users! � �r c C r )z� List services belonging to this account CLI Example: .. code-block:: bash salt myminion pagerduty.get_services �servicesr r r r r r r � get_services5 r r c C r )z� List schedules belonging to this account CLI Example: .. code-block:: bash salt myminion pagerduty.get_schedules � schedulesr r r r r r r � get_schedulesI r r c C r )z� List escalation_policies belonging to this account CLI Example: .. code-block:: bash salt myminion pagerduty.get_escalation_policies Zescalation_policiesr r r r r r r �get_escalation_policies] r r c C s2 t |||| d�}i }|| D ]}|||| < q|S )z] List items belonging to an API call. This method should be in utils.pagerduty. )r r r �action)�_query)r �keyr r r �items�ret�itemr r r r q s r �GET�api/v1Tc C sv |r t d |�} n|| d�} |du rd�| d ||�}|du r!i }|du r'i }dd�| d �i} | d kr8d | d < tj| || |tjj�|�| d d �} | jdu sS| jdkrUdS | �� }d|v r�d|v r�d|v r�|d }|d }|d }|| |k r�|| }d}||d< ||d< tj| || ||| d d ��� }|d }|d }|� � D ]\}}t |t �r�|| || 7 < q�|| |k sw|S )zR Query the PagerDuty API. This method should be in utils.pagerduty. z config.option)�pagerduty.api_key�pagerduty.subdomainNz https://{}.pagerduty.com/{}/{}r Z AuthorizationzToken token={}r r zapplication/jsonz Content-type�x )�headers�params�dataZverify�timeout� �total�offset�limit�d ) Z__salt__�format�requests�request�salt�utils�json�dumps�textr � isinstance�list)�methodr �url�pathr r Zservicer! r" r Z verify_sslZcredsr �resultZ result_jsonr& r' r% Znext_page_results�k�vr r r r ~ sp � � � �� � �r c C s( d| v r| d S d| v r| d d S dS )zf helper method to find the resource id, since PD API doesn't always return it in the same way r ZscheduleNr )�resourcer r r �_get_resource_id� s r: c C s� dt vri t d< | t d vr'| dkr| d }n| }t||||d�| t d | < t d | D ]+}|D ]&}|| |krW| dkrQtd�| |d �|||d�} | S | S q1q-dS ) am Get any single pagerduty resource by key. We allow flexible lookup by any of a list of identifier_fields. So, for example, you can look up users by email address or name by calling: get_resource('users', key, ['name', 'email'], ...) This method is mainly used to translate state sls into pagerduty id's for dependent objects. For example, a pagerduty escalation policy contains one or more schedules, which must be passed by their pagerduty id. We look up the schedules by name (using this method), and then translate the names into id's. This method is implemented by getting all objects of the resource type (cached into __context__), then brute force searching through the list and trying to match any of the identifier_fields. The __context__ cache is purged after any create, update or delete to the resource. � pagerduty_util.resource_cacher z ?include[]=escalation_policy)r r r r r z{}/{}r N)� __context__r r) ) � resource_namer �identifier_fieldsr r r r r9 �fieldZfull_resource_infor r r � get_resource� s4 � � � �� r@ c C s d}|D ]}||v rt | || ||||�}|dur nq|du r5td r&dS td | = td| ||||d�S i } |r?|||�} n!|�� D ] \} } | �d�rMqC|�| d�} | dur_| | kr_| | | < qC| r�td rhdS td | = t|�} td | � d | � �| |||d�S d S ) a/ create or update any pagerduty resource Helper method for present(). Determining if two resources are the same is different for different PD resource, so this method accepts a diff function. The diff function will be invoked as diff(state_information, object_returned_from_pagerduty), and should return a dict of data to pass to the PagerDuty update API method, or None if no update is to be performed. If no diff method is provided, the default behavor is to scan the keys in the state_information, comparing the matching values in the object_returned_from_pagerduty, and update any values that differ. examples: create_or_update_resource("user", ["id","name","email"]) create_or_update_resource("escalation_policies", ["id","name"], diff=my_diff_function) N�testz would creater; �POST)r3 r r" r r r �_z would update�PUT�/T)r@ �__opts__r< r r � startswith�getr: )r= r> r" �diffr r r r9 r? Zdata_to_updater7 r8 Zresource_value� resource_idr r r �create_or_update_resource sd �� � � � rK c C sT t | |||||�}|r(td rdS td | = t|�}td| � d|� �|||d�S dS )z� delete any pagerduty resource Helper method for absent() example: delete_resource("users", key, ["id","name","email"]) # delete by id or name or email rA z would deleter; ZDELETErE )r3 r r r r T)r@ rF r< r: r )r= r r> r r r r9 rJ r r r �delete_resourceh s � �rL c K s� |d i ddd�}t | ||||||d�}|du r |S |du r%d|d< |S td r/||d < |S d |v r=d |d< ||d < |S d|d< ||d < |S ) aI Generic resource.present state method. Pagerduty state modules should be a thin wrapper over this method, with a custom diff function. This method calls create_or_update_resource() and formats the result as a salt state return value. example: resource_present("users", ["id","name","email"]) �nameNr$ �rM Zchangesr6 �comment)rI r r r Tr6 rA rO �errorF)rK rF ) r9 r> rI r r r �kwargsr r6 r r r �resource_present� s4 � � ���rR c K s� |d i ddd�}|� � D ]G\}}||vrq t| |||||d�} | du r3d|d< |� d�|d < | S | du r8q td rD| |d < | S d | v rTd |d< | |d < | S q |S ) a= Generic resource.absent state method. Pagerduty state modules should be a thin wrapper over this method, with a custom diff function. This method calls delete_resource() and formats the result as a salt state return value. example: resource_absent("users", ["id","name","email"]) rM Nr$ rN r Tr6 z deletedrO rA rP F)r rL rF ) r9 r> r r r rQ r r7 r8 r6 r r r �resource_absent� s6 ��rS )r NN)NNN) r NNr NNNNNNT)Nr NN)�__doc__r* Zsalt.utils.jsonr, r r r r r r r r: r@ rK rL rR rS r r r r �<module> sX �U �9 �Y �( �/�
| ver. 1.4 |
Github
|
.
| PHP 8.2.30 | Generation time: 0 |
proxy
|
phpinfo
|
Settings