From 35b2ea1e847b1552ebd27e5c2919592e66d0f7f8 Mon Sep 17 00:00:00 2001 From: Jeff Ching Date: Mon, 3 Feb 2020 14:34:20 -0800 Subject: [PATCH] chore: update repo-metadata and regenerate README from templates --- .repo-metadata.json | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/.repo-metadata.json b/.repo-metadata.json index 5812ec9a..cc0e533a 100644 --- a/.repo-metadata.json +++ b/.repo-metadata.json @@ -2,12 +2,15 @@ "name": "containeranalysis", "name_pretty": "Cloud Container Analysis", "product_documentation": "https://cloud.google.com/container-registry/docs/container-analysis", - "client_documentation": "https://googleapis.dev/java/google-cloud-clients/latest/index.html?com/google/cloud/devtools/containeranalysis/v1/package-summary.html", + "client_documentation": "https://googleapis.dev/java/google-cloud-containeranalysis/latest/", "issue_tracker": "https://issuetracker.google.com/savedsearches/559777", "release_level": "beta", "language": "java", "repo": "googleapis/java-containeranalysis", "repo_short": "java-containeranalysis", "distribution_name": "com.google.cloud:google-cloud-containeranalysis", - "api_id": "containeranalysis.googleapis.com" + "api_id": "containeranalysis.googleapis.com", + "api_description": "is a service that provides vulnerability scanning and metadata storage for software artifacts. The service performs vulnerability scans on built software artifacts, such as the images in Container Registry, then stores the resulting metadata and makes it available for consumption through an API. The metadata may come from several sources, including vulnerability scanning, other Cloud services, and third-party providers.", + "transport": "grpc", + "requires_billing": true } \ No newline at end of file