Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion generation_config.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2209,7 +2209,7 @@ libraries:
GAPICs:
- proto_path: google/cloud/run/v2
- api_shortname: saasservicemgmt
name_pretty: SaaS Runtime API
name_pretty: App Lifecycle Manager
product_documentation: https://cloud.google.com/saas-runtime/docs/overview
api_description: "Model, deploy, and operate your SaaS at scale.\t"
client_documentation:
Expand Down
2 changes: 1 addition & 1 deletion java-saasservicemgmt/.repo-metadata.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"api_shortname": "saasservicemgmt",
"name_pretty": "SaaS Runtime API",
"name_pretty": "App Lifecycle Manager",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is generated from name_pretty in generation_config.yaml. Updating the config should trigger regeneration of this file and the README.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh I see. repo-metadata is probably generated then

"product_documentation": "https://cloud.google.com/saas-runtime/docs/overview",
"api_description": "Model, deploy, and operate your SaaS at scale.\t",
"client_documentation": "https://cloud.google.com/java/docs/reference/google-cloud-saasservicemgmt/latest/overview",
Expand Down
20 changes: 10 additions & 10 deletions java-saasservicemgmt/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Google SaaS Runtime API Client for Java
# Google App Lifecycle Manager Client for Java

Java idiomatic client for [SaaS Runtime API][product-docs].
Java idiomatic client for [App Lifecycle Manager][product-docs].
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The main header on line 1 (# Google SaaS Runtime API Client for Java) should also be updated to reference "App Lifecycle Manager" to maintain consistency throughout the document.


[![Maven][maven-version-image]][maven-version-link]
![Stability][stability-image]
Expand Down Expand Up @@ -67,14 +67,14 @@ See the [Authentication][authentication] section in the base directory's README.

## Authorization

The client application making API calls must be granted [authorization scopes][auth-scopes] required for the desired SaaS Runtime API APIs, and the authenticated principal must have the [IAM role(s)][predefined-iam-roles] required to access GCP resources using the SaaS Runtime API API calls.
The client application making API calls must be granted [authorization scopes][auth-scopes] required for the desired App Lifecycle Manager APIs, and the authenticated principal must have the [IAM role(s)][predefined-iam-roles] required to access GCP resources using the App Lifecycle Manager API calls.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Consider using the singular "API" instead of "APIs" for consistency with the usage on line 76 and to better reflect the service name.

Suggested change
The client application making API calls must be granted [authorization scopes][auth-scopes] required for the desired App Lifecycle Manager APIs, and the authenticated principal must have the [IAM role(s)][predefined-iam-roles] required to access GCP resources using the App Lifecycle Manager API calls.
The client application making API calls must be granted [authorization scopes][auth-scopes] required for the desired App Lifecycle Manager API, and the authenticated principal must have the [IAM role(s)][predefined-iam-roles] required to access GCP resources using the App Lifecycle Manager API calls.


## Getting Started

### Prerequisites

You will need a [Google Cloud Platform Console][developer-console] project with the SaaS Runtime API [API enabled][enable-api].
You will need to [enable billing][enable-billing] to use Google SaaS Runtime API.
You will need a [Google Cloud Platform Console][developer-console] project with the App Lifecycle Manager [API enabled][enable-api].
You will need to [enable billing][enable-billing] to use Google App Lifecycle Manager.
[Follow these instructions][create-project] to get your project set up. You will also need to set up the local development environment by
[installing the Google Cloud Command Line Interface][cloud-cli] and running the following commands in command line:
`gcloud auth login` and `gcloud config set project [YOUR PROJECT ID]`.
Expand All @@ -84,13 +84,13 @@ You will need to [enable billing][enable-billing] to use Google SaaS Runtime API
You'll need to obtain the `google-cloud-saasservicemgmt` library. See the [Quickstart](#quickstart) section
to add `google-cloud-saasservicemgmt` as a dependency in your code.

## About SaaS Runtime API
## About App Lifecycle Manager


[SaaS Runtime API][product-docs] Model, deploy, and operate your SaaS at scale.
[App Lifecycle Manager][product-docs] Model, deploy, and operate your SaaS at scale.

See the [SaaS Runtime API client library docs][javadocs] to learn how to
use this SaaS Runtime API Client Library.
See the [App Lifecycle Manager client library docs][javadocs] to learn how to
use this App Lifecycle Manager Client Library.



Expand All @@ -103,7 +103,7 @@ To get help, follow the instructions in the [shared Troubleshooting document][tr

## Transport

SaaS Runtime API uses both gRPC and HTTP/JSON for the transport layer.
App Lifecycle Manager uses both gRPC and HTTP/JSON for the transport layer.

## Supported Java Versions

Expand Down
Loading