diff --git a/gapic/templates/%namespace/%name_%version/%sub/services/%service/_shared_macros.j2 b/gapic/templates/%namespace/%name_%version/%sub/services/%service/_shared_macros.j2 index 7ec9de91e..e96594c01 100644 --- a/gapic/templates/%namespace/%name_%version/%sub/services/%service/_shared_macros.j2 +++ b/gapic/templates/%namespace/%name_%version/%sub/services/%service/_shared_macros.j2 @@ -402,11 +402,13 @@ class {{ async_method_name_prefix }}{{ service.name }}RestInterceptor: Override in a subclass to read or manipulate the response or metadata after it is returned by the {{ service.name }} server but before it is returned to user code. - This `post_{{ method.name|snake_case }}_with_metadata` interceptor runs after the - `post_{{ method.name|snake_case }}` iterceptor. If the response is modified in - `post_{{ method.name|snake_case }}`, the modified response will be used in - `post_{{ method.name|snake_case }}_with_metadata`. This `post_{{ method.name|snake_case }}_with_metadata` - interceptor is recommended for new development instead of `post_{{ method.name|snake_case }}`. + + We recommend only using this `post_{{ method.name|snake_case }}_with_metadata` + interceptor in new development instead of the `post_{{ method.name|snake_case }}` interceptor. + When both interceptors are used, this `post_{{ method.name|snake_case }}_with_metadata` interceptor runs after the + `post_{{ method.name|snake_case }}` interceptor. The (possibly modified) response returned by + `post_{{ method.name|snake_case }}` will be passed to + `post_{{ method.name|snake_case }}_with_metadata`. """ return response, metadata diff --git a/tests/integration/goldens/asset/google/cloud/asset_v1/services/asset_service/transports/rest.py b/tests/integration/goldens/asset/google/cloud/asset_v1/services/asset_service/transports/rest.py index a96e87b04..f222a8a46 100755 --- a/tests/integration/goldens/asset/google/cloud/asset_v1/services/asset_service/transports/rest.py +++ b/tests/integration/goldens/asset/google/cloud/asset_v1/services/asset_service/transports/rest.py @@ -283,11 +283,13 @@ def post_analyze_iam_policy_with_metadata(self, response: asset_service.AnalyzeI Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_analyze_iam_policy_with_metadata` interceptor runs after the - `post_analyze_iam_policy` iterceptor. If the response is modified in - `post_analyze_iam_policy`, the modified response will be used in - `post_analyze_iam_policy_with_metadata`. This `post_analyze_iam_policy_with_metadata` - interceptor is recommended for new development instead of `post_analyze_iam_policy`. + + We recommend only using this `post_analyze_iam_policy_with_metadata` + interceptor in new development instead of the `post_analyze_iam_policy` interceptor. + When both interceptors are used, this `post_analyze_iam_policy_with_metadata` interceptor runs after the + `post_analyze_iam_policy` interceptor. The (possibly modified) response returned by + `post_analyze_iam_policy` will be passed to + `post_analyze_iam_policy_with_metadata`. """ return response, metadata @@ -317,11 +319,13 @@ def post_analyze_iam_policy_longrunning_with_metadata(self, response: operations Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_analyze_iam_policy_longrunning_with_metadata` interceptor runs after the - `post_analyze_iam_policy_longrunning` iterceptor. If the response is modified in - `post_analyze_iam_policy_longrunning`, the modified response will be used in - `post_analyze_iam_policy_longrunning_with_metadata`. This `post_analyze_iam_policy_longrunning_with_metadata` - interceptor is recommended for new development instead of `post_analyze_iam_policy_longrunning`. + + We recommend only using this `post_analyze_iam_policy_longrunning_with_metadata` + interceptor in new development instead of the `post_analyze_iam_policy_longrunning` interceptor. + When both interceptors are used, this `post_analyze_iam_policy_longrunning_with_metadata` interceptor runs after the + `post_analyze_iam_policy_longrunning` interceptor. The (possibly modified) response returned by + `post_analyze_iam_policy_longrunning` will be passed to + `post_analyze_iam_policy_longrunning_with_metadata`. """ return response, metadata @@ -351,11 +355,13 @@ def post_analyze_move_with_metadata(self, response: asset_service.AnalyzeMoveRes Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_analyze_move_with_metadata` interceptor runs after the - `post_analyze_move` iterceptor. If the response is modified in - `post_analyze_move`, the modified response will be used in - `post_analyze_move_with_metadata`. This `post_analyze_move_with_metadata` - interceptor is recommended for new development instead of `post_analyze_move`. + + We recommend only using this `post_analyze_move_with_metadata` + interceptor in new development instead of the `post_analyze_move` interceptor. + When both interceptors are used, this `post_analyze_move_with_metadata` interceptor runs after the + `post_analyze_move` interceptor. The (possibly modified) response returned by + `post_analyze_move` will be passed to + `post_analyze_move_with_metadata`. """ return response, metadata @@ -385,11 +391,13 @@ def post_analyze_org_policies_with_metadata(self, response: asset_service.Analyz Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_analyze_org_policies_with_metadata` interceptor runs after the - `post_analyze_org_policies` iterceptor. If the response is modified in - `post_analyze_org_policies`, the modified response will be used in - `post_analyze_org_policies_with_metadata`. This `post_analyze_org_policies_with_metadata` - interceptor is recommended for new development instead of `post_analyze_org_policies`. + + We recommend only using this `post_analyze_org_policies_with_metadata` + interceptor in new development instead of the `post_analyze_org_policies` interceptor. + When both interceptors are used, this `post_analyze_org_policies_with_metadata` interceptor runs after the + `post_analyze_org_policies` interceptor. The (possibly modified) response returned by + `post_analyze_org_policies` will be passed to + `post_analyze_org_policies_with_metadata`. """ return response, metadata @@ -419,11 +427,13 @@ def post_analyze_org_policy_governed_assets_with_metadata(self, response: asset_ Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_analyze_org_policy_governed_assets_with_metadata` interceptor runs after the - `post_analyze_org_policy_governed_assets` iterceptor. If the response is modified in - `post_analyze_org_policy_governed_assets`, the modified response will be used in - `post_analyze_org_policy_governed_assets_with_metadata`. This `post_analyze_org_policy_governed_assets_with_metadata` - interceptor is recommended for new development instead of `post_analyze_org_policy_governed_assets`. + + We recommend only using this `post_analyze_org_policy_governed_assets_with_metadata` + interceptor in new development instead of the `post_analyze_org_policy_governed_assets` interceptor. + When both interceptors are used, this `post_analyze_org_policy_governed_assets_with_metadata` interceptor runs after the + `post_analyze_org_policy_governed_assets` interceptor. The (possibly modified) response returned by + `post_analyze_org_policy_governed_assets` will be passed to + `post_analyze_org_policy_governed_assets_with_metadata`. """ return response, metadata @@ -453,11 +463,13 @@ def post_analyze_org_policy_governed_containers_with_metadata(self, response: as Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_analyze_org_policy_governed_containers_with_metadata` interceptor runs after the - `post_analyze_org_policy_governed_containers` iterceptor. If the response is modified in - `post_analyze_org_policy_governed_containers`, the modified response will be used in - `post_analyze_org_policy_governed_containers_with_metadata`. This `post_analyze_org_policy_governed_containers_with_metadata` - interceptor is recommended for new development instead of `post_analyze_org_policy_governed_containers`. + + We recommend only using this `post_analyze_org_policy_governed_containers_with_metadata` + interceptor in new development instead of the `post_analyze_org_policy_governed_containers` interceptor. + When both interceptors are used, this `post_analyze_org_policy_governed_containers_with_metadata` interceptor runs after the + `post_analyze_org_policy_governed_containers` interceptor. The (possibly modified) response returned by + `post_analyze_org_policy_governed_containers` will be passed to + `post_analyze_org_policy_governed_containers_with_metadata`. """ return response, metadata @@ -487,11 +499,13 @@ def post_batch_get_assets_history_with_metadata(self, response: asset_service.Ba Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_batch_get_assets_history_with_metadata` interceptor runs after the - `post_batch_get_assets_history` iterceptor. If the response is modified in - `post_batch_get_assets_history`, the modified response will be used in - `post_batch_get_assets_history_with_metadata`. This `post_batch_get_assets_history_with_metadata` - interceptor is recommended for new development instead of `post_batch_get_assets_history`. + + We recommend only using this `post_batch_get_assets_history_with_metadata` + interceptor in new development instead of the `post_batch_get_assets_history` interceptor. + When both interceptors are used, this `post_batch_get_assets_history_with_metadata` interceptor runs after the + `post_batch_get_assets_history` interceptor. The (possibly modified) response returned by + `post_batch_get_assets_history` will be passed to + `post_batch_get_assets_history_with_metadata`. """ return response, metadata @@ -521,11 +535,13 @@ def post_batch_get_effective_iam_policies_with_metadata(self, response: asset_se Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_batch_get_effective_iam_policies_with_metadata` interceptor runs after the - `post_batch_get_effective_iam_policies` iterceptor. If the response is modified in - `post_batch_get_effective_iam_policies`, the modified response will be used in - `post_batch_get_effective_iam_policies_with_metadata`. This `post_batch_get_effective_iam_policies_with_metadata` - interceptor is recommended for new development instead of `post_batch_get_effective_iam_policies`. + + We recommend only using this `post_batch_get_effective_iam_policies_with_metadata` + interceptor in new development instead of the `post_batch_get_effective_iam_policies` interceptor. + When both interceptors are used, this `post_batch_get_effective_iam_policies_with_metadata` interceptor runs after the + `post_batch_get_effective_iam_policies` interceptor. The (possibly modified) response returned by + `post_batch_get_effective_iam_policies` will be passed to + `post_batch_get_effective_iam_policies_with_metadata`. """ return response, metadata @@ -555,11 +571,13 @@ def post_create_feed_with_metadata(self, response: asset_service.Feed, metadata: Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_create_feed_with_metadata` interceptor runs after the - `post_create_feed` iterceptor. If the response is modified in - `post_create_feed`, the modified response will be used in - `post_create_feed_with_metadata`. This `post_create_feed_with_metadata` - interceptor is recommended for new development instead of `post_create_feed`. + + We recommend only using this `post_create_feed_with_metadata` + interceptor in new development instead of the `post_create_feed` interceptor. + When both interceptors are used, this `post_create_feed_with_metadata` interceptor runs after the + `post_create_feed` interceptor. The (possibly modified) response returned by + `post_create_feed` will be passed to + `post_create_feed_with_metadata`. """ return response, metadata @@ -589,11 +607,13 @@ def post_create_saved_query_with_metadata(self, response: asset_service.SavedQue Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_create_saved_query_with_metadata` interceptor runs after the - `post_create_saved_query` iterceptor. If the response is modified in - `post_create_saved_query`, the modified response will be used in - `post_create_saved_query_with_metadata`. This `post_create_saved_query_with_metadata` - interceptor is recommended for new development instead of `post_create_saved_query`. + + We recommend only using this `post_create_saved_query_with_metadata` + interceptor in new development instead of the `post_create_saved_query` interceptor. + When both interceptors are used, this `post_create_saved_query_with_metadata` interceptor runs after the + `post_create_saved_query` interceptor. The (possibly modified) response returned by + `post_create_saved_query` will be passed to + `post_create_saved_query_with_metadata`. """ return response, metadata @@ -639,11 +659,13 @@ def post_export_assets_with_metadata(self, response: operations_pb2.Operation, m Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_export_assets_with_metadata` interceptor runs after the - `post_export_assets` iterceptor. If the response is modified in - `post_export_assets`, the modified response will be used in - `post_export_assets_with_metadata`. This `post_export_assets_with_metadata` - interceptor is recommended for new development instead of `post_export_assets`. + + We recommend only using this `post_export_assets_with_metadata` + interceptor in new development instead of the `post_export_assets` interceptor. + When both interceptors are used, this `post_export_assets_with_metadata` interceptor runs after the + `post_export_assets` interceptor. The (possibly modified) response returned by + `post_export_assets` will be passed to + `post_export_assets_with_metadata`. """ return response, metadata @@ -673,11 +695,13 @@ def post_get_feed_with_metadata(self, response: asset_service.Feed, metadata: Se Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_get_feed_with_metadata` interceptor runs after the - `post_get_feed` iterceptor. If the response is modified in - `post_get_feed`, the modified response will be used in - `post_get_feed_with_metadata`. This `post_get_feed_with_metadata` - interceptor is recommended for new development instead of `post_get_feed`. + + We recommend only using this `post_get_feed_with_metadata` + interceptor in new development instead of the `post_get_feed` interceptor. + When both interceptors are used, this `post_get_feed_with_metadata` interceptor runs after the + `post_get_feed` interceptor. The (possibly modified) response returned by + `post_get_feed` will be passed to + `post_get_feed_with_metadata`. """ return response, metadata @@ -707,11 +731,13 @@ def post_get_saved_query_with_metadata(self, response: asset_service.SavedQuery, Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_get_saved_query_with_metadata` interceptor runs after the - `post_get_saved_query` iterceptor. If the response is modified in - `post_get_saved_query`, the modified response will be used in - `post_get_saved_query_with_metadata`. This `post_get_saved_query_with_metadata` - interceptor is recommended for new development instead of `post_get_saved_query`. + + We recommend only using this `post_get_saved_query_with_metadata` + interceptor in new development instead of the `post_get_saved_query` interceptor. + When both interceptors are used, this `post_get_saved_query_with_metadata` interceptor runs after the + `post_get_saved_query` interceptor. The (possibly modified) response returned by + `post_get_saved_query` will be passed to + `post_get_saved_query_with_metadata`. """ return response, metadata @@ -741,11 +767,13 @@ def post_list_assets_with_metadata(self, response: asset_service.ListAssetsRespo Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_list_assets_with_metadata` interceptor runs after the - `post_list_assets` iterceptor. If the response is modified in - `post_list_assets`, the modified response will be used in - `post_list_assets_with_metadata`. This `post_list_assets_with_metadata` - interceptor is recommended for new development instead of `post_list_assets`. + + We recommend only using this `post_list_assets_with_metadata` + interceptor in new development instead of the `post_list_assets` interceptor. + When both interceptors are used, this `post_list_assets_with_metadata` interceptor runs after the + `post_list_assets` interceptor. The (possibly modified) response returned by + `post_list_assets` will be passed to + `post_list_assets_with_metadata`. """ return response, metadata @@ -775,11 +803,13 @@ def post_list_feeds_with_metadata(self, response: asset_service.ListFeedsRespons Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_list_feeds_with_metadata` interceptor runs after the - `post_list_feeds` iterceptor. If the response is modified in - `post_list_feeds`, the modified response will be used in - `post_list_feeds_with_metadata`. This `post_list_feeds_with_metadata` - interceptor is recommended for new development instead of `post_list_feeds`. + + We recommend only using this `post_list_feeds_with_metadata` + interceptor in new development instead of the `post_list_feeds` interceptor. + When both interceptors are used, this `post_list_feeds_with_metadata` interceptor runs after the + `post_list_feeds` interceptor. The (possibly modified) response returned by + `post_list_feeds` will be passed to + `post_list_feeds_with_metadata`. """ return response, metadata @@ -809,11 +839,13 @@ def post_list_saved_queries_with_metadata(self, response: asset_service.ListSave Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_list_saved_queries_with_metadata` interceptor runs after the - `post_list_saved_queries` iterceptor. If the response is modified in - `post_list_saved_queries`, the modified response will be used in - `post_list_saved_queries_with_metadata`. This `post_list_saved_queries_with_metadata` - interceptor is recommended for new development instead of `post_list_saved_queries`. + + We recommend only using this `post_list_saved_queries_with_metadata` + interceptor in new development instead of the `post_list_saved_queries` interceptor. + When both interceptors are used, this `post_list_saved_queries_with_metadata` interceptor runs after the + `post_list_saved_queries` interceptor. The (possibly modified) response returned by + `post_list_saved_queries` will be passed to + `post_list_saved_queries_with_metadata`. """ return response, metadata @@ -843,11 +875,13 @@ def post_query_assets_with_metadata(self, response: asset_service.QueryAssetsRes Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_query_assets_with_metadata` interceptor runs after the - `post_query_assets` iterceptor. If the response is modified in - `post_query_assets`, the modified response will be used in - `post_query_assets_with_metadata`. This `post_query_assets_with_metadata` - interceptor is recommended for new development instead of `post_query_assets`. + + We recommend only using this `post_query_assets_with_metadata` + interceptor in new development instead of the `post_query_assets` interceptor. + When both interceptors are used, this `post_query_assets_with_metadata` interceptor runs after the + `post_query_assets` interceptor. The (possibly modified) response returned by + `post_query_assets` will be passed to + `post_query_assets_with_metadata`. """ return response, metadata @@ -877,11 +911,13 @@ def post_search_all_iam_policies_with_metadata(self, response: asset_service.Sea Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_search_all_iam_policies_with_metadata` interceptor runs after the - `post_search_all_iam_policies` iterceptor. If the response is modified in - `post_search_all_iam_policies`, the modified response will be used in - `post_search_all_iam_policies_with_metadata`. This `post_search_all_iam_policies_with_metadata` - interceptor is recommended for new development instead of `post_search_all_iam_policies`. + + We recommend only using this `post_search_all_iam_policies_with_metadata` + interceptor in new development instead of the `post_search_all_iam_policies` interceptor. + When both interceptors are used, this `post_search_all_iam_policies_with_metadata` interceptor runs after the + `post_search_all_iam_policies` interceptor. The (possibly modified) response returned by + `post_search_all_iam_policies` will be passed to + `post_search_all_iam_policies_with_metadata`. """ return response, metadata @@ -911,11 +947,13 @@ def post_search_all_resources_with_metadata(self, response: asset_service.Search Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_search_all_resources_with_metadata` interceptor runs after the - `post_search_all_resources` iterceptor. If the response is modified in - `post_search_all_resources`, the modified response will be used in - `post_search_all_resources_with_metadata`. This `post_search_all_resources_with_metadata` - interceptor is recommended for new development instead of `post_search_all_resources`. + + We recommend only using this `post_search_all_resources_with_metadata` + interceptor in new development instead of the `post_search_all_resources` interceptor. + When both interceptors are used, this `post_search_all_resources_with_metadata` interceptor runs after the + `post_search_all_resources` interceptor. The (possibly modified) response returned by + `post_search_all_resources` will be passed to + `post_search_all_resources_with_metadata`. """ return response, metadata @@ -945,11 +983,13 @@ def post_update_feed_with_metadata(self, response: asset_service.Feed, metadata: Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_update_feed_with_metadata` interceptor runs after the - `post_update_feed` iterceptor. If the response is modified in - `post_update_feed`, the modified response will be used in - `post_update_feed_with_metadata`. This `post_update_feed_with_metadata` - interceptor is recommended for new development instead of `post_update_feed`. + + We recommend only using this `post_update_feed_with_metadata` + interceptor in new development instead of the `post_update_feed` interceptor. + When both interceptors are used, this `post_update_feed_with_metadata` interceptor runs after the + `post_update_feed` interceptor. The (possibly modified) response returned by + `post_update_feed` will be passed to + `post_update_feed_with_metadata`. """ return response, metadata @@ -979,11 +1019,13 @@ def post_update_saved_query_with_metadata(self, response: asset_service.SavedQue Override in a subclass to read or manipulate the response or metadata after it is returned by the AssetService server but before it is returned to user code. - This `post_update_saved_query_with_metadata` interceptor runs after the - `post_update_saved_query` iterceptor. If the response is modified in - `post_update_saved_query`, the modified response will be used in - `post_update_saved_query_with_metadata`. This `post_update_saved_query_with_metadata` - interceptor is recommended for new development instead of `post_update_saved_query`. + + We recommend only using this `post_update_saved_query_with_metadata` + interceptor in new development instead of the `post_update_saved_query` interceptor. + When both interceptors are used, this `post_update_saved_query_with_metadata` interceptor runs after the + `post_update_saved_query` interceptor. The (possibly modified) response returned by + `post_update_saved_query` will be passed to + `post_update_saved_query_with_metadata`. """ return response, metadata diff --git a/tests/integration/goldens/credentials/google/iam/credentials_v1/services/iam_credentials/transports/rest.py b/tests/integration/goldens/credentials/google/iam/credentials_v1/services/iam_credentials/transports/rest.py index 75e9ebf34..9dc7959ac 100755 --- a/tests/integration/goldens/credentials/google/iam/credentials_v1/services/iam_credentials/transports/rest.py +++ b/tests/integration/goldens/credentials/google/iam/credentials_v1/services/iam_credentials/transports/rest.py @@ -136,11 +136,13 @@ def post_generate_access_token_with_metadata(self, response: common.GenerateAcce Override in a subclass to read or manipulate the response or metadata after it is returned by the IAMCredentials server but before it is returned to user code. - This `post_generate_access_token_with_metadata` interceptor runs after the - `post_generate_access_token` iterceptor. If the response is modified in - `post_generate_access_token`, the modified response will be used in - `post_generate_access_token_with_metadata`. This `post_generate_access_token_with_metadata` - interceptor is recommended for new development instead of `post_generate_access_token`. + + We recommend only using this `post_generate_access_token_with_metadata` + interceptor in new development instead of the `post_generate_access_token` interceptor. + When both interceptors are used, this `post_generate_access_token_with_metadata` interceptor runs after the + `post_generate_access_token` interceptor. The (possibly modified) response returned by + `post_generate_access_token` will be passed to + `post_generate_access_token_with_metadata`. """ return response, metadata @@ -170,11 +172,13 @@ def post_generate_id_token_with_metadata(self, response: common.GenerateIdTokenR Override in a subclass to read or manipulate the response or metadata after it is returned by the IAMCredentials server but before it is returned to user code. - This `post_generate_id_token_with_metadata` interceptor runs after the - `post_generate_id_token` iterceptor. If the response is modified in - `post_generate_id_token`, the modified response will be used in - `post_generate_id_token_with_metadata`. This `post_generate_id_token_with_metadata` - interceptor is recommended for new development instead of `post_generate_id_token`. + + We recommend only using this `post_generate_id_token_with_metadata` + interceptor in new development instead of the `post_generate_id_token` interceptor. + When both interceptors are used, this `post_generate_id_token_with_metadata` interceptor runs after the + `post_generate_id_token` interceptor. The (possibly modified) response returned by + `post_generate_id_token` will be passed to + `post_generate_id_token_with_metadata`. """ return response, metadata @@ -204,11 +208,13 @@ def post_sign_blob_with_metadata(self, response: common.SignBlobResponse, metada Override in a subclass to read or manipulate the response or metadata after it is returned by the IAMCredentials server but before it is returned to user code. - This `post_sign_blob_with_metadata` interceptor runs after the - `post_sign_blob` iterceptor. If the response is modified in - `post_sign_blob`, the modified response will be used in - `post_sign_blob_with_metadata`. This `post_sign_blob_with_metadata` - interceptor is recommended for new development instead of `post_sign_blob`. + + We recommend only using this `post_sign_blob_with_metadata` + interceptor in new development instead of the `post_sign_blob` interceptor. + When both interceptors are used, this `post_sign_blob_with_metadata` interceptor runs after the + `post_sign_blob` interceptor. The (possibly modified) response returned by + `post_sign_blob` will be passed to + `post_sign_blob_with_metadata`. """ return response, metadata @@ -238,11 +244,13 @@ def post_sign_jwt_with_metadata(self, response: common.SignJwtResponse, metadata Override in a subclass to read or manipulate the response or metadata after it is returned by the IAMCredentials server but before it is returned to user code. - This `post_sign_jwt_with_metadata` interceptor runs after the - `post_sign_jwt` iterceptor. If the response is modified in - `post_sign_jwt`, the modified response will be used in - `post_sign_jwt_with_metadata`. This `post_sign_jwt_with_metadata` - interceptor is recommended for new development instead of `post_sign_jwt`. + + We recommend only using this `post_sign_jwt_with_metadata` + interceptor in new development instead of the `post_sign_jwt` interceptor. + When both interceptors are used, this `post_sign_jwt_with_metadata` interceptor runs after the + `post_sign_jwt` interceptor. The (possibly modified) response returned by + `post_sign_jwt` will be passed to + `post_sign_jwt_with_metadata`. """ return response, metadata diff --git a/tests/integration/goldens/eventarc/google/cloud/eventarc_v1/services/eventarc/transports/rest.py b/tests/integration/goldens/eventarc/google/cloud/eventarc_v1/services/eventarc/transports/rest.py index 30c6869c5..32211ddf9 100755 --- a/tests/integration/goldens/eventarc/google/cloud/eventarc_v1/services/eventarc/transports/rest.py +++ b/tests/integration/goldens/eventarc/google/cloud/eventarc_v1/services/eventarc/transports/rest.py @@ -259,11 +259,13 @@ def post_create_channel_with_metadata(self, response: operations_pb2.Operation, Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_create_channel_with_metadata` interceptor runs after the - `post_create_channel` iterceptor. If the response is modified in - `post_create_channel`, the modified response will be used in - `post_create_channel_with_metadata`. This `post_create_channel_with_metadata` - interceptor is recommended for new development instead of `post_create_channel`. + + We recommend only using this `post_create_channel_with_metadata` + interceptor in new development instead of the `post_create_channel` interceptor. + When both interceptors are used, this `post_create_channel_with_metadata` interceptor runs after the + `post_create_channel` interceptor. The (possibly modified) response returned by + `post_create_channel` will be passed to + `post_create_channel_with_metadata`. """ return response, metadata @@ -293,11 +295,13 @@ def post_create_channel_connection_with_metadata(self, response: operations_pb2. Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_create_channel_connection_with_metadata` interceptor runs after the - `post_create_channel_connection` iterceptor. If the response is modified in - `post_create_channel_connection`, the modified response will be used in - `post_create_channel_connection_with_metadata`. This `post_create_channel_connection_with_metadata` - interceptor is recommended for new development instead of `post_create_channel_connection`. + + We recommend only using this `post_create_channel_connection_with_metadata` + interceptor in new development instead of the `post_create_channel_connection` interceptor. + When both interceptors are used, this `post_create_channel_connection_with_metadata` interceptor runs after the + `post_create_channel_connection` interceptor. The (possibly modified) response returned by + `post_create_channel_connection` will be passed to + `post_create_channel_connection_with_metadata`. """ return response, metadata @@ -327,11 +331,13 @@ def post_create_trigger_with_metadata(self, response: operations_pb2.Operation, Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_create_trigger_with_metadata` interceptor runs after the - `post_create_trigger` iterceptor. If the response is modified in - `post_create_trigger`, the modified response will be used in - `post_create_trigger_with_metadata`. This `post_create_trigger_with_metadata` - interceptor is recommended for new development instead of `post_create_trigger`. + + We recommend only using this `post_create_trigger_with_metadata` + interceptor in new development instead of the `post_create_trigger` interceptor. + When both interceptors are used, this `post_create_trigger_with_metadata` interceptor runs after the + `post_create_trigger` interceptor. The (possibly modified) response returned by + `post_create_trigger` will be passed to + `post_create_trigger_with_metadata`. """ return response, metadata @@ -361,11 +367,13 @@ def post_delete_channel_with_metadata(self, response: operations_pb2.Operation, Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_delete_channel_with_metadata` interceptor runs after the - `post_delete_channel` iterceptor. If the response is modified in - `post_delete_channel`, the modified response will be used in - `post_delete_channel_with_metadata`. This `post_delete_channel_with_metadata` - interceptor is recommended for new development instead of `post_delete_channel`. + + We recommend only using this `post_delete_channel_with_metadata` + interceptor in new development instead of the `post_delete_channel` interceptor. + When both interceptors are used, this `post_delete_channel_with_metadata` interceptor runs after the + `post_delete_channel` interceptor. The (possibly modified) response returned by + `post_delete_channel` will be passed to + `post_delete_channel_with_metadata`. """ return response, metadata @@ -395,11 +403,13 @@ def post_delete_channel_connection_with_metadata(self, response: operations_pb2. Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_delete_channel_connection_with_metadata` interceptor runs after the - `post_delete_channel_connection` iterceptor. If the response is modified in - `post_delete_channel_connection`, the modified response will be used in - `post_delete_channel_connection_with_metadata`. This `post_delete_channel_connection_with_metadata` - interceptor is recommended for new development instead of `post_delete_channel_connection`. + + We recommend only using this `post_delete_channel_connection_with_metadata` + interceptor in new development instead of the `post_delete_channel_connection` interceptor. + When both interceptors are used, this `post_delete_channel_connection_with_metadata` interceptor runs after the + `post_delete_channel_connection` interceptor. The (possibly modified) response returned by + `post_delete_channel_connection` will be passed to + `post_delete_channel_connection_with_metadata`. """ return response, metadata @@ -429,11 +439,13 @@ def post_delete_trigger_with_metadata(self, response: operations_pb2.Operation, Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_delete_trigger_with_metadata` interceptor runs after the - `post_delete_trigger` iterceptor. If the response is modified in - `post_delete_trigger`, the modified response will be used in - `post_delete_trigger_with_metadata`. This `post_delete_trigger_with_metadata` - interceptor is recommended for new development instead of `post_delete_trigger`. + + We recommend only using this `post_delete_trigger_with_metadata` + interceptor in new development instead of the `post_delete_trigger` interceptor. + When both interceptors are used, this `post_delete_trigger_with_metadata` interceptor runs after the + `post_delete_trigger` interceptor. The (possibly modified) response returned by + `post_delete_trigger` will be passed to + `post_delete_trigger_with_metadata`. """ return response, metadata @@ -463,11 +475,13 @@ def post_get_channel_with_metadata(self, response: channel.Channel, metadata: Se Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_get_channel_with_metadata` interceptor runs after the - `post_get_channel` iterceptor. If the response is modified in - `post_get_channel`, the modified response will be used in - `post_get_channel_with_metadata`. This `post_get_channel_with_metadata` - interceptor is recommended for new development instead of `post_get_channel`. + + We recommend only using this `post_get_channel_with_metadata` + interceptor in new development instead of the `post_get_channel` interceptor. + When both interceptors are used, this `post_get_channel_with_metadata` interceptor runs after the + `post_get_channel` interceptor. The (possibly modified) response returned by + `post_get_channel` will be passed to + `post_get_channel_with_metadata`. """ return response, metadata @@ -497,11 +511,13 @@ def post_get_channel_connection_with_metadata(self, response: channel_connection Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_get_channel_connection_with_metadata` interceptor runs after the - `post_get_channel_connection` iterceptor. If the response is modified in - `post_get_channel_connection`, the modified response will be used in - `post_get_channel_connection_with_metadata`. This `post_get_channel_connection_with_metadata` - interceptor is recommended for new development instead of `post_get_channel_connection`. + + We recommend only using this `post_get_channel_connection_with_metadata` + interceptor in new development instead of the `post_get_channel_connection` interceptor. + When both interceptors are used, this `post_get_channel_connection_with_metadata` interceptor runs after the + `post_get_channel_connection` interceptor. The (possibly modified) response returned by + `post_get_channel_connection` will be passed to + `post_get_channel_connection_with_metadata`. """ return response, metadata @@ -531,11 +547,13 @@ def post_get_google_channel_config_with_metadata(self, response: google_channel_ Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_get_google_channel_config_with_metadata` interceptor runs after the - `post_get_google_channel_config` iterceptor. If the response is modified in - `post_get_google_channel_config`, the modified response will be used in - `post_get_google_channel_config_with_metadata`. This `post_get_google_channel_config_with_metadata` - interceptor is recommended for new development instead of `post_get_google_channel_config`. + + We recommend only using this `post_get_google_channel_config_with_metadata` + interceptor in new development instead of the `post_get_google_channel_config` interceptor. + When both interceptors are used, this `post_get_google_channel_config_with_metadata` interceptor runs after the + `post_get_google_channel_config` interceptor. The (possibly modified) response returned by + `post_get_google_channel_config` will be passed to + `post_get_google_channel_config_with_metadata`. """ return response, metadata @@ -565,11 +583,13 @@ def post_get_provider_with_metadata(self, response: discovery.Provider, metadata Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_get_provider_with_metadata` interceptor runs after the - `post_get_provider` iterceptor. If the response is modified in - `post_get_provider`, the modified response will be used in - `post_get_provider_with_metadata`. This `post_get_provider_with_metadata` - interceptor is recommended for new development instead of `post_get_provider`. + + We recommend only using this `post_get_provider_with_metadata` + interceptor in new development instead of the `post_get_provider` interceptor. + When both interceptors are used, this `post_get_provider_with_metadata` interceptor runs after the + `post_get_provider` interceptor. The (possibly modified) response returned by + `post_get_provider` will be passed to + `post_get_provider_with_metadata`. """ return response, metadata @@ -599,11 +619,13 @@ def post_get_trigger_with_metadata(self, response: trigger.Trigger, metadata: Se Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_get_trigger_with_metadata` interceptor runs after the - `post_get_trigger` iterceptor. If the response is modified in - `post_get_trigger`, the modified response will be used in - `post_get_trigger_with_metadata`. This `post_get_trigger_with_metadata` - interceptor is recommended for new development instead of `post_get_trigger`. + + We recommend only using this `post_get_trigger_with_metadata` + interceptor in new development instead of the `post_get_trigger` interceptor. + When both interceptors are used, this `post_get_trigger_with_metadata` interceptor runs after the + `post_get_trigger` interceptor. The (possibly modified) response returned by + `post_get_trigger` will be passed to + `post_get_trigger_with_metadata`. """ return response, metadata @@ -633,11 +655,13 @@ def post_list_channel_connections_with_metadata(self, response: eventarc.ListCha Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_list_channel_connections_with_metadata` interceptor runs after the - `post_list_channel_connections` iterceptor. If the response is modified in - `post_list_channel_connections`, the modified response will be used in - `post_list_channel_connections_with_metadata`. This `post_list_channel_connections_with_metadata` - interceptor is recommended for new development instead of `post_list_channel_connections`. + + We recommend only using this `post_list_channel_connections_with_metadata` + interceptor in new development instead of the `post_list_channel_connections` interceptor. + When both interceptors are used, this `post_list_channel_connections_with_metadata` interceptor runs after the + `post_list_channel_connections` interceptor. The (possibly modified) response returned by + `post_list_channel_connections` will be passed to + `post_list_channel_connections_with_metadata`. """ return response, metadata @@ -667,11 +691,13 @@ def post_list_channels_with_metadata(self, response: eventarc.ListChannelsRespon Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_list_channels_with_metadata` interceptor runs after the - `post_list_channels` iterceptor. If the response is modified in - `post_list_channels`, the modified response will be used in - `post_list_channels_with_metadata`. This `post_list_channels_with_metadata` - interceptor is recommended for new development instead of `post_list_channels`. + + We recommend only using this `post_list_channels_with_metadata` + interceptor in new development instead of the `post_list_channels` interceptor. + When both interceptors are used, this `post_list_channels_with_metadata` interceptor runs after the + `post_list_channels` interceptor. The (possibly modified) response returned by + `post_list_channels` will be passed to + `post_list_channels_with_metadata`. """ return response, metadata @@ -701,11 +727,13 @@ def post_list_providers_with_metadata(self, response: eventarc.ListProvidersResp Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_list_providers_with_metadata` interceptor runs after the - `post_list_providers` iterceptor. If the response is modified in - `post_list_providers`, the modified response will be used in - `post_list_providers_with_metadata`. This `post_list_providers_with_metadata` - interceptor is recommended for new development instead of `post_list_providers`. + + We recommend only using this `post_list_providers_with_metadata` + interceptor in new development instead of the `post_list_providers` interceptor. + When both interceptors are used, this `post_list_providers_with_metadata` interceptor runs after the + `post_list_providers` interceptor. The (possibly modified) response returned by + `post_list_providers` will be passed to + `post_list_providers_with_metadata`. """ return response, metadata @@ -735,11 +763,13 @@ def post_list_triggers_with_metadata(self, response: eventarc.ListTriggersRespon Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_list_triggers_with_metadata` interceptor runs after the - `post_list_triggers` iterceptor. If the response is modified in - `post_list_triggers`, the modified response will be used in - `post_list_triggers_with_metadata`. This `post_list_triggers_with_metadata` - interceptor is recommended for new development instead of `post_list_triggers`. + + We recommend only using this `post_list_triggers_with_metadata` + interceptor in new development instead of the `post_list_triggers` interceptor. + When both interceptors are used, this `post_list_triggers_with_metadata` interceptor runs after the + `post_list_triggers` interceptor. The (possibly modified) response returned by + `post_list_triggers` will be passed to + `post_list_triggers_with_metadata`. """ return response, metadata @@ -769,11 +799,13 @@ def post_update_channel_with_metadata(self, response: operations_pb2.Operation, Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_update_channel_with_metadata` interceptor runs after the - `post_update_channel` iterceptor. If the response is modified in - `post_update_channel`, the modified response will be used in - `post_update_channel_with_metadata`. This `post_update_channel_with_metadata` - interceptor is recommended for new development instead of `post_update_channel`. + + We recommend only using this `post_update_channel_with_metadata` + interceptor in new development instead of the `post_update_channel` interceptor. + When both interceptors are used, this `post_update_channel_with_metadata` interceptor runs after the + `post_update_channel` interceptor. The (possibly modified) response returned by + `post_update_channel` will be passed to + `post_update_channel_with_metadata`. """ return response, metadata @@ -803,11 +835,13 @@ def post_update_google_channel_config_with_metadata(self, response: gce_google_c Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_update_google_channel_config_with_metadata` interceptor runs after the - `post_update_google_channel_config` iterceptor. If the response is modified in - `post_update_google_channel_config`, the modified response will be used in - `post_update_google_channel_config_with_metadata`. This `post_update_google_channel_config_with_metadata` - interceptor is recommended for new development instead of `post_update_google_channel_config`. + + We recommend only using this `post_update_google_channel_config_with_metadata` + interceptor in new development instead of the `post_update_google_channel_config` interceptor. + When both interceptors are used, this `post_update_google_channel_config_with_metadata` interceptor runs after the + `post_update_google_channel_config` interceptor. The (possibly modified) response returned by + `post_update_google_channel_config` will be passed to + `post_update_google_channel_config_with_metadata`. """ return response, metadata @@ -837,11 +871,13 @@ def post_update_trigger_with_metadata(self, response: operations_pb2.Operation, Override in a subclass to read or manipulate the response or metadata after it is returned by the Eventarc server but before it is returned to user code. - This `post_update_trigger_with_metadata` interceptor runs after the - `post_update_trigger` iterceptor. If the response is modified in - `post_update_trigger`, the modified response will be used in - `post_update_trigger_with_metadata`. This `post_update_trigger_with_metadata` - interceptor is recommended for new development instead of `post_update_trigger`. + + We recommend only using this `post_update_trigger_with_metadata` + interceptor in new development instead of the `post_update_trigger` interceptor. + When both interceptors are used, this `post_update_trigger_with_metadata` interceptor runs after the + `post_update_trigger` interceptor. The (possibly modified) response returned by + `post_update_trigger` will be passed to + `post_update_trigger_with_metadata`. """ return response, metadata diff --git a/tests/integration/goldens/redis/google/cloud/redis_v1/services/cloud_redis/transports/rest.py b/tests/integration/goldens/redis/google/cloud/redis_v1/services/cloud_redis/transports/rest.py index 32b164701..702c01fb2 100755 --- a/tests/integration/goldens/redis/google/cloud/redis_v1/services/cloud_redis/transports/rest.py +++ b/tests/integration/goldens/redis/google/cloud/redis_v1/services/cloud_redis/transports/rest.py @@ -195,11 +195,13 @@ def post_create_instance_with_metadata(self, response: operations_pb2.Operation, Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_create_instance_with_metadata` interceptor runs after the - `post_create_instance` iterceptor. If the response is modified in - `post_create_instance`, the modified response will be used in - `post_create_instance_with_metadata`. This `post_create_instance_with_metadata` - interceptor is recommended for new development instead of `post_create_instance`. + + We recommend only using this `post_create_instance_with_metadata` + interceptor in new development instead of the `post_create_instance` interceptor. + When both interceptors are used, this `post_create_instance_with_metadata` interceptor runs after the + `post_create_instance` interceptor. The (possibly modified) response returned by + `post_create_instance` will be passed to + `post_create_instance_with_metadata`. """ return response, metadata @@ -229,11 +231,13 @@ def post_delete_instance_with_metadata(self, response: operations_pb2.Operation, Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_delete_instance_with_metadata` interceptor runs after the - `post_delete_instance` iterceptor. If the response is modified in - `post_delete_instance`, the modified response will be used in - `post_delete_instance_with_metadata`. This `post_delete_instance_with_metadata` - interceptor is recommended for new development instead of `post_delete_instance`. + + We recommend only using this `post_delete_instance_with_metadata` + interceptor in new development instead of the `post_delete_instance` interceptor. + When both interceptors are used, this `post_delete_instance_with_metadata` interceptor runs after the + `post_delete_instance` interceptor. The (possibly modified) response returned by + `post_delete_instance` will be passed to + `post_delete_instance_with_metadata`. """ return response, metadata @@ -263,11 +267,13 @@ def post_export_instance_with_metadata(self, response: operations_pb2.Operation, Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_export_instance_with_metadata` interceptor runs after the - `post_export_instance` iterceptor. If the response is modified in - `post_export_instance`, the modified response will be used in - `post_export_instance_with_metadata`. This `post_export_instance_with_metadata` - interceptor is recommended for new development instead of `post_export_instance`. + + We recommend only using this `post_export_instance_with_metadata` + interceptor in new development instead of the `post_export_instance` interceptor. + When both interceptors are used, this `post_export_instance_with_metadata` interceptor runs after the + `post_export_instance` interceptor. The (possibly modified) response returned by + `post_export_instance` will be passed to + `post_export_instance_with_metadata`. """ return response, metadata @@ -297,11 +303,13 @@ def post_failover_instance_with_metadata(self, response: operations_pb2.Operatio Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_failover_instance_with_metadata` interceptor runs after the - `post_failover_instance` iterceptor. If the response is modified in - `post_failover_instance`, the modified response will be used in - `post_failover_instance_with_metadata`. This `post_failover_instance_with_metadata` - interceptor is recommended for new development instead of `post_failover_instance`. + + We recommend only using this `post_failover_instance_with_metadata` + interceptor in new development instead of the `post_failover_instance` interceptor. + When both interceptors are used, this `post_failover_instance_with_metadata` interceptor runs after the + `post_failover_instance` interceptor. The (possibly modified) response returned by + `post_failover_instance` will be passed to + `post_failover_instance_with_metadata`. """ return response, metadata @@ -331,11 +339,13 @@ def post_get_instance_with_metadata(self, response: cloud_redis.Instance, metada Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_get_instance_with_metadata` interceptor runs after the - `post_get_instance` iterceptor. If the response is modified in - `post_get_instance`, the modified response will be used in - `post_get_instance_with_metadata`. This `post_get_instance_with_metadata` - interceptor is recommended for new development instead of `post_get_instance`. + + We recommend only using this `post_get_instance_with_metadata` + interceptor in new development instead of the `post_get_instance` interceptor. + When both interceptors are used, this `post_get_instance_with_metadata` interceptor runs after the + `post_get_instance` interceptor. The (possibly modified) response returned by + `post_get_instance` will be passed to + `post_get_instance_with_metadata`. """ return response, metadata @@ -365,11 +375,13 @@ def post_get_instance_auth_string_with_metadata(self, response: cloud_redis.Inst Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_get_instance_auth_string_with_metadata` interceptor runs after the - `post_get_instance_auth_string` iterceptor. If the response is modified in - `post_get_instance_auth_string`, the modified response will be used in - `post_get_instance_auth_string_with_metadata`. This `post_get_instance_auth_string_with_metadata` - interceptor is recommended for new development instead of `post_get_instance_auth_string`. + + We recommend only using this `post_get_instance_auth_string_with_metadata` + interceptor in new development instead of the `post_get_instance_auth_string` interceptor. + When both interceptors are used, this `post_get_instance_auth_string_with_metadata` interceptor runs after the + `post_get_instance_auth_string` interceptor. The (possibly modified) response returned by + `post_get_instance_auth_string` will be passed to + `post_get_instance_auth_string_with_metadata`. """ return response, metadata @@ -399,11 +411,13 @@ def post_import_instance_with_metadata(self, response: operations_pb2.Operation, Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_import_instance_with_metadata` interceptor runs after the - `post_import_instance` iterceptor. If the response is modified in - `post_import_instance`, the modified response will be used in - `post_import_instance_with_metadata`. This `post_import_instance_with_metadata` - interceptor is recommended for new development instead of `post_import_instance`. + + We recommend only using this `post_import_instance_with_metadata` + interceptor in new development instead of the `post_import_instance` interceptor. + When both interceptors are used, this `post_import_instance_with_metadata` interceptor runs after the + `post_import_instance` interceptor. The (possibly modified) response returned by + `post_import_instance` will be passed to + `post_import_instance_with_metadata`. """ return response, metadata @@ -433,11 +447,13 @@ def post_list_instances_with_metadata(self, response: cloud_redis.ListInstancesR Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_list_instances_with_metadata` interceptor runs after the - `post_list_instances` iterceptor. If the response is modified in - `post_list_instances`, the modified response will be used in - `post_list_instances_with_metadata`. This `post_list_instances_with_metadata` - interceptor is recommended for new development instead of `post_list_instances`. + + We recommend only using this `post_list_instances_with_metadata` + interceptor in new development instead of the `post_list_instances` interceptor. + When both interceptors are used, this `post_list_instances_with_metadata` interceptor runs after the + `post_list_instances` interceptor. The (possibly modified) response returned by + `post_list_instances` will be passed to + `post_list_instances_with_metadata`. """ return response, metadata @@ -467,11 +483,13 @@ def post_reschedule_maintenance_with_metadata(self, response: operations_pb2.Ope Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_reschedule_maintenance_with_metadata` interceptor runs after the - `post_reschedule_maintenance` iterceptor. If the response is modified in - `post_reschedule_maintenance`, the modified response will be used in - `post_reschedule_maintenance_with_metadata`. This `post_reschedule_maintenance_with_metadata` - interceptor is recommended for new development instead of `post_reschedule_maintenance`. + + We recommend only using this `post_reschedule_maintenance_with_metadata` + interceptor in new development instead of the `post_reschedule_maintenance` interceptor. + When both interceptors are used, this `post_reschedule_maintenance_with_metadata` interceptor runs after the + `post_reschedule_maintenance` interceptor. The (possibly modified) response returned by + `post_reschedule_maintenance` will be passed to + `post_reschedule_maintenance_with_metadata`. """ return response, metadata @@ -501,11 +519,13 @@ def post_update_instance_with_metadata(self, response: operations_pb2.Operation, Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_update_instance_with_metadata` interceptor runs after the - `post_update_instance` iterceptor. If the response is modified in - `post_update_instance`, the modified response will be used in - `post_update_instance_with_metadata`. This `post_update_instance_with_metadata` - interceptor is recommended for new development instead of `post_update_instance`. + + We recommend only using this `post_update_instance_with_metadata` + interceptor in new development instead of the `post_update_instance` interceptor. + When both interceptors are used, this `post_update_instance_with_metadata` interceptor runs after the + `post_update_instance` interceptor. The (possibly modified) response returned by + `post_update_instance` will be passed to + `post_update_instance_with_metadata`. """ return response, metadata @@ -535,11 +555,13 @@ def post_upgrade_instance_with_metadata(self, response: operations_pb2.Operation Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_upgrade_instance_with_metadata` interceptor runs after the - `post_upgrade_instance` iterceptor. If the response is modified in - `post_upgrade_instance`, the modified response will be used in - `post_upgrade_instance_with_metadata`. This `post_upgrade_instance_with_metadata` - interceptor is recommended for new development instead of `post_upgrade_instance`. + + We recommend only using this `post_upgrade_instance_with_metadata` + interceptor in new development instead of the `post_upgrade_instance` interceptor. + When both interceptors are used, this `post_upgrade_instance_with_metadata` interceptor runs after the + `post_upgrade_instance` interceptor. The (possibly modified) response returned by + `post_upgrade_instance` will be passed to + `post_upgrade_instance_with_metadata`. """ return response, metadata diff --git a/tests/integration/goldens/redis/google/cloud/redis_v1/services/cloud_redis/transports/rest_asyncio.py b/tests/integration/goldens/redis/google/cloud/redis_v1/services/cloud_redis/transports/rest_asyncio.py index a8e3ee3ff..24f3370c4 100755 --- a/tests/integration/goldens/redis/google/cloud/redis_v1/services/cloud_redis/transports/rest_asyncio.py +++ b/tests/integration/goldens/redis/google/cloud/redis_v1/services/cloud_redis/transports/rest_asyncio.py @@ -208,11 +208,13 @@ async def post_create_instance_with_metadata(self, response: operations_pb2.Oper Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_create_instance_with_metadata` interceptor runs after the - `post_create_instance` iterceptor. If the response is modified in - `post_create_instance`, the modified response will be used in - `post_create_instance_with_metadata`. This `post_create_instance_with_metadata` - interceptor is recommended for new development instead of `post_create_instance`. + + We recommend only using this `post_create_instance_with_metadata` + interceptor in new development instead of the `post_create_instance` interceptor. + When both interceptors are used, this `post_create_instance_with_metadata` interceptor runs after the + `post_create_instance` interceptor. The (possibly modified) response returned by + `post_create_instance` will be passed to + `post_create_instance_with_metadata`. """ return response, metadata @@ -242,11 +244,13 @@ async def post_delete_instance_with_metadata(self, response: operations_pb2.Oper Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_delete_instance_with_metadata` interceptor runs after the - `post_delete_instance` iterceptor. If the response is modified in - `post_delete_instance`, the modified response will be used in - `post_delete_instance_with_metadata`. This `post_delete_instance_with_metadata` - interceptor is recommended for new development instead of `post_delete_instance`. + + We recommend only using this `post_delete_instance_with_metadata` + interceptor in new development instead of the `post_delete_instance` interceptor. + When both interceptors are used, this `post_delete_instance_with_metadata` interceptor runs after the + `post_delete_instance` interceptor. The (possibly modified) response returned by + `post_delete_instance` will be passed to + `post_delete_instance_with_metadata`. """ return response, metadata @@ -276,11 +280,13 @@ async def post_export_instance_with_metadata(self, response: operations_pb2.Oper Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_export_instance_with_metadata` interceptor runs after the - `post_export_instance` iterceptor. If the response is modified in - `post_export_instance`, the modified response will be used in - `post_export_instance_with_metadata`. This `post_export_instance_with_metadata` - interceptor is recommended for new development instead of `post_export_instance`. + + We recommend only using this `post_export_instance_with_metadata` + interceptor in new development instead of the `post_export_instance` interceptor. + When both interceptors are used, this `post_export_instance_with_metadata` interceptor runs after the + `post_export_instance` interceptor. The (possibly modified) response returned by + `post_export_instance` will be passed to + `post_export_instance_with_metadata`. """ return response, metadata @@ -310,11 +316,13 @@ async def post_failover_instance_with_metadata(self, response: operations_pb2.Op Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_failover_instance_with_metadata` interceptor runs after the - `post_failover_instance` iterceptor. If the response is modified in - `post_failover_instance`, the modified response will be used in - `post_failover_instance_with_metadata`. This `post_failover_instance_with_metadata` - interceptor is recommended for new development instead of `post_failover_instance`. + + We recommend only using this `post_failover_instance_with_metadata` + interceptor in new development instead of the `post_failover_instance` interceptor. + When both interceptors are used, this `post_failover_instance_with_metadata` interceptor runs after the + `post_failover_instance` interceptor. The (possibly modified) response returned by + `post_failover_instance` will be passed to + `post_failover_instance_with_metadata`. """ return response, metadata @@ -344,11 +352,13 @@ async def post_get_instance_with_metadata(self, response: cloud_redis.Instance, Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_get_instance_with_metadata` interceptor runs after the - `post_get_instance` iterceptor. If the response is modified in - `post_get_instance`, the modified response will be used in - `post_get_instance_with_metadata`. This `post_get_instance_with_metadata` - interceptor is recommended for new development instead of `post_get_instance`. + + We recommend only using this `post_get_instance_with_metadata` + interceptor in new development instead of the `post_get_instance` interceptor. + When both interceptors are used, this `post_get_instance_with_metadata` interceptor runs after the + `post_get_instance` interceptor. The (possibly modified) response returned by + `post_get_instance` will be passed to + `post_get_instance_with_metadata`. """ return response, metadata @@ -378,11 +388,13 @@ async def post_get_instance_auth_string_with_metadata(self, response: cloud_redi Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_get_instance_auth_string_with_metadata` interceptor runs after the - `post_get_instance_auth_string` iterceptor. If the response is modified in - `post_get_instance_auth_string`, the modified response will be used in - `post_get_instance_auth_string_with_metadata`. This `post_get_instance_auth_string_with_metadata` - interceptor is recommended for new development instead of `post_get_instance_auth_string`. + + We recommend only using this `post_get_instance_auth_string_with_metadata` + interceptor in new development instead of the `post_get_instance_auth_string` interceptor. + When both interceptors are used, this `post_get_instance_auth_string_with_metadata` interceptor runs after the + `post_get_instance_auth_string` interceptor. The (possibly modified) response returned by + `post_get_instance_auth_string` will be passed to + `post_get_instance_auth_string_with_metadata`. """ return response, metadata @@ -412,11 +424,13 @@ async def post_import_instance_with_metadata(self, response: operations_pb2.Oper Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_import_instance_with_metadata` interceptor runs after the - `post_import_instance` iterceptor. If the response is modified in - `post_import_instance`, the modified response will be used in - `post_import_instance_with_metadata`. This `post_import_instance_with_metadata` - interceptor is recommended for new development instead of `post_import_instance`. + + We recommend only using this `post_import_instance_with_metadata` + interceptor in new development instead of the `post_import_instance` interceptor. + When both interceptors are used, this `post_import_instance_with_metadata` interceptor runs after the + `post_import_instance` interceptor. The (possibly modified) response returned by + `post_import_instance` will be passed to + `post_import_instance_with_metadata`. """ return response, metadata @@ -446,11 +460,13 @@ async def post_list_instances_with_metadata(self, response: cloud_redis.ListInst Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_list_instances_with_metadata` interceptor runs after the - `post_list_instances` iterceptor. If the response is modified in - `post_list_instances`, the modified response will be used in - `post_list_instances_with_metadata`. This `post_list_instances_with_metadata` - interceptor is recommended for new development instead of `post_list_instances`. + + We recommend only using this `post_list_instances_with_metadata` + interceptor in new development instead of the `post_list_instances` interceptor. + When both interceptors are used, this `post_list_instances_with_metadata` interceptor runs after the + `post_list_instances` interceptor. The (possibly modified) response returned by + `post_list_instances` will be passed to + `post_list_instances_with_metadata`. """ return response, metadata @@ -480,11 +496,13 @@ async def post_reschedule_maintenance_with_metadata(self, response: operations_p Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_reschedule_maintenance_with_metadata` interceptor runs after the - `post_reschedule_maintenance` iterceptor. If the response is modified in - `post_reschedule_maintenance`, the modified response will be used in - `post_reschedule_maintenance_with_metadata`. This `post_reschedule_maintenance_with_metadata` - interceptor is recommended for new development instead of `post_reschedule_maintenance`. + + We recommend only using this `post_reschedule_maintenance_with_metadata` + interceptor in new development instead of the `post_reschedule_maintenance` interceptor. + When both interceptors are used, this `post_reschedule_maintenance_with_metadata` interceptor runs after the + `post_reschedule_maintenance` interceptor. The (possibly modified) response returned by + `post_reschedule_maintenance` will be passed to + `post_reschedule_maintenance_with_metadata`. """ return response, metadata @@ -514,11 +532,13 @@ async def post_update_instance_with_metadata(self, response: operations_pb2.Oper Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_update_instance_with_metadata` interceptor runs after the - `post_update_instance` iterceptor. If the response is modified in - `post_update_instance`, the modified response will be used in - `post_update_instance_with_metadata`. This `post_update_instance_with_metadata` - interceptor is recommended for new development instead of `post_update_instance`. + + We recommend only using this `post_update_instance_with_metadata` + interceptor in new development instead of the `post_update_instance` interceptor. + When both interceptors are used, this `post_update_instance_with_metadata` interceptor runs after the + `post_update_instance` interceptor. The (possibly modified) response returned by + `post_update_instance` will be passed to + `post_update_instance_with_metadata`. """ return response, metadata @@ -548,11 +568,13 @@ async def post_upgrade_instance_with_metadata(self, response: operations_pb2.Ope Override in a subclass to read or manipulate the response or metadata after it is returned by the CloudRedis server but before it is returned to user code. - This `post_upgrade_instance_with_metadata` interceptor runs after the - `post_upgrade_instance` iterceptor. If the response is modified in - `post_upgrade_instance`, the modified response will be used in - `post_upgrade_instance_with_metadata`. This `post_upgrade_instance_with_metadata` - interceptor is recommended for new development instead of `post_upgrade_instance`. + + We recommend only using this `post_upgrade_instance_with_metadata` + interceptor in new development instead of the `post_upgrade_instance` interceptor. + When both interceptors are used, this `post_upgrade_instance_with_metadata` interceptor runs after the + `post_upgrade_instance` interceptor. The (possibly modified) response returned by + `post_upgrade_instance` will be passed to + `post_upgrade_instance_with_metadata`. """ return response, metadata