o !d2@sddlZddlZddlmZddlmZddlmZddlm Z ddl m Z m Z m Z mZmZmZddlmZeeZejdZd ZGd d d eZGd d d eZGdddeZdS)N) OrderedDict) BasicCommand) uni_print)EKSClusterError) KubeconfigKubeconfigErrorKubeconfigLoaderKubeconfigWriterKubeconfigValidatorKubeconfigAppender)ordered_yaml_dumpz~/.kube/configz$client.authentication.k8s.io/v1beta1c @s~eZdZdZedddZdddddd d dd d d dd dd dd dddd ddddd dddd dgZddZddZ dS)UpdateKubeconfigCommandzupdate-kubeconfigeksz_description.rstnamezThe name of the cluster for which to create a kubeconfig entry. This cluster must exist in your account and in the specified or configured default Region for your AWS CLI installation.T)r help_textrequired kubeconfigaOptionally specify a kubeconfig file to append with your configuration. By default, the configuration is written to the first file path in the KUBECONFIG environment variable (if it is set) or the default kubeconfig path (.kube/config) in your home directory.Fzrole-arnzTo assume a role for cluster authentication, specify an IAM role ARN with this option. For example, if you created a cluster while assuming an IAM role, then you must also assume that role to connect to the cluster the first time.zdry-run store_truezRPrint the merged kubeconfig to stdout instead of writing it to the specified file.)ractiondefaultrrverbosez_Print more detailed output when writing to the kubeconfig file, including the appended entries.)rrrraliaszBAlias for the cluster context name. Defaults to match cluster ARN.z user-aliaszAAlias for the generated user name. Defaults to match cluster ARN.cCs*td|D] }tt|tdqdS)z Display entries in yaml format :param entries: a list of OrderedDicts to be printed :type entries: list z Entries:  N)rr )selfentriesentryrOusr/lib/python3.10/site-packages/awscli/customizations/eks/update_kubeconfig.py_display_entriesls   z(UpdateKubeconfigCommand._display_entriesc Cst|j|j|j|}|}|j|jd}ttj dd|j }| |d}| |d}t} | ||||j} |jrEt|dSt} | ||r[td| d|jn td| d|j|jrs|| ||gdSdS)N) user_aliasZ KUBECONFIGrzUpdated context {0} in {1} zAdded new context {0} to {1} ) EKSClient_sessionrrole_arnget_cluster_entryget_user_entryrKubeconfigSelectorosenvirongetrchoose_kubeconfig has_clusterr Zinsert_cluster_user_pairrdry_runrZ dump_contentr Zwrite_kubeconfigformatpathrr) rZ parsed_argsparsed_globalsclientZnew_cluster_dictZ new_user_dictZconfig_selectorconfigZupdating_existingZappenderZnew_context_dictwriterrrr _run_mainxsN     z!UpdateKubeconfigCommand._run_mainN) __name__ __module__ __qualname__NAMErZ FROM_FILEZ DESCRIPTIONZ ARG_TABLErr3rrrrr &sR     = r c@s*eZdZ  dddZddZddZdS) r&Ncs|durt}|_|durt|}|_|dur"|g_dS|dkr(t}fdd|tj D_t jdkrCtg_dSdS)a6 Parse KUBECONFIG into a list of absolute paths. Also replace the empty list with DEFAULT_PATH :param env_variable: KUBECONFIG as a long string :type env_variable: string :param path_in: The path passed in through the CLI :type path_in: string or None Nr cs&g|]}t|dkr|qS)r)lenstrip _expand_path).0elementrrr s z/KubeconfigSelector.__init__..r) r _validatorr_loaderr:_paths DEFAULT_PATHsplitr'pathsepr8)rZ env_variableZpath_in validatorloaderrr=r__init__s     zKubeconfigSelector.__init__c Cs|jD]7}z|j|}||rtd||WSWqty:}ztd||WYd}~qd}~ww|j|jdS)a Choose which kubeconfig file to read from. If name is already an entry in one of the $KUBECONFIG files, choose that one. Otherwise choose the first file. :param cluster_name: The name of the cluster which is going to be added :type cluster_name: String :return: a chosen Kubeconfig based on above rules :rtype: Kubeconfig zFound entry to update at {0}zPassing {0}:{1}Nr) rAr@Zload_kubeconfigr+LOGdebugr-rwarning)r cluster_nameZcandidate_pathZ loaded_configerrrr*s    z$KubeconfigSelector.choose_kubeconfigcCstjtj|S)z4 A helper to expand a path to a full absolute path. )r'r.abspath expanduser)rr.rrrr:szKubeconfigSelector._expand_path)NN)r4r5r6rGr*r:rrrrr&s  ! r&c@s0eZdZd ddZddZddZd dd ZdS) r!NcCs"||_||_||_d|_||_dSN)r" _cluster_name _role_arn_cluster_description_globals)rZsessionrKr#r/rrrrGs  zEKSClient.__init__cCs|jdurG|jdur|jd}n|jjd|jj|jj|jjd}|j|jd}|d|_d|jvr6t d|jddvrGt d |jd|jS) z Use an eks describe-cluster call to get the cluster description Cache the response in self._cluster_description. describe-cluster will only be called once. Nr)Z region_name endpoint_urlZverify)rclusterstatuszCluster not found)ZACTIVEZUPDATINGzCluster status is {0}) rRrSr"Z create_clientregionrTZ verify_sslZdescribe_clusterrPrr-)rr0Zfull_descriptionrrr_get_cluster_descriptions$    z"EKSClient._get_cluster_descriptioncCsX|dddid}|d}|d}tdtd|fd|fgfd |fgS) ze Return a cluster entry generated using the previously obtained description. ZcertificateAuthoritydatar endpointarnrUzcertificate-authority-dataserverr)rXr)r)rZ cert_datarZr[rrrr$s zEKSClient.get_cluster_entrycCs|}|ddd}|d}|durd}|j}nd}|d}td |p/|dd fd td td tfdd|dd||ddgfdgfgfg}|jdur_|d d dd|jg|jj rttdd|jj fgg|d d d<|S)zb Return a user entry generated using the previously obtained description. r[:Z outpostConfigNz--cluster-namez --cluster-ididrr userexecZ apiVersionargsz--regionrz get-tokenz--outputjson)commandZawsz--role)rZ AWS_PROFILEvalueenv) rXr)rCrPr API_VERSIONrQextendr"Zprofile)rrZcluster_descriptionrWZoutpost_configZ cluster_identification_parameterZcluster_identification_valueZgenerated_userrrrr%$sN     zEKSClient.get_user_entryrO)r4r5r6rGrXr$r%rrrrr!s  r!)r'loggingZbotocore.compatrZawscli.customizations.commandsrZawscli.customizations.utilsrZ$awscli.customizations.eks.exceptionsrZ$awscli.customizations.eks.kubeconfigrrrr r r Z&awscli.customizations.eks.ordered_yamlr getLoggerr4rHr.rNrBrgr objectr&r!rrrrs         G