0BSrSSKJr SSKJr SSKJr SSKrSSKrSSKJr SSK J r SSK J r SS K J r SS KJr SS KJr SS KJr SS KJr SSKJr SSKJr SSKJr SSKJr \R8"5S5r\R<"SS\R>55r g)z3Implementation of create command for notifications.)absolute_import)division)unicode_literalsN) exceptions) api_factory) cloud_api)errors) error_util)apis) arg_parsers)base)#notification_configuration_iterator) storage_url)log) propertiesc [R"SS5n[R"SS5nURR UR US95 [ R"SU-5 SnURRUR!US 95nUR#S S U-/S9nXR$;awUR$R'U5 URR)UR+UUR-US9S95n [ R"SRU 55 g [ R"SRX55 U$![RaknURS:waeURRURUS95n[ R"SRU55 S nS nAGNcS nAff=f)aEnsures that topic with SA permissions exists, creating it if needed. Args: topic_name (str): Name of the Cloud Pub/Sub topic to use or create. service_account_email (str): The project service account for Google Cloud Storage. This SA needs publish permission on the PubSub topic. Returns: True if topic was created or had its IAM permissions modified. Otherwise, False. pubsubv1)topiczTopic already exists: Fi)namezCreated topic: {}TN)resourcezroles/pubsub.publisherzserviceAccount:)rolemembers)policy)rsetIamPolicyRequestzUpdated topic IAM policy: {}zFProject service account {} already has publish permission for topic {})r GetClientInstanceGetMessagesModuleprojects_topicsGetPubsubProjectsTopicsGetRequestrwarningapitools_exceptions HttpError status_codeCreateTopicinfoformat GetIamPolicy'PubsubProjectsTopicsGetIamPolicyRequestBindingbindingsappend SetIamPolicy'PubsubProjectsTopicsSetIamPolicyRequestSetIamPolicyRequest) topic_nameservice_account_email pubsub_clientpubsub_messagescreated_new_topice new_topictopic_iam_policyexpected_bindingupdated_topic_iam_policys 3lib/surface/storage/buckets/notifications/create.py_maybe_create_or_modify_topicr<'s((48-**8T:/ !!%%66Z6HJKK(:56#22??==> %,, # #889-;666$$%56,<<II?? / C C'!D!) @ * + HH , 3 34L MN KKP % 24 G  & &}} --44:.0IHH ! ( ( 34sAEG0A GGc8\rSrSrSrSSS.r\S5rSrSr g ) r%bz0Create a notification configuration on a bucket.a *{command}* creates a notification configuration on a bucket, establishing a flow of event notifications from Cloud Storage to a Cloud Pub/Sub topic. As part of creating this flow, it also verifies that the destination Cloud Pub/Sub topic exists, creating it if necessary, and verifies that the Cloud Storage bucket has permission to publish events to that topic, granting the permission if necessary. If a destination Cloud Pub/Sub topic is not specified with the `-t` flag, Cloud Storage chooses a topic name in the default project whose ID is the same as the bucket name. For example, if the default project ID specified is `default-project` and the bucket being configured is `gs://example-bucket`, the create command uses the Cloud Pub/Sub topic `projects/default-project/topics/example-bucket`. In order to enable notifications, your project's [Cloud Storage service agent](https://cloud.google.com/storage/docs/projects#service-accounts) must have the IAM permission "pubsub.topics.publish". This command checks to see if the destination Cloud Pub/Sub topic grants the service agent this permission. If not, the create command attempts to grant it. A bucket can have up to 100 total notification configurations and up to 10 notification configurations set to trigger for a specific event. a Send notifications of all changes to the bucket `example-bucket` to the Cloud Pub/Sub topic `projects/default-project/topics/example-bucket`: $ {command} gs://example-bucket The same as the above but sends no notification payload: $ {command} --payload-format=none gs://example-bucket Include custom metadata in notification payloads: $ {command} --custom-attributes=key1:value1,key2:value2 gs://example-bucket Create a notification configuration that only sends an event when a new object has been created or an object is deleted: $ {command} --event-types=OBJECT_FINALIZE,OBJECT_DELETE gs://example-bucket Create a topic and notification configuration that sends events only when they affect objects with the prefix `photos/`: $ {command} --object-prefix=photos/ gs://example-bucket Specifies the destination topic ID `files-to-process` in the default project: $ {command} --topic=files-to-process gs://example-bucket The same as above but specifies a Cloud Pub/Sub topic belonging to the specific cloud project `example-project`: $ {command} --topic=projects/example-project/topics/files-to-process gs://example-bucket Skip creating a topic when creating the notification configuraiton: $ {command} --skip-topic-setup gs://example-bucket ) DESCRIPTIONEXAMPLESc dURSSS9 URSSS[R"5SS9 URS S S [R"[ [ R Vs/sHoRPM sn5S 9S S9 URSSSS9 URSS[ [ RVs/sHoRPM sn5[ RRRSS9 URSSSSS9 URSSSS9 gs snfs snf)Nurlz>URL of the bucket to create the notification configuration on.)helpz-mz--custom-attributesz KEY=VALUEzSpecifies key:value attributes that are appended to the set of attributes sent to Cloud Pub/Sub for all events associated with this notification configuration.)metavartyperCz-ez --event-typesNOTIFICATION_EVENT_TYPE)choicesaSpecify event type filters for this notification configuration. Cloud Storage will send notifications of only these types. By default, Cloud Storage sends notifications for all event types. * OBJECT_FINALIZE: An object has been created. * OBJECT_METADATA_UPDATE: The metadata of an object has changed. * OBJECT_DELETE: An object has been permanently deleted. * OBJECT_ARCHIVE: A live version of an object has become a noncurrent version.z-pz--object-prefixzSpecifies a prefix path for this notification configuration. Cloud Storage will send notifications for only objects in the bucket whose names begin with the prefix.z-fz--payload-formatzSpecifies the payload format of notification messages. Notification details are available in the message attributes. 'none' sends no payload.)rGdefaultrCz-sz--skip-topic-setup store_truezSkips creation and permission assignment of the Cloud Pub/Sub topic. This is useful if the caller does not have permission to access the topic in question, or if the topic already exists and has the appropriate publish permission assigned.)actionrCz-tz--topiczSpecifies the Cloud Pub/Sub topic to send notifications to. If not specified, this command chooses a topic whose project is your default project and whose ID is the same as the Cloud Storage bucket name.) add_argumentr ArgDictArgListsortedrNotificationEventTypevalueNotificationPayloadFormatJSON)parserstatuss r;Args Create.Argssm      ", -  )  ,5,K,KL,K&,KLNO #%   56   (1(K(K L(Kf\\(K LN3388>>$ %  8 9  &'CM( Ms ,D(D-c <[RRRR 5n[ R "UR5n[R"U5 UR(dSRX#R5nO[URRS5(d/SRUURRS5S5nO URn[R "[ R"R$5nUR&(dpUR)UR5R*R,nUR/US9n[0R2"SRXBU55 [5XG5nOSnUR6(a1UR6V s/sHn [8R:"U 5PM n n OSn [<R>"UR@UUURBU URD[8RF"URH5S9n U "5$s sn f![JRLa> U(de[0RN"S 5 [PRR"S 5 U "5s$f=f) Nzprojects/{}/topics/{}z projects//)project_numberzDChecking for topic {} with access for project {} service account {}.F)custom_attributes event_typesobject_name_prefixpayload_formatz`Retrying create notification request because topic changes may take up to 10 seconds to process. )*rVALUEScoreproject GetOrFailrstorage_url_from_stringrBr*raise_error_if_not_gcs_bucket_matching_urlrr( bucket_name startswith rpartitionrget_apiProviderPrefixGCSskip_topic_setup get_bucketmetadata projectNumberget_service_agentrr'r<r\rrO functoolspartial!create_notification_configurationr[ object_prefixrQr^ api_errors CloudApiErrorr!timesleep) selfargs project_idrBr1 gcs_clientbucket_project_numberr2(created_new_topic_or_set_new_permissions event_typer\rss r;Run Create.Runs/""''//99;J  - -dhh 7C'RR  ::*11*ooNj ZZ " "; / /*11  **   $R (*j::j$$[%?%?%C%CDJ  )33 //#8MM)::.;0 hh P 6**? @B2O 2-.27. !,,,j  ) )* 5,k k(1(9(944 00-- ::4;N;NO)Q% 1 . 00  # #1 5  kk /0 jjn . 001s I=I AJJN) __name__ __module__ __qualname____firstlineno____doc__ detailed_help staticmethodrUr__static_attributes__rr;r%r%bs28 4& 9C-J:':'x:1rr%)!r __future__rrrrqrwapitools.base.pyrr"googlecloudsdk.api_lib.storagerrr ru'googlecloudsdk.api_lib.storage.gcs_jsonr googlecloudsdk.api_lib.utilr googlecloudsdk.callioper r "googlecloudsdk.command_lib.storagerrgooglecloudsdk.corerr$catch_http_error_raise_gcs_api_errorr<UniverseCompatibleCommandr%rrr;rs:&' >64?>,/(R:#* 002737t1T\\11r