The extensions names are Quarkus not Quarkiverse

quarkiverse · Feb 15, 2022 · a972610 · a972610
1 parent f018ef4
commit a972610
Show file tree

Hide file tree

Showing 14 changed files with 17 additions and 14 deletions.
diff --git a/bigquery/README.md b/bigquery/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - BigQuery
+# Quarkus - Google Cloud Services - BigQuery
 
 This extension allows to inject a `com.google.cloud.bigquery.BigQuery` object inside your Quarkus application.
 

diff --git a/bigtable/README.md b/bigtable/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - Bigtable
+# Quarkus - Google Cloud Services - Bigtable
 
 This extension allows using Google Cloud Bigtable inside your Quarkus application.
 

diff --git a/common/README.md b/common/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - Common
+# Quarkus - Google Cloud Services - Common
 
 Common module for Google Cloud Services extensions.
 

diff --git a/docs/modules/ROOT/pages/index.adoc b/docs/modules/ROOT/pages/index.adoc
@@ -21,7 +21,7 @@ that will use the default project detected via Application Default Credentials.
 
 All these extensions work with applications built as native image executables.
 
-These extensions work well within the various Google Cloud Functions extensions available inside Quarkus as they directly authenticate via the built-in credentials.
+These extensions work well within the various Google Cloud Functions extensions available inside Quarkus as they directly authenticate via the built-in credentials, see the https://quarkus.io/guides/deploying-to-google-cloud[deploying to google cloud platform] guide.
 
 [[authenticating]]
 == Authenticating to Google Cloud
@@ -42,7 +42,8 @@ but will be ignored if the `quarkus.google.cloud.accessTokenEnabled` property is
 * Credentials provided by the Google Cloud SDK `gcloud auth application-default login` command.
 * Google Cloud managed environment (Google App Engine, Google Cloud Functions, GCE, ...) built-in credentials.
 
-**Google PubSub and Google Bigtable must be authenticated using the `GOOGLE_APPLICATION_CREDENTIALS` environment variable only.**
+**Google PubSub and Google Bigtable should be authenticated using the `GOOGLE_APPLICATION_CREDENTIALS` environment variable,
+or use the provided `CredentialsProvider` when instantiating their objects.**
 
 [[emulators]]
 == Google Cloud services emulators: mocking Google Cloud credentials

diff --git a/docs/modules/ROOT/pages/secretmanager.adoc b/docs/modules/ROOT/pages/secretmanager.adoc
@@ -2,6 +2,8 @@
 
 This extension allows to use the Google Cloud Platform Secret Manager client library inside your Quarkus application.The current implementation is focused on _accessing_ the secrets, but extending the implementation into also allowing to create or edit a secret might be a natural next step.
 
+It also allows to use secrets from the secret manager directly inside your `application.properties`.
+
 == Bootstrapping the project
 
 First, we need a new project.Create a new project with the following command (replace the version placeholders with the correct ones):

diff --git a/firestore/README.md b/firestore/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - Firestore
+# Quarkus - Google Cloud Services - Firestore
 
 This extension allows to inject a `com.google.cloud.firestore.Firestore` object inside your Quarkus application.
 

diff --git a/integration-tests/README.md b/integration-tests/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - Integration Tests 
+# Quarkus - Google Cloud Services - Integration Tests 
 
 The Google Cloud Services extensions are tested using the following integration tests:
 

diff --git a/integration-tests/app-engine/README.md b/integration-tests/app-engine/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - Integration Tests - Google App Engine
+# Quarkus - Google Cloud Services - Integration Tests - Google App Engine
 
 This integration test show how to integrate Google Cloud Storage with Google App Engine.
 

diff --git a/integration-tests/google-cloud-functions/README.md b/integration-tests/google-cloud-functions/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - Integration Tests - Google Cloud Functions
+# Quarkus - Google Cloud Services - Integration Tests - Google Cloud Functions
 
 This integration test show how to integrate Google Cloud Storage with Google Cloud Functions.
 

diff --git a/integration-tests/main/README.md b/integration-tests/main/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - Integration Tests - Main
+# Quarkus - Google Cloud Services - Integration Tests - Main
 
 This is the main integration test, it allows to test all Google Cloud services from REST endpoints using a service account authentication.
 

diff --git a/pubsub/README.md b/pubsub/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - PubSub
+# Quarkus - Google Cloud Services - PubSub
 
 This extension allows using Google Cloud PubSub inside your Quarkus application.
 

diff --git a/secret-manager/README.md b/secret-manager/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - Secret Manager
+# Quarkus - Google Cloud Services - Secret Manager
 
 This extension allows to use the Google Cloud Platform Secret Manager client library inside your Quarkus application. The current implementation is focused on _accessing_ the secrets, but extending the implementation into also allowing to create or edit a secret might be a natural next step.
 

diff --git a/spanner/README.md b/spanner/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - Spanner
+# Quarkus - Google Cloud Services - Spanner
 
 This extension allows to inject a `com.google.cloud.spanner.Spanner` object inside your Quarkus application.
 

diff --git a/storage/README.md b/storage/README.md
@@ -1,4 +1,4 @@
-# Quarkiverse - Google Cloud Services - Storage
+# Quarkus - Google Cloud Services - Storage
 
 This extension allows to inject a `com.google.cloud.storage.Storage` object inside your Quarkus application.