fix(Global Search/Tagging): regenerated services with latest API definition (#116)

damianovesperini · web-flow · commit 2ac673660dce · 2021-06-14T11:14:14.000-05:00
diff --git a/ibm_platform_services/global_search_v2.py b/ibm_platform_services/global_search_v2.py
@@ -14,18 +14,17 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-# IBM OpenAPI SDK Code Generator Version: 99-SNAPSHOT-b414353e-20210324-135924
+# IBM OpenAPI SDK Code Generator Version: 3.33.0-caf29bd0-20210603-225214
  
 """
 Search for resources with the global and shared resource properties repository integrated
-in the IBM Cloud Platform. The search repository stores and searches cloud resources
+in the IBM Cloud platform. The search repository stores and searches cloud resources
 attributes, which categorize or classify resources. A resource is a physical or logical
-component that can be provisioned or reserved for an application or service instance and
-is owned by resource providers, such as Cloud Foundry, IBM containers, or Resource
-Controller, in the IBM Cloud platform. Resources are uniquely identified by a CRN (Cloud
-Resource Naming identifier) or by an IMS ID. The properties of a resource include tags and
-system properties. Both properties are defined in an IBM Cloud billing account, and span
-across many regions.
+component that can be created or reserved for an application or service instance and is
+owned by resource providers, such as Cloud Foundry, IBM Kubernetes Service, or resource
+controller in IBM Cloud. Resources are uniquely identified by a Cloud Resource Name (CRN)
+or by an IMS ID. The properties of a resource include tags and system properties. Both
+properties are defined in an IBM Cloud billing account, and span across many regions.
 """
 
 from typing import Dict, List
@@ -98,21 +97,22 @@ def search(self,
         """
         Find instances of resources (v3).
 
-        Find cloud foundry resources, resource controller-enabled resources, or storage
-        and network resources running on classic infrastructure in a specific account ID.
-        You can apply query strings if necessary. To filter results, you can insert a
-        string using the Lucene syntax and the query string is parsed into a series of
-        terms and operators. A term can be a single word or a phrase, in which case the
-        search is performed for all the words, in the same order. To filter for a specific
-        value regardless of the property that contains it, use an asterisk as the key
-        name. Only resources that belong to the account ID and that are accessible by the
-        client are returned. You must use this operation when you need to fetch more than
-        `10000` resource items. The `/v2/resources/search` prohibits paginating through
-        such a big number. On the first call, the operation returns a live cursor on the
-        data that you must use on all the subsequent calls to get the next batch of
-        results until you get the empty result set. By default, the fields returned for
-        every resources are: "crn", "name", "family", "type", "account_id". You can
-        specify the subset of the fields you want in your request.
+        Find Cloud Foundry resources, IAM-enabled resources, or  storage and network
+        resources running on classic infrastructure in a  specific account ID. You can
+        apply query strings if necessary.
+        To filter results, you can insert a string using the Lucene syntax and the  query
+        string is parsed into a series of terms and operators. A term can be  a single
+        word or a phrase, in which case the search is performed for all  the words, in the
+        same order. To filter for a specific value regardless of  the property that
+        contains it, type the search term without specifying a  field. Only resources that
+        belong to the account ID and that are accessible  by the client are returned.
+        You must use `/v3/resources/search` when you need to fetch more than `10000`
+        resource items. The `/v2/resources/search` prohibits paginating through such  a
+        big number. On the first call, the operation returns a live cursor on the  data
+        that you must use on all the subsequent calls to get the next batch of  results
+        until you get the empty result set. By default, the fields returned  for every
+        resource are "crn", "name", "family", "type", and "account_id". You  can specify
+        the subset of the fields you want in your request.
 
         :param str query: (optional) The Lucene-formatted query string. Default to
                '*' if not set.
diff --git a/ibm_platform_services/global_tagging_v1.py b/ibm_platform_services/global_tagging_v1.py
@@ -14,7 +14,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-# IBM OpenAPI SDK Code Generator Version: 99-SNAPSHOT-a8493a65-20210115-083246
+# IBM OpenAPI SDK Code Generator Version: 3.33.0-caf29bd0-20210603-225214
  
 """
 Manage your tags with the Tagging API in IBM Cloud. You can attach, detach, delete a tag
@@ -115,15 +115,16 @@ def list_tags(self,
                provider, `ghost`, `ims` or `ghost,ims`, where the tag exists and the
                number of attached resources.
         :param List[str] providers: (optional) Select a provider. Supported values
-               are `ghost` and `ims`. To list GhoST tags and infrastructure tags use
-               `ghost,ims`. `service` and `access` tags can only be attached to GhoST
-               onboarded resources, so you should not set this parameter when listing
-               them.
+               are `ghost` and `ims`. To list both Global Search and Tagging tags and
+               infrastructure tags, use `ghost,ims`. `service` and `access` tags can only
+               be attached to resources that are onboarded to Global Search and Tagging,
+               so you should not set this parameter when listing them.
         :param str attached_to: (optional) If you want to return only the list of
                tags attached to a specified resource, pass the ID of the resource on this
-               parameter. For GhoST onboarded resources, the resource ID is the CRN; for
-               IMS resources, it is the IMS ID. When using this parameter, you must
-               specify the appropriate provider (`ims` or `ghost`).
+               parameter. For resources that are onboarded to Global Search and Tagging,
+               the resource ID is the CRN; for IMS resources, it is the IMS ID. When using
+               this parameter, you must specify the appropriate provider (`ims` or
+               `ghost`).
         :param int offset: (optional) The offset is the index of the item from
                which you want to start returning data from.
         :param int limit: (optional) The number of tags to return.
@@ -311,7 +312,8 @@ def delete_tag(self,
 
         :param str tag_name: The name of tag to be deleted.
         :param List[str] providers: (optional) Select a provider. Supported values
-               are `ghost` and `ims`. To delete tag both in GhoST in IMS, use `ghost,ims`.
+               are `ghost` and `ims`. To delete tags both in Global Search and Tagging and
+               in IMS, use `ghost,ims`.
         :param str impersonate_user: (optional) The user on whose behalf the delete
                operation must be performed (_for administrators only_).
         :param str account_id: (optional) The ID of the billing account to delete
@@ -370,14 +372,7 @@ def attach_tag(self,
         """
         Attach tags.
 
-        Attaches one or more tags to one or more resources. To attach a `user` tag on a
-        resource, you must have the access listed in the [Granting users access to tag
-        resources](https://cloud.ibm.com/docs/account?topic=account-access) documentation.
-        To attach a `service` tag, you must be an authorized service. If that is the case,
-        then you can attach a `service` tag with your registered `prefix` to any resource
-        in any account. The account ID must be set through the `account_id` query
-        parameter. To attach an `access` tag, you must be the resource administrator
-        within the account. You can attach only `access` tags already existing.
+        Attaches one or more tags to one or more resources.
 
         :param List[Resource] resources: List of resources on which the tag or tags
                should be attached.
@@ -449,14 +444,7 @@ def detach_tag(self,
         """
         Detach tags.
 
-        Detaches one or more tags from one or more resources. To detach a `user` tag on a
-        resource you must have the permissions listed in the [Granting users access to tag
-        resources](https://cloud.ibm.com/docs/account?topic=account-access) documentation.
-        To detach a `service` tag you must be an authorized Service. If that is the case,
-        then you can detach a `service` tag with your registered `prefix` from any
-        resource in any account. The account ID must be set through the `account_id` query
-        parameter. To detach an `access` tag, you must be the resource administrator
-        within the account.
+        Detaches one or more tags from one or more resources.
 
         :param List[Resource] resources: List of resources on which the tag or tags
                should be detached.
@@ -530,10 +518,10 @@ class TagType(str, Enum):
         ACCESS = 'access'
     class Providers(str, Enum):
         """
-        Select a provider. Supported values are `ghost` and `ims`. To list GhoST tags and
-        infrastructure tags use `ghost,ims`. `service` and `access` tags can only be
-        attached to GhoST onboarded resources, so you should not set this parameter when
-        listing them.
+        Select a provider. Supported values are `ghost` and `ims`. To list both Global
+        Search and Tagging tags and infrastructure tags, use `ghost,ims`. `service` and
+        `access` tags can only be attached to resources that are onboarded to Global
+        Search and Tagging, so you should not set this parameter when listing them.
         """
         GHOST = 'ghost'
         IMS = 'ims'
@@ -586,8 +574,8 @@ class DeleteTagEnums:
 
     class Providers(str, Enum):
         """
-        Select a provider. Supported values are `ghost` and `ims`. To delete tag both in
-        GhoST in IMS, use `ghost,ims`.
+        Select a provider. Supported values are `ghost` and `ims`. To delete tags both in
+        Global Search and Tagging and in IMS, use `ghost,ims`.
         """
         GHOST = 'ghost'
         IMS = 'ims'
diff --git a/test/unit/test_global_search_v2.py b/test/unit/test_global_search_v2.py
@@ -1,5 +1,5 @@
 # -*- coding: utf-8 -*-
-# (C) Copyright IBM Corp. 2020.
+# (C) Copyright IBM Corp. 2021.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
@@ -28,12 +28,12 @@
 from ibm_platform_services.global_search_v2 import *
 
 
-service = GlobalSearchV2(
+_service = GlobalSearchV2(
     authenticator=NoAuthAuthenticator()
     )
 
-base_url = 'https://api.global-search-tagging.cloud.ibm.com'
-service.set_service_url(base_url)
+_base_url = 'https://api.global-search-tagging.cloud.ibm.com'
+_service.set_service_url(_base_url)
 
 ##############################################################################
 # Start of Service: Search
@@ -60,7 +60,7 @@ def test_search_all_params(self):
         search()
         """
         # Set up mock
-        url = self.preprocess_url(base_url + '/v3/resources/search')
+        url = self.preprocess_url(_base_url + '/v3/resources/search')
         mock_response = '{"search_cursor": "search_cursor", "limit": 5, "items": [{"crn": "crn"}]}'
         responses.add(responses.POST,
                       url,
@@ -79,7 +79,7 @@ def test_search_all_params(self):
         sort = ['testString']
 
         # Invoke method
-        response = service.search(
+        response = _service.search(
             query=query,
             fields=fields,
             search_cursor=search_cursor,
@@ -114,7 +114,7 @@ def test_search_required_params(self):
         test_search_required_params()
         """
         # Set up mock
-        url = self.preprocess_url(base_url + '/v3/resources/search')
+        url = self.preprocess_url(_base_url + '/v3/resources/search')
         mock_response = '{"search_cursor": "search_cursor", "limit": 5, "items": [{"crn": "crn"}]}'
         responses.add(responses.POST,
                       url,
@@ -128,7 +128,7 @@ def test_search_required_params(self):
         search_cursor = 'testString'
 
         # Invoke method
-        response = service.search(
+        response = _service.search(
             query=query,
             fields=fields,
             search_cursor=search_cursor,
@@ -175,7 +175,7 @@ def test_get_supported_types_all_params(self):
         get_supported_types()
         """
         # Set up mock
-        url = self.preprocess_url(base_url + '/v2/resources/supported_types')
+        url = self.preprocess_url(_base_url + '/v2/resources/supported_types')
         mock_response = '{"supported_types": ["supported_types"]}'
         responses.add(responses.GET,
                       url,
@@ -184,7 +184,7 @@ def test_get_supported_types_all_params(self):
                       status=200)
 
         # Invoke method
-        response = service.get_supported_types()
+        response = _service.get_supported_types()
 
 
         # Check for correct operation
@@ -202,7 +202,7 @@ def test_get_supported_types_all_params(self):
 # Start of Model Tests
 ##############################################################################
 # region
-class TestResultItem():
+class ResultItemUnitTests():
     """
     Test Class for ResultItem
     """
@@ -232,7 +232,7 @@ def test_result_item_serialization(self):
         result_item_model_json2 = result_item_model.to_dict()
         assert result_item_model_json2 == result_item_model_json
 
-class TestScanResult():
+class ScanResultUnitTests():
     """
     Test Class for ScanResult
     """
@@ -269,7 +269,7 @@ def test_scan_result_serialization(self):
         scan_result_model_json2 = scan_result_model.to_dict()
         assert scan_result_model_json2 == scan_result_model_json
 
-class TestSupportedTypesList():
+class SupportedTypesListUnitTests():
     """
     Test Class for SupportedTypesList
     """
diff --git a/test/unit/test_global_tagging_v1.py b/test/unit/test_global_tagging_v1.py
