Merge branch 'GONRG-5890-Change-to-GC' into 'master'

GONRG-5890-Change-to-GC

See merge request !406

README.md

@@ -2,9 +2,9 @@
 
 The Schema Service is a Maven multi-module project with each cloud implemention placed in its submodule. To build or run Schema Service locally, follow the below steps :
 
-### 1. GCP deployment
+### 1. Google Cloud deployment
 
-Instructions for running the GCP implementation in the cloud can be found [here](./provider/schema-gcp/README.md).
+Instructions for running the Google Cloud implementation in the cloud can be found [here](./provider/schema-gcp/README.md).
 
 ### 2. Azure deployment 
 
@@ -14,13 +14,13 @@ Instructions for running the Azure implementation in the cloud can be found [her
 
 DevSanity tests are located in a schema-core project in testing directory under the project root directory.
 
-1. GCP
+1. Google Cloud
 These tests validate functionality of schema service. 
 
 They can then be run/debugged directly in your IDE of choice using the GUI or via the commandline using below command from schema-core project.
 Below command has to be run post building complete project.
 
-Instructions for running the GCP integration tests can be found [here](./provider/schema-gcp/README.md).
+Instructions for running the Google Cloud integration tests can be found [here](./provider/schema-gcp/README.md).
 
 Below command can be run through azure-pipeline.yml after setting environment variables in the pipeline.
 

provider/schema-gcp/README.md

@@ -17,8 +17,8 @@ Pre-requisites
 ### Service Configuration
 #### Anthos:
 [Anthos service configuration ](docs/anthos/README.md)
-#### GCP:
-[Gcp service configuration ](docs/gcp/README.md)
+#### Google Cloud:
+[Google Cloud service configuration ](docs/gcp/README.md)
 
 ### Run Locally
 Check that maven is installed:
@@ -78,13 +78,13 @@ Once the above Prerequisite are done, we can follow the below steps to run the s
     ```bash
     mvn clean install
     ```
-    This will build the core project as well as all the underlying projects. If we want  to build projects for specific cloud vendor, we can use mvn --projects command. For example, if we want to build only for GCP(Google Cloud Platform), we can use below command :
+    This will build the core project as well as all the underlying projects. If we want  to build projects for specific cloud vendor, we can use mvn --projects command. For example, if we want to build only for Google Cloud, we can use below command :
     ```bash
     mvn --projects schema-core,provider/schema-gcp clean install
     ```
-2. Run schema service in command line. We need to select which cloud vendor specific schema-service we want to run. For example, if we want to run schema-service for GCP, run the below command : 
+2. Run schema service in command line. We need to select which cloud vendor specific schema-service we want to run. For example, if we want to run schema-service for Google Cloud, run the below command : 
     ```bash 
-    # Running GCP : 
+    # Running Google Cloud : 
     java -jar  provider\schema-gcp\target\os-schema-gcp-0.0.1-spring-boot.jar
 3. The port and path for the service endpoint can be configured in ```application.properties``` in the provider folder as following. If not specified, then  the web container (ex. Tomcat) default is used: 
     ```bash
@@ -96,8 +96,8 @@ You can access the service APIs by following the service contract in [schema.yam
 ## Testing
 #### Anthos:
 [Anthos Testing](docs/anthos/README.md)
-#### GCP:
-[Gcp Testing](docs/gcp/README.md)
+#### Google Cloud:
+[Google Cloud Testing](docs/gcp/README.md)
 
 ## Deployment
 

provider/schema-gcp/docs/anthos/README.md

@@ -8,7 +8,7 @@ Must have:
 
 | name | value | description | sensitive? | source |
 | ---  | ---   | ---         | ---        | ---    |
-| `SPRING_PROFILES_ACTIVE` | ex `anthos` | Spring profile that activate default configuration for GCP environment | false | - |
+| `SPRING_PROFILES_ACTIVE` | ex `anthos` | Spring profile that activate default configuration for Google Cloud environment | false | - |
 | `SHARED_TENANT_NAME` | ex `anthos` | Shared account id | no | - |
 | `<POSTGRES_PASSWORD_ENV_VARIABLE_NAME>` | ex `password` | Potgres user, name of that variable not defined at the service level, the name will be received through partition service. Each tenant can have it's own ENV name value, and it must be present in ENV of Indexer service, see [Partition properties set](#Properties-set-in-Partition-service)  | yes | - |
 | `<MINIO_SECRETKEY_ENV_VARIABLE_NAME>` | ex `password` | Minio password, name of that variable not defined at the service level, the name will be received through partition service. Each tenant can have it's own ENV name value, and it must be present in ENV of Indexer service, see [Partition properties set](#Properties-set-in-Partition-service) | yes | - |

provider/schema-gcp/docs/gcp/README.md

-## Service Configuration for GCP
+## Service Configuration for Google Cloud
 
 ## Environment variables:
 
@@ -9,7 +9,7 @@ Must have:
 | name | value | description | sensitive? | source |
 | ---  | ---   | ---         | ---        | ---    |
 | `GOOGLE_AUDIENCES` | ex `*****.apps.googleusercontent.com` | Client ID for getting access to cloud resources | yes | https://console.cloud.google.com/apis/credentials |
-| `SPRING_PROFILES_ACTIVE` | ex `gcp` | Spring profile that activate default configuration for GCP environment | false | - |
+| `SPRING_PROFILES_ACTIVE` | ex `gcp` | Spring profile that activate default configuration for Google Cloud environment | false | - |
 | `SHARED_TENANT_NAME` | ex `osdu` | Shared account id | no | - |
 
 Defined in default application property file but possible to override: