File: //usr/lib/google-cloud-sdk/lib/surface/projects/__pycache__/move.cpython-312.pyc
�
��� � �& � d Z ddlmZ ddlmZ ddlmZ ddlmZ ddlmZ ddl m
Z ddl m Z
ddlm
Z dd lmZ dd
lmZ ej( ej* j, ej* j. � G d � d ej0 � � Zy
)z/Command to move a project into an organization.� )�absolute_import)�division)�unicode_literals)� projects_api)�base)�flags)�util)�log)�
console_ioc �& � e Zd ZdZed� � Zd� Zy)�Movea� Move a project into an organization.
Moves the given project into the given organization.
This command can fail for the following reasons:
* There is no project with the given ID.
* There is no organization with the given ID, if an organization is given
as the destination.
* There is no folder with the given ID, if a folder is given as the
destination.
* More than one of organization or folder is provided.
* The active account does not have the
resourcemanager.projects.update permission for the given
project.
* The active account does not have the
resourcemanager.projects.create permission for the given
organization.
* The given project is already in an organization.
## EXAMPLES
The following command moves a project with the ID `super-awesome-project` into
the organization `25872158`:
$ {command} super-awesome-project --organization=25872158
c �� � t j d� j | � t j | � | j
j
t j � y )N�move) �
project_flags�GetProjectIDNumberFlag� AddToParser� folder_flags�AddParentFlagsToParser� display_info� AddFormat�command_lib_util� LIST_FORMAT)�parsers � lib/surface/projects/move.py�Argsz Move.Args; sD � ��(�(��0�<�<�V�D��'�'��/�
���!�!�"2�">�">�?� c �> � t j |� t j |j � }t j d� sy t j |t j t j |� � �� }t j |� |S )Na� Your project will be moved. This may alter the policies enforced on your Project, either exposing your Project to more security risk through looser polices or cause an outage through stricter polices. See these public notes on policy implications for more information: https://cloud.google.com/resource-manager/docs/creating-managing-folders#moving-folders-policy-considerations and https://cloud.google.com/resource-manager/docs/migrating-projects-billing#note_on_policy_implications. Once moved, you can move the Project again so long as you have the appropriate permissions. See our public documentation for more information: https://cloud.google.com/resource-manager/docs/creating-managing-folders#moving_a_project_into_a_folder)�parent)
r �CheckParentFlagsr � ParseProject�idr �PromptContinuer �Update�ParentNameToResourceId�GetParentFromFlagsr
�UpdatedResource)�self�args� project_ref�results r �RunzMove.RunA s� � ��!�!�$�'�"�/�/����8�K� � $� $� C�
� �
�
�
���2�2� � +� +�D� 1�3�4�F� ��� �$� �Mr N)�__name__�
__module__� __qualname__�__doc__� staticmethodr r+ � r r r
r
s" � ��6 �@� �@�
r r
N)r/ �
__future__r r r �+googlecloudsdk.api_lib.cloudresourcemanagerr �googlecloudsdk.callioper �#googlecloudsdk.command_lib.projectsr r r r �+googlecloudsdk.command_lib.resource_managerr �googlecloudsdk.corer
�googlecloudsdk.core.consoler �
ReleaseTracks� ReleaseTrack�ALPHA�BETA�Commandr
r1 r r �<module>r> so �� 6� &� � '� D� (� F� H� M� #� 2� ����D�%�%�+�+�T�->�->�-C�-C�D�9�4�<�<� 9� E�9r