google-api-client 0.36.3 → 0.36.4

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: ac8abfef0889e726c91049f01c73e9c4cf4fa951525dbd1c25ffd3d494fc2fdf
4
- data.tar.gz: 92adeb71a76d3bea7d1288163f9f73db07326f81945e6f900ae3906d466afa97
3
+ metadata.gz: 7629a7ab62bd0d438d251e606fc8f6bc9632bd7002723e7d1e5370bc1515c3ba
4
+ data.tar.gz: 19b922cf761b75881b58edd1b2d4267eb5eac196bae813c638a62426a0114f54
5
5
  SHA512:
6
- metadata.gz: d42f7495bf35537127efd1c7733698d60d925963354c3bc5140d8fb0833f50b399c610ef0d0779a12953510a833f412ff7ec013264a30f86310c33df5d9f0598
7
- data.tar.gz: cd75b418c1e2143cfbc925c1f300a235e82a686ead51d97a11bee771f7eae82b72d4dda1021f6cfaf0cd43a900946b6afb803eeb26737d2d832fa7959546bfb1
6
+ metadata.gz: cbdd711e1881b0ffcde93a327162847fbffa01b9c1f99fa420ea208ae6a79a0eedc8c919eccdb42a4a6fea82fa6da4a7615a0474c328aa74fb20246840b19b8a
7
+ data.tar.gz: 3f8570ab80417b75744a820d8d13ca031b922983f7ecffe77375801bef94d6eadeffc17b16e2e141adeada5e275c1fe06d442e0789f1662978bc5e2bc32964eb
@@ -1,3 +1,16 @@
1
+ # 0.36.4
2
+ * Backwards compatible changes:
3
+ * Updated `people_v1`
4
+ * Updated `remotebuildexecution_v1`
5
+ * Updated `remotebuildexecution_v1alpha`
6
+ * Updated `remotebuildexecution_v2`
7
+ * Updated `searchconsole_v1`
8
+ * Updated `serviceconsumermanagement_v1`
9
+ * Updated `servicenetworking_v1`
10
+ * Updated `servicenetworking_v1beta`
11
+ * Updated `serviceusage_v1`
12
+ * Updated `serviceusage_v1beta1`
13
+
1
14
  # 0.36.3
2
15
  * Backwards compatible changes:
3
16
  * Updated `healthcare_v1beta1`
@@ -25,7 +25,7 @@ module Google
25
25
  # @see https://developers.google.com/people/
26
26
  module PeopleV1
27
27
  VERSION = 'V1'
28
- REVISION = '20191030'
28
+ REVISION = '20191230'
29
29
 
30
30
  # See, edit, download, and permanently delete your contacts
31
31
  AUTH_CONTACTS = 'https://www.googleapis.com/auth/contacts'
@@ -42,6 +42,9 @@ module Google
42
42
  # View your email addresses
43
43
  AUTH_USER_EMAILS_READ = 'https://www.googleapis.com/auth/user.emails.read'
44
44
 
45
+ # See your education, work history and org info
46
+ AUTH_USER_ORGANIZATION_READ = 'https://www.googleapis.com/auth/user.organization.read'
47
+
45
48
  # View your phone numbers
46
49
  AUTH_USER_PHONENUMBERS_READ = 'https://www.googleapis.com/auth/user.phonenumbers.read'
47
50
 
@@ -25,7 +25,7 @@ module Google
25
25
  # @see https://cloud.google.com/remote-build-execution/docs/
26
26
  module RemotebuildexecutionV1
27
27
  VERSION = 'V1'
28
- REVISION = '20191211'
28
+ REVISION = '20200102'
29
29
 
30
30
  # View and manage your data across Google Cloud Platform services
31
31
  AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
@@ -25,7 +25,7 @@ module Google
25
25
  # @see https://cloud.google.com/remote-build-execution/docs/
26
26
  module RemotebuildexecutionV1alpha
27
27
  VERSION = 'V1alpha'
28
- REVISION = '20191211'
28
+ REVISION = '20200102'
29
29
 
30
30
  # View and manage your data across Google Cloud Platform services
31
31
  AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
@@ -25,7 +25,7 @@ module Google
25
25
  # @see https://cloud.google.com/remote-build-execution/docs/
26
26
  module RemotebuildexecutionV2
27
27
  VERSION = 'V2'
28
- REVISION = '20191211'
28
+ REVISION = '20200102'
29
29
 
30
30
  # View and manage your data across Google Cloud Platform services
31
31
  AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
@@ -25,7 +25,7 @@ module Google
25
25
  # @see https://developers.google.com/webmaster-tools/search-console-api/
26
26
  module SearchconsoleV1
27
27
  VERSION = 'V1'
28
- REVISION = '20180601'
28
+ REVISION = '20200104'
29
29
  end
30
30
  end
31
31
  end
@@ -25,7 +25,7 @@ module Google
25
25
  # @see https://cloud.google.com/service-consumer-management/docs/overview
26
26
  module ServiceconsumermanagementV1
27
27
  VERSION = 'V1'
28
- REVISION = '20191210'
28
+ REVISION = '20191230'
29
29
 
30
30
  # View and manage your data across Google Cloud Platform services
31
31
  AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
@@ -1927,6 +1927,48 @@ module Google
1927
1927
  # @return [String]
1928
1928
  attr_accessor :type
1929
1929
 
1930
+ # The units in which the metric value is reported. It is only applicable
1931
+ # if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
1932
+ # defines the representation of the stored metric values.
1933
+ # Different systems may scale the values to be more easily displayed (so a
1934
+ # value of `0.02KBy` _might_ be displayed as `20By`, and a value of
1935
+ # `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
1936
+ # `KBy`, then the value of the metric is always in thousands of bytes, no
1937
+ # matter how it may be displayed..
1938
+ # If you want a custom metric to record the exact number of CPU-seconds used
1939
+ # by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
1940
+ # `s`CPU`` (or equivalently `1s`CPU`` or just `s`). If the job uses 12,005
1941
+ # CPU-seconds, then the value is written as `12005`.
1942
+ # Alternatively, if you want a custom metric to record data in a more
1943
+ # granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
1944
+ # `ks`CPU``, and then write the value `12.005` (which is `12005/1000`),
1945
+ # or use `Kis`CPU`` and write `11.723` (which is `12005/1024`).
1946
+ # The supported units are a subset of [The Unified Code for Units of
1947
+ # Measure](http://unitsofmeasure.org/ucum.html) standard:
1948
+ # **Basic units (UNIT)**
1949
+ # * `bit` bit
1950
+ # * `By` byte
1951
+ # * `s` second
1952
+ # * `min` minute
1953
+ # * `h` hour
1954
+ # * `d` day
1955
+ # **Prefixes (PREFIX)**
1956
+ # * `k` kilo (10^3)
1957
+ # * `M` mega (10^6)
1958
+ # * `G` giga (10^9)
1959
+ # * `T` tera (10^12)
1960
+ # * `P` peta (10^15)
1961
+ # * `E` exa (10^18)
1962
+ # * `Z` zetta (10^21)
1963
+ # * `Y` yotta (10^24)
1964
+ # * `m` milli (10^-3)
1965
+ # * `u` micro (10^-6)
1966
+ # * `n` nano (10^-9)
1967
+ # * `p` pico (10^-12)
1968
+ # * `f` femto (10^-15)
1969
+ # * `a` atto (10^-18)
1970
+ # * `z` zepto (10^-21)
1971
+ # * `y` yocto (10^-24)
1930
1972
  # * `Ki` kibi (2^10)
1931
1973
  # * `Mi` mebi (2^20)
1932
1974
  # * `Gi` gibi (2^30)
@@ -26,7 +26,7 @@ module Google
26
26
  # @see https://cloud.google.com/service-infrastructure/docs/service-networking/getting-started
27
27
  module ServicenetworkingV1
28
28
  VERSION = 'V1'
29
- REVISION = '20191206'
29
+ REVISION = '20191230'
30
30
 
31
31
  # View and manage your data across Google Cloud Platform services
32
32
  AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
@@ -2008,6 +2008,48 @@ module Google
2008
2008
  # @return [String]
2009
2009
  attr_accessor :type
2010
2010
 
2011
+ # The units in which the metric value is reported. It is only applicable
2012
+ # if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
2013
+ # defines the representation of the stored metric values.
2014
+ # Different systems may scale the values to be more easily displayed (so a
2015
+ # value of `0.02KBy` _might_ be displayed as `20By`, and a value of
2016
+ # `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
2017
+ # `KBy`, then the value of the metric is always in thousands of bytes, no
2018
+ # matter how it may be displayed..
2019
+ # If you want a custom metric to record the exact number of CPU-seconds used
2020
+ # by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
2021
+ # `s`CPU`` (or equivalently `1s`CPU`` or just `s`). If the job uses 12,005
2022
+ # CPU-seconds, then the value is written as `12005`.
2023
+ # Alternatively, if you want a custom metric to record data in a more
2024
+ # granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
2025
+ # `ks`CPU``, and then write the value `12.005` (which is `12005/1000`),
2026
+ # or use `Kis`CPU`` and write `11.723` (which is `12005/1024`).
2027
+ # The supported units are a subset of [The Unified Code for Units of
2028
+ # Measure](http://unitsofmeasure.org/ucum.html) standard:
2029
+ # **Basic units (UNIT)**
2030
+ # * `bit` bit
2031
+ # * `By` byte
2032
+ # * `s` second
2033
+ # * `min` minute
2034
+ # * `h` hour
2035
+ # * `d` day
2036
+ # **Prefixes (PREFIX)**
2037
+ # * `k` kilo (10^3)
2038
+ # * `M` mega (10^6)
2039
+ # * `G` giga (10^9)
2040
+ # * `T` tera (10^12)
2041
+ # * `P` peta (10^15)
2042
+ # * `E` exa (10^18)
2043
+ # * `Z` zetta (10^21)
2044
+ # * `Y` yotta (10^24)
2045
+ # * `m` milli (10^-3)
2046
+ # * `u` micro (10^-6)
2047
+ # * `n` nano (10^-9)
2048
+ # * `p` pico (10^-12)
2049
+ # * `f` femto (10^-15)
2050
+ # * `a` atto (10^-18)
2051
+ # * `z` zepto (10^-21)
2052
+ # * `y` yocto (10^-24)
2011
2053
  # * `Ki` kibi (2^10)
2012
2054
  # * `Mi` mebi (2^20)
2013
2055
  # * `Gi` gibi (2^30)
@@ -26,7 +26,7 @@ module Google
26
26
  # @see https://cloud.google.com/service-infrastructure/docs/service-networking/getting-started
27
27
  module ServicenetworkingV1beta
28
28
  VERSION = 'V1beta'
29
- REVISION = '20191206'
29
+ REVISION = '20191230'
30
30
 
31
31
  # View and manage your data across Google Cloud Platform services
32
32
  AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
@@ -1882,6 +1882,48 @@ module Google
1882
1882
  # @return [String]
1883
1883
  attr_accessor :type
1884
1884
 
1885
+ # The units in which the metric value is reported. It is only applicable
1886
+ # if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
1887
+ # defines the representation of the stored metric values.
1888
+ # Different systems may scale the values to be more easily displayed (so a
1889
+ # value of `0.02KBy` _might_ be displayed as `20By`, and a value of
1890
+ # `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
1891
+ # `KBy`, then the value of the metric is always in thousands of bytes, no
1892
+ # matter how it may be displayed..
1893
+ # If you want a custom metric to record the exact number of CPU-seconds used
1894
+ # by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
1895
+ # `s`CPU`` (or equivalently `1s`CPU`` or just `s`). If the job uses 12,005
1896
+ # CPU-seconds, then the value is written as `12005`.
1897
+ # Alternatively, if you want a custom metric to record data in a more
1898
+ # granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
1899
+ # `ks`CPU``, and then write the value `12.005` (which is `12005/1000`),
1900
+ # or use `Kis`CPU`` and write `11.723` (which is `12005/1024`).
1901
+ # The supported units are a subset of [The Unified Code for Units of
1902
+ # Measure](http://unitsofmeasure.org/ucum.html) standard:
1903
+ # **Basic units (UNIT)**
1904
+ # * `bit` bit
1905
+ # * `By` byte
1906
+ # * `s` second
1907
+ # * `min` minute
1908
+ # * `h` hour
1909
+ # * `d` day
1910
+ # **Prefixes (PREFIX)**
1911
+ # * `k` kilo (10^3)
1912
+ # * `M` mega (10^6)
1913
+ # * `G` giga (10^9)
1914
+ # * `T` tera (10^12)
1915
+ # * `P` peta (10^15)
1916
+ # * `E` exa (10^18)
1917
+ # * `Z` zetta (10^21)
1918
+ # * `Y` yotta (10^24)
1919
+ # * `m` milli (10^-3)
1920
+ # * `u` micro (10^-6)
1921
+ # * `n` nano (10^-9)
1922
+ # * `p` pico (10^-12)
1923
+ # * `f` femto (10^-15)
1924
+ # * `a` atto (10^-18)
1925
+ # * `z` zepto (10^-21)
1926
+ # * `y` yocto (10^-24)
1885
1927
  # * `Ki` kibi (2^10)
1886
1928
  # * `Mi` mebi (2^20)
1887
1929
  # * `Gi` gibi (2^30)
@@ -27,7 +27,7 @@ module Google
27
27
  # @see https://cloud.google.com/service-usage/
28
28
  module ServiceusageV1
29
29
  VERSION = 'V1'
30
- REVISION = '20191206'
30
+ REVISION = '20191230'
31
31
 
32
32
  # View and manage your data across Google Cloud Platform services
33
33
  AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
@@ -2716,6 +2716,48 @@ module Google
2716
2716
  # @return [String]
2717
2717
  attr_accessor :type
2718
2718
 
2719
+ # The units in which the metric value is reported. It is only applicable
2720
+ # if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
2721
+ # defines the representation of the stored metric values.
2722
+ # Different systems may scale the values to be more easily displayed (so a
2723
+ # value of `0.02KBy` _might_ be displayed as `20By`, and a value of
2724
+ # `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
2725
+ # `KBy`, then the value of the metric is always in thousands of bytes, no
2726
+ # matter how it may be displayed..
2727
+ # If you want a custom metric to record the exact number of CPU-seconds used
2728
+ # by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
2729
+ # `s`CPU`` (or equivalently `1s`CPU`` or just `s`). If the job uses 12,005
2730
+ # CPU-seconds, then the value is written as `12005`.
2731
+ # Alternatively, if you want a custom metric to record data in a more
2732
+ # granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
2733
+ # `ks`CPU``, and then write the value `12.005` (which is `12005/1000`),
2734
+ # or use `Kis`CPU`` and write `11.723` (which is `12005/1024`).
2735
+ # The supported units are a subset of [The Unified Code for Units of
2736
+ # Measure](http://unitsofmeasure.org/ucum.html) standard:
2737
+ # **Basic units (UNIT)**
2738
+ # * `bit` bit
2739
+ # * `By` byte
2740
+ # * `s` second
2741
+ # * `min` minute
2742
+ # * `h` hour
2743
+ # * `d` day
2744
+ # **Prefixes (PREFIX)**
2745
+ # * `k` kilo (10^3)
2746
+ # * `M` mega (10^6)
2747
+ # * `G` giga (10^9)
2748
+ # * `T` tera (10^12)
2749
+ # * `P` peta (10^15)
2750
+ # * `E` exa (10^18)
2751
+ # * `Z` zetta (10^21)
2752
+ # * `Y` yotta (10^24)
2753
+ # * `m` milli (10^-3)
2754
+ # * `u` micro (10^-6)
2755
+ # * `n` nano (10^-9)
2756
+ # * `p` pico (10^-12)
2757
+ # * `f` femto (10^-15)
2758
+ # * `a` atto (10^-18)
2759
+ # * `z` zepto (10^-21)
2760
+ # * `y` yocto (10^-24)
2719
2761
  # * `Ki` kibi (2^10)
2720
2762
  # * `Mi` mebi (2^20)
2721
2763
  # * `Gi` gibi (2^30)
@@ -27,7 +27,7 @@ module Google
27
27
  # @see https://cloud.google.com/service-usage/
28
28
  module ServiceusageV1beta1
29
29
  VERSION = 'V1beta1'
30
- REVISION = '20191206'
30
+ REVISION = '20191230'
31
31
 
32
32
  # View and manage your data across Google Cloud Platform services
33
33
  AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'
@@ -2694,6 +2694,48 @@ module Google
2694
2694
  # @return [String]
2695
2695
  attr_accessor :type
2696
2696
 
2697
+ # The units in which the metric value is reported. It is only applicable
2698
+ # if the `value_type` is `INT64`, `DOUBLE`, or `DISTRIBUTION`. The `unit`
2699
+ # defines the representation of the stored metric values.
2700
+ # Different systems may scale the values to be more easily displayed (so a
2701
+ # value of `0.02KBy` _might_ be displayed as `20By`, and a value of
2702
+ # `3523KBy` _might_ be displayed as `3.5MBy`). However, if the `unit` is
2703
+ # `KBy`, then the value of the metric is always in thousands of bytes, no
2704
+ # matter how it may be displayed..
2705
+ # If you want a custom metric to record the exact number of CPU-seconds used
2706
+ # by a job, you can create an `INT64 CUMULATIVE` metric whose `unit` is
2707
+ # `s`CPU`` (or equivalently `1s`CPU`` or just `s`). If the job uses 12,005
2708
+ # CPU-seconds, then the value is written as `12005`.
2709
+ # Alternatively, if you want a custom metric to record data in a more
2710
+ # granular way, you can create a `DOUBLE CUMULATIVE` metric whose `unit` is
2711
+ # `ks`CPU``, and then write the value `12.005` (which is `12005/1000`),
2712
+ # or use `Kis`CPU`` and write `11.723` (which is `12005/1024`).
2713
+ # The supported units are a subset of [The Unified Code for Units of
2714
+ # Measure](http://unitsofmeasure.org/ucum.html) standard:
2715
+ # **Basic units (UNIT)**
2716
+ # * `bit` bit
2717
+ # * `By` byte
2718
+ # * `s` second
2719
+ # * `min` minute
2720
+ # * `h` hour
2721
+ # * `d` day
2722
+ # **Prefixes (PREFIX)**
2723
+ # * `k` kilo (10^3)
2724
+ # * `M` mega (10^6)
2725
+ # * `G` giga (10^9)
2726
+ # * `T` tera (10^12)
2727
+ # * `P` peta (10^15)
2728
+ # * `E` exa (10^18)
2729
+ # * `Z` zetta (10^21)
2730
+ # * `Y` yotta (10^24)
2731
+ # * `m` milli (10^-3)
2732
+ # * `u` micro (10^-6)
2733
+ # * `n` nano (10^-9)
2734
+ # * `p` pico (10^-12)
2735
+ # * `f` femto (10^-15)
2736
+ # * `a` atto (10^-18)
2737
+ # * `z` zepto (10^-21)
2738
+ # * `y` yocto (10^-24)
2697
2739
  # * `Ki` kibi (2^10)
2698
2740
  # * `Mi` mebi (2^20)
2699
2741
  # * `Gi` gibi (2^30)
@@ -15,7 +15,7 @@
15
15
  module Google
16
16
  module Apis
17
17
  # Client library version
18
- VERSION = '0.36.3'.freeze
18
+ VERSION = '0.36.4'.freeze
19
19
 
20
20
  # Current operating system
21
21
  # @private
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-api-client
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.36.3
4
+ version: 0.36.4
5
5
  platform: ruby
6
6
  authors:
7
7
  - Steven Bazyl
@@ -11,7 +11,7 @@ authors:
11
11
  autorequire:
12
12
  bindir: bin
13
13
  cert_chain: []
14
- date: 2019-12-30 00:00:00.000000000 Z
14
+ date: 2020-01-06 00:00:00.000000000 Z
15
15
  dependencies:
16
16
  - !ruby/object:Gem::Dependency
17
17
  name: representable
@@ -1351,7 +1351,7 @@ homepage: https://github.com/google/google-api-ruby-client
1351
1351
  licenses:
1352
1352
  - Apache-2.0
1353
1353
  metadata:
1354
- documentation_uri: https://googleapis.dev/ruby/google-api-client/v0.36.3
1354
+ documentation_uri: https://googleapis.dev/ruby/google-api-client/v0.36.4
1355
1355
  post_install_message:
1356
1356
  rdoc_options: []
1357
1357
  require_paths: