Autogenerated update (2020-01-04)

Update:
- people_v1
- remotebuildexecution_v1alpha
- serviceconsumermanagement_v1
- servicenetworking_v1
- servicenetworking_v1beta
- serviceusage_v1
- serviceusage_v1beta1
This commit is contained in:
Google APIs 2020-01-04 00:37:35 +00:00
parent 6ab7553f4d
commit 98ee35a859
12 changed files with 220 additions and 7 deletions

View File

@ -25,7 +25,7 @@ module Google
# @see https://developers.google.com/people/
module PeopleV1
VERSION = 'V1'
REVISION = '20191030'
REVISION = '20191230'
# See, edit, download, and permanently delete your contacts
AUTH_CONTACTS = 'https://www.googleapis.com/auth/contacts'
@ -42,6 +42,9 @@ module Google
# View your email addresses
AUTH_USER_EMAILS_READ = 'https://www.googleapis.com/auth/user.emails.read'
# See your education, work history and org info
AUTH_USER_ORGANIZATION_READ = 'https://www.googleapis.com/auth/user.organization.read'
# View your phone numbers
AUTH_USER_PHONENUMBERS_READ = 'https://www.googleapis.com/auth/user.phonenumbers.read'

View File

@ -25,7 +25,7 @@ module Google
# @see https://cloud.google.com/remote-build-execution/docs/
module RemotebuildexecutionV1alpha
VERSION = 'V1alpha'
REVISION = '20191211'
REVISION = '20200102'
# View and manage your data across Google Cloud Platform services
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

View File

@ -25,7 +25,7 @@ module Google
# @see https://cloud.google.com/service-consumer-management/docs/overview
module ServiceconsumermanagementV1
VERSION = 'V1'
REVISION = '20191210'
REVISION = '20191230'
# View and manage your data across Google Cloud Platform services
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

View File

@ -1927,6 +1927,48 @@ module Google
# @return [String]
attr_accessor :type
# The units in which the metric value is reported. It is only applicable
# if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
# defines the representation of the stored metric values.
# Different systems may scale the values to be more easily displayed (so a
# value of `0.02KBy` _might_ be displayed as `20By`, and a value of
# `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
# `KBy`, then the value of the metric is always in thousands of bytes, no
# matter how it may be displayed..
# If you want a custom metric to record the exact number of CPU-seconds used
# by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
# `s`CPU`` (or equivalently `1s`CPU`` or just `s`). If the job uses 12,005
# CPU-seconds, then the value is written as `12005`.
# Alternatively, if you want a custom metric to record data in a more
# granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
# `ks`CPU``, and then write the value `12.005` (which is `12005/1000`),
# or use `Kis`CPU`` and write `11.723` (which is `12005/1024`).
# The supported units are a subset of [The Unified Code for Units of
# Measure](http://unitsofmeasure.org/ucum.html) standard:
# **Basic units (UNIT)**
# * `bit` bit
# * `By` byte
# * `s` second
# * `min` minute
# * `h` hour
# * `d` day
# **Prefixes (PREFIX)**
# * `k` kilo (10^3)
# * `M` mega (10^6)
# * `G` giga (10^9)
# * `T` tera (10^12)
# * `P` peta (10^15)
# * `E` exa (10^18)
# * `Z` zetta (10^21)
# * `Y` yotta (10^24)
# * `m` milli (10^-3)
# * `u` micro (10^-6)
# * `n` nano (10^-9)
# * `p` pico (10^-12)
# * `f` femto (10^-15)
# * `a` atto (10^-18)
# * `z` zepto (10^-21)
# * `y` yocto (10^-24)
# * `Ki` kibi (2^10)
# * `Mi` mebi (2^20)
# * `Gi` gibi (2^30)

View File

@ -26,7 +26,7 @@ module Google
# @see https://cloud.google.com/service-infrastructure/docs/service-networking/getting-started
module ServicenetworkingV1
VERSION = 'V1'
REVISION = '20191206'
REVISION = '20191230'
# View and manage your data across Google Cloud Platform services
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

View File

@ -2008,6 +2008,48 @@ module Google
# @return [String]
attr_accessor :type
# The units in which the metric value is reported. It is only applicable
# if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
# defines the representation of the stored metric values.
# Different systems may scale the values to be more easily displayed (so a
# value of `0.02KBy` _might_ be displayed as `20By`, and a value of
# `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
# `KBy`, then the value of the metric is always in thousands of bytes, no
# matter how it may be displayed..
# If you want a custom metric to record the exact number of CPU-seconds used
# by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
# `s`CPU`` (or equivalently `1s`CPU`` or just `s`). If the job uses 12,005
# CPU-seconds, then the value is written as `12005`.
# Alternatively, if you want a custom metric to record data in a more
# granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
# `ks`CPU``, and then write the value `12.005` (which is `12005/1000`),
# or use `Kis`CPU`` and write `11.723` (which is `12005/1024`).
# The supported units are a subset of [The Unified Code for Units of
# Measure](http://unitsofmeasure.org/ucum.html) standard:
# **Basic units (UNIT)**
# * `bit` bit
# * `By` byte
# * `s` second
# * `min` minute
# * `h` hour
# * `d` day
# **Prefixes (PREFIX)**
# * `k` kilo (10^3)
# * `M` mega (10^6)
# * `G` giga (10^9)
# * `T` tera (10^12)
# * `P` peta (10^15)
# * `E` exa (10^18)
# * `Z` zetta (10^21)
# * `Y` yotta (10^24)
# * `m` milli (10^-3)
# * `u` micro (10^-6)
# * `n` nano (10^-9)
# * `p` pico (10^-12)
# * `f` femto (10^-15)
# * `a` atto (10^-18)
# * `z` zepto (10^-21)
# * `y` yocto (10^-24)
# * `Ki` kibi (2^10)
# * `Mi` mebi (2^20)
# * `Gi` gibi (2^30)

View File

@ -26,7 +26,7 @@ module Google
# @see https://cloud.google.com/service-infrastructure/docs/service-networking/getting-started
module ServicenetworkingV1beta
VERSION = 'V1beta'
REVISION = '20191206'
REVISION = '20191230'
# View and manage your data across Google Cloud Platform services
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

View File

@ -1882,6 +1882,48 @@ module Google
# @return [String]
attr_accessor :type
# The units in which the metric value is reported. It is only applicable
# if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
# defines the representation of the stored metric values.
# Different systems may scale the values to be more easily displayed (so a
# value of `0.02KBy` _might_ be displayed as `20By`, and a value of
# `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
# `KBy`, then the value of the metric is always in thousands of bytes, no
# matter how it may be displayed..
# If you want a custom metric to record the exact number of CPU-seconds used
# by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
# `s`CPU`` (or equivalently `1s`CPU`` or just `s`). If the job uses 12,005
# CPU-seconds, then the value is written as `12005`.
# Alternatively, if you want a custom metric to record data in a more
# granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
# `ks`CPU``, and then write the value `12.005` (which is `12005/1000`),
# or use `Kis`CPU`` and write `11.723` (which is `12005/1024`).
# The supported units are a subset of [The Unified Code for Units of
# Measure](http://unitsofmeasure.org/ucum.html) standard:
# **Basic units (UNIT)**
# * `bit` bit
# * `By` byte
# * `s` second
# * `min` minute
# * `h` hour
# * `d` day
# **Prefixes (PREFIX)**
# * `k` kilo (10^3)
# * `M` mega (10^6)
# * `G` giga (10^9)
# * `T` tera (10^12)
# * `P` peta (10^15)
# * `E` exa (10^18)
# * `Z` zetta (10^21)
# * `Y` yotta (10^24)
# * `m` milli (10^-3)
# * `u` micro (10^-6)
# * `n` nano (10^-9)
# * `p` pico (10^-12)
# * `f` femto (10^-15)
# * `a` atto (10^-18)
# * `z` zepto (10^-21)
# * `y` yocto (10^-24)
# * `Ki` kibi (2^10)
# * `Mi` mebi (2^20)
# * `Gi` gibi (2^30)

View File

@ -27,7 +27,7 @@ module Google
# @see https://cloud.google.com/service-usage/
module ServiceusageV1
VERSION = 'V1'
REVISION = '20191206'
REVISION = '20191230'
# View and manage your data across Google Cloud Platform services
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

View File

@ -2716,6 +2716,48 @@ module Google
# @return [String]
attr_accessor :type
# The units in which the metric value is reported. It is only applicable
# if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
# defines the representation of the stored metric values.
# Different systems may scale the values to be more easily displayed (so a
# value of `0.02KBy` _might_ be displayed as `20By`, and a value of
# `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
# `KBy`, then the value of the metric is always in thousands of bytes, no
# matter how it may be displayed..
# If you want a custom metric to record the exact number of CPU-seconds used
# by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
# `s`CPU`` (or equivalently `1s`CPU`` or just `s`). If the job uses 12,005
# CPU-seconds, then the value is written as `12005`.
# Alternatively, if you want a custom metric to record data in a more
# granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
# `ks`CPU``, and then write the value `12.005` (which is `12005/1000`),
# or use `Kis`CPU`` and write `11.723` (which is `12005/1024`).
# The supported units are a subset of [The Unified Code for Units of
# Measure](http://unitsofmeasure.org/ucum.html) standard:
# **Basic units (UNIT)**
# * `bit` bit
# * `By` byte
# * `s` second
# * `min` minute
# * `h` hour
# * `d` day
# **Prefixes (PREFIX)**
# * `k` kilo (10^3)
# * `M` mega (10^6)
# * `G` giga (10^9)
# * `T` tera (10^12)
# * `P` peta (10^15)
# * `E` exa (10^18)
# * `Z` zetta (10^21)
# * `Y` yotta (10^24)
# * `m` milli (10^-3)
# * `u` micro (10^-6)
# * `n` nano (10^-9)
# * `p` pico (10^-12)
# * `f` femto (10^-15)
# * `a` atto (10^-18)
# * `z` zepto (10^-21)
# * `y` yocto (10^-24)
# * `Ki` kibi (2^10)
# * `Mi` mebi (2^20)
# * `Gi` gibi (2^30)

View File

@ -27,7 +27,7 @@ module Google
# @see https://cloud.google.com/service-usage/
module ServiceusageV1beta1
VERSION = 'V1beta1'
REVISION = '20191206'
REVISION = '20191230'
# View and manage your data across Google Cloud Platform services
AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

View File

@ -2694,6 +2694,48 @@ module Google
# @return [String]
attr_accessor :type
# The units in which the metric value is reported. It is only applicable
# if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
# defines the representation of the stored metric values.
# Different systems may scale the values to be more easily displayed (so a
# value of `0.02KBy` _might_ be displayed as `20By`, and a value of
# `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
# `KBy`, then the value of the metric is always in thousands of bytes, no
# matter how it may be displayed..
# If you want a custom metric to record the exact number of CPU-seconds used
# by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
# `s`CPU`` (or equivalently `1s`CPU`` or just `s`). If the job uses 12,005
# CPU-seconds, then the value is written as `12005`.
# Alternatively, if you want a custom metric to record data in a more
# granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
# `ks`CPU``, and then write the value `12.005` (which is `12005/1000`),
# or use `Kis`CPU`` and write `11.723` (which is `12005/1024`).
# The supported units are a subset of [The Unified Code for Units of
# Measure](http://unitsofmeasure.org/ucum.html) standard:
# **Basic units (UNIT)**
# * `bit` bit
# * `By` byte
# * `s` second
# * `min` minute
# * `h` hour
# * `d` day
# **Prefixes (PREFIX)**
# * `k` kilo (10^3)
# * `M` mega (10^6)
# * `G` giga (10^9)
# * `T` tera (10^12)
# * `P` peta (10^15)
# * `E` exa (10^18)
# * `Z` zetta (10^21)
# * `Y` yotta (10^24)
# * `m` milli (10^-3)
# * `u` micro (10^-6)
# * `n` nano (10^-9)
# * `p` pico (10^-12)
# * `f` femto (10^-15)
# * `a` atto (10^-18)
# * `z` zepto (10^-21)
# * `y` yocto (10^-24)
# * `Ki` kibi (2^10)
# * `Mi` mebi (2^20)
# * `Gi` gibi (2^30)