File: //lib/python3/dist-packages/awscli/customizations/datapipeline/__pycache__/__init__.cpython-310.pyc
o
    .&�a4B  �                   @   s2  d dl Z d dlmZmZ d dlmZ d dlmZ d dlmZ d dl	m
Z
 d dlmZ d dl
mZ d	Zd
ZdZdZd
ZG dd� de�ZG dd� de�Zdd� Zdd� Zdd� Zdd� Zdd� Zdd� Zd,dd�ZG d d!� d!e�ZG d"d#� d#e�Z G d$d%� d%e�Z!G d&d'� d'e�Z"G d(d)� d)e�Z#G d*d+� d+e�Z$dS )-�    N)�datetime�	timedelta)�
get_formatter)�CustomArgument)�BasicCommand)�
translator)�CreateDefaultRoles)�ListRunsFormatterz�The JSON pipeline definition.  If the pipeline definition
is in a file you can use the file://<filename> syntax to
specify a filename.
a  The JSON parameter objects.  If the parameter objects are
in a file you can use the file://<filename> syntax to
specify a filename. You can optionally provide these in
pipeline definition as well. Parameter objects provided
on command line would replace the one in definition.
a  The JSON parameter values.  If the parameter values are
in a file you can use the file://<filename> syntax to
specify a filename. You can optionally provide these in
pipeline definition as well. Parameter values provided
on command line would replace the one in definition.
a  The JSON parameter values. You can specify these as
key-value pairs in the key=value format. Multiple parameters
are separated by a space. For list type parameter values
you can use the same key name and specify each value as
a key value pair. e.g. arrayValue=value1 arrayValue=value2
�d   c                   @   s   e Zd ZdS )�DocSectionNotFoundErrorN)�__name__�
__module__�__qualname__� r   r   �M/usr/lib/python3/dist-packages/awscli/customizations/datapipeline/__init__.pyr   8   s    r   c                       s   e Zd Z� fdd�Z�  ZS )�ParameterDefinitionErrorc                    s"