Skip to content

Commit f5eaefe

Browse files
feat: Automated regeneration of monitoring v3 client (#5802)
This PR was generated using Autosynth. 🌈 <details><summary>Log from Synthtool</summary> ``` 2021-07-16 03:52:02,066 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-api-ruby-client/synth.py. On branch autosynth-monitoring-v3 nothing to commit, working tree clean 2021-07-16 03:52:02,135 synthtool [DEBUG] > Running: docker run --rm -v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace -v/var/run/docker.sock:/var/run/docker.sock -w /workspace -e USER_GROUP=1000:1000 --entrypoint script/synth.rb gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth monitoring v3 DEBUG:synthtool:Running: docker run --rm -v/home/kbuilder/.cache/synthtool/google-api-ruby-client:/workspace -v/var/run/docker.sock:/var/run/docker.sock -w /workspace -e USER_GROUP=1000:1000 --entrypoint script/synth.rb gcr.io/cloud-devrel-kokoro-resources/yoshi-ruby/autosynth monitoring v3 git clean -df bundle install Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine. Fetching gem metadata from https://rubygems.org/......... Resolving dependencies... Fetching rake 13.0.6 Installing rake 13.0.6 Fetching concurrent-ruby 1.1.9 Fetching minitest 5.14.4 Fetching public_suffix 4.0.6 Fetching zeitwerk 2.4.2 Installing zeitwerk 2.4.2 Installing public_suffix 4.0.6 Installing minitest 5.14.4 Installing concurrent-ruby 1.1.9 Fetching ast 2.4.2 Installing ast 2.4.2 Using bundler 2.2.17 Fetching byebug 11.1.3 Installing byebug 11.1.3 with native extensions Fetching coderay 1.1.3 Installing coderay 1.1.3 Fetching json 2.5.1 Installing json 2.5.1 with native extensions Fetching docile 1.4.0 Installing docile 1.4.0 Fetching simplecov-html 0.10.2 Installing simplecov-html 0.10.2 Using sync 0.5.0 Fetching thor 1.1.0 Installing thor 1.1.0 Fetching rexml 3.2.5 Fetching declarative 0.0.20 Installing rexml 3.2.5 Installing declarative 0.0.20 Fetching diff-lcs 1.4.4 Installing diff-lcs 1.4.4 Fetching dotenv 2.7.6 Installing dotenv 2.7.6 Fetching fakefs 0.20.1 Fetching faraday-em_http 1.0.0 Installing fakefs 0.20.1 Installing faraday-em_http 1.0.0 Fetching faraday-em_synchrony 1.0.0 Fetching faraday-excon 1.1.0 Installing faraday-em_synchrony 1.0.0 Installing faraday-excon 1.1.0 Fetching faraday-net_http 1.0.1 Fetching faraday-httpclient 1.0.1 Installing faraday-net_http 1.0.1 Fetching faraday-net_http_persistent 1.2.0 Installing faraday-httpclient 1.0.1 Fetching faraday-patron 1.0.0 Installing faraday-net_http_persistent 1.2.0 Fetching multipart-post 2.1.1 Installing faraday-patron 1.0.0 Fetching ruby2_keywords 0.0.5 Installing multipart-post 2.1.1 Installing ruby2_keywords 0.0.5 Fetching gems 1.2.0 Fetching github-markup 1.7.0 Installing gems 1.2.0 Installing github-markup 1.7.0 Fetching jwt 2.2.3 Installing jwt 2.2.3 Fetching memoist 0.16.2 Fetching multi_json 1.15.0 Installing memoist 0.16.2 Installing multi_json 1.15.0 Fetching os 0.9.6 Fetching httpclient 2.8.3 Installing os 0.9.6 Fetching mini_mime 1.1.0 Installing mini_mime 1.1.0 Installing httpclient 2.8.3 Fetching trailblazer-option 0.1.1 Installing trailblazer-option 0.1.1 Fetching uber 0.1.0 Fetching retriable 3.1.2 Fetching webrick 1.7.0 Installing uber 0.1.0 Installing retriable 3.1.2 Installing webrick 1.7.0 Fetching hashdiff 1.0.1 Fetching mime-types-data 3.2021.0704 Installing hashdiff 1.0.1 Installing mime-types-data 3.2021.0704 Fetching multi_xml 0.6.0 Installing multi_xml 0.6.0 Fetching rspec-support 3.10.2 Fetching little-plugger 1.1.4 Fetching method_source 1.0.0 Installing rspec-support 3.10.2 Installing little-plugger 1.1.4 Installing method_source 1.0.0 Fetching opencensus 0.5.0 Installing opencensus 0.5.0 Fetching parallel 1.20.1 Installing parallel 1.20.1 Fetching powerpack 0.1.3 Fetching yard 0.9.26 Installing powerpack 0.1.3 Installing yard 0.9.26 Fetching rainbow 2.2.2 Installing rainbow 2.2.2 with native extensions Fetching redcarpet 3.5.1 Installing redcarpet 3.5.1 with native extensions Fetching redis 3.3.5 Installing redis 3.3.5 Fetching rmail 1.1.4 Installing rmail 1.1.4 Fetching ruby-progressbar 1.11.0 Fetching unicode-display_width 1.7.0 Installing ruby-progressbar 1.11.0 Installing unicode-display_width 1.7.0 Fetching parser 2.7.2.0 Fetching addressable 2.8.0 Installing addressable 2.8.0 Installing parser 2.7.2.0 Fetching i18n 1.8.10 Fetching tzinfo 2.0.4 Installing i18n 1.8.10 Installing tzinfo 2.0.4 Fetching tins 1.29.1 Fetching crack 0.4.5 Fetching faraday 1.5.1 Installing tins 1.29.1 Installing crack 0.4.5 Installing faraday 1.5.1 Fetching google-id-token 1.4.2 Installing google-id-token 1.4.2 Fetching representable 3.1.1 Installing representable 3.1.1 Fetching mime-types 3.3.1 Installing mime-types 3.3.1 Fetching logging 2.3.0 Fetching pry 0.13.1 Installing logging 2.3.0 Installing pry 0.13.1 Fetching rspec-core 3.10.1 Installing rspec-core 3.10.1 Fetching rspec-expectations 3.10.1 Installing rspec-expectations 3.10.1 Fetching rspec-mocks 3.10.2 Fetching simplecov 0.16.1 Fetching launchy 2.5.0 Installing launchy 2.5.0 Installing rspec-mocks 3.10.2 Installing simplecov 0.16.1 Fetching rubocop 0.49.1 Fetching activesupport 6.1.4 Fetching webmock 2.3.2 Installing webmock 2.3.2 Installing activesupport 6.1.4 Installing rubocop 0.49.1 Fetching signet 0.15.0 Installing signet 0.15.0 Fetching httparty 0.18.1 Installing httparty 0.18.1 Fetching term-ansicolor 1.7.1 Installing term-ansicolor 1.7.1 Fetching pry-byebug 3.9.0 Fetching pry-doc 0.13.5 Installing pry-byebug 3.9.0 Fetching rspec 3.10.0 Installing rspec 3.10.0 Fetching googleauth 0.16.2 Fetching coveralls 0.8.23 Installing googleauth 0.16.2 Installing coveralls 0.8.23 Fetching json_spec 1.1.5 Installing json_spec 1.1.5 Installing pry-doc 0.13.5 Fetching google-apis-core 0.4.0 Installing google-apis-core 0.4.0 Fetching google-apis-discovery_v1 0.6.0 Installing google-apis-discovery_v1 0.6.0 Using google-apis-generator 0.4.0 from source at `.` and installing its executables Bundle complete! 25 Gemfile dependencies, 88 gems now installed. Use `bundle info [gemname]` to see where a bundled gem is installed. Post-install message from httparty: When you HTTParty, you must party hard! echo a | bundle exec bin/generate-api gen /workspace/generated --api=monitoring.v3 --names=/workspace/api_names.yaml --names-out=/workspace/api_names_out.yaml --spot-check Loading monitoring, version v3 from https://raw.githubusercontent.com/googleapis/discovery-artifact-manager/master/discoveries/monitoring.v3.json W, [2021-07-16T10:52:18.512570 #225] WARN -- : Found reserved property 'method' W, [2021-07-16T10:52:18.512648 #225] WARN -- : Changed to 'method_prop' conflict google-apis-monitoring_v3/lib/google/apis/monitoring_v3.rb <s/monitoring_v3.rb? (enter "h" for help) [Ynaqdhm] a force google-apis-monitoring_v3/lib/google/apis/monitoring_v3.rb conflict google-apis-monitoring_v3/lib/google/apis/monitoring_v3/classes.rb force google-apis-monitoring_v3/lib/google/apis/monitoring_v3/classes.rb conflict google-apis-monitoring_v3/lib/google/apis/monitoring_v3/service.rb force google-apis-monitoring_v3/lib/google/apis/monitoring_v3/service.rb conflict google-apis-monitoring_v3/lib/google/apis/monitoring_v3/gem_version.rb force google-apis-monitoring_v3/lib/google/apis/monitoring_v3/gem_version.rb conflict google-apis-monitoring_v3/CHANGELOG.md force google-apis-monitoring_v3/CHANGELOG.md Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine. Fetching gem metadata from https://rubygems.org/......... Resolving dependencies... Using rake 13.0.6 Using public_suffix 4.0.6 Using bundler 2.2.17 Using declarative 0.0.20 Using diff-lcs 1.4.4 Using faraday-em_http 1.0.0 Using faraday-em_synchrony 1.0.0 Using faraday-excon 1.1.0 Using faraday-httpclient 1.0.1 Using faraday-net_http 1.0.1 Using faraday-net_http_persistent 1.2.0 Using faraday-patron 1.0.0 Using multipart-post 2.1.1 Using ruby2_keywords 0.0.5 Using jwt 2.2.3 Using memoist 0.16.2 Using multi_json 1.15.0 Fetching os 1.1.1 Using httpclient 2.8.3 Using mini_mime 1.1.0 Using trailblazer-option 0.1.1 Using uber 0.1.0 Using retriable 3.1.2 Using rexml 3.2.5 Using webrick 1.7.0 Using opencensus 0.5.0 Using redcarpet 3.5.1 Using rspec-support 3.10.2 Using yard 0.9.26 Using addressable 2.8.0 Using representable 3.1.1 Using faraday 1.5.1 Using rspec-core 3.10.1 Using rspec-expectations 3.10.1 Using rspec-mocks 3.10.2 Using signet 0.15.0 Using rspec 3.10.0 Installing os 1.1.1 Using googleauth 0.16.2 Using google-apis-core 0.4.0 Using google-apis-monitoring_v3 0.12.0 from source at `.` Bundle complete! 8 Gemfile dependencies, 40 gems now installed. Use `bundle info [gemname]` to see where a bundled gem is installed. /root/.rbenv/versions/2.6.7/bin/ruby -I/root/.rbenv/versions/2.6.7/lib/ruby/gems/2.6.0/gems/rspec-core-3.10.1/lib:/root/.rbenv/versions/2.6.7/lib/ruby/gems/2.6.0/gems/rspec-support-3.10.2/lib /root/.rbenv/versions/2.6.7/lib/ruby/gems/2.6.0/gems/rspec-core-3.10.1/exe/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb Google::Apis::MonitoringV3 should load Finished in 0.34525 seconds (files took 0.09691 seconds to load) 1 example, 0 failures Files: 4 Modules: 3 ( 1 undocumented) Classes: 103 ( 0 undocumented) Constants: 8 ( 0 undocumented) Attributes: 223 ( 0 undocumented) Methods: 254 ( 0 undocumented) 99.83% documented google-apis-monitoring_v3 0.12.0 built to pkg/google-apis-monitoring_v3-0.12.0.gem. identical /workspace/api_names_out.yaml chown -R 1000:1000 /workspace/generated 2021-07-16 03:52:33,051 synthtool [DEBUG] > Wrote metadata to generated/google-apis-monitoring_v3/synth.metadata. DEBUG:synthtool:Wrote metadata to generated/google-apis-monitoring_v3/synth.metadata. ``` </details> Full log will be available here: https://source.cloud.google.com/results/invocations/0c07da54-e214-4319-b7e0-d829f5496bf7/targets - [ ] To automatically regenerate this PR, check this box. (May take up to 24 hours.)
1 parent bc70543 commit f5eaefe

File tree

6 files changed

+88
-73
lines changed

6 files changed

+88
-73
lines changed

generated/google-apis-monitoring_v3/CHANGELOG.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
# Release history for google-apis-monitoring_v3
22

3+
### v0.12.0 (2021-07-16)
4+
5+
* Regenerated from discovery document revision 20210712
6+
37
### v0.11.0 (2021-07-06)
48

59
* Regenerated from discovery document revision 20210702

generated/google-apis-monitoring_v3/lib/google/apis/monitoring_v3.rb

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,8 @@ module Apis
2525
# associated with a Workspace, with a few exceptions as noted on the individual
2626
# method pages. The table entries below are presented in alphabetical order, not
2727
# in order of common use. For explanations of the concepts found in the table
28-
# entries, read the Cloud Monitoring documentation.
28+
# entries, read the Cloud Monitoring documentation (https://cloud.google.com/
29+
# monitoring/docs).
2930
#
3031
# @see https://cloud.google.com/monitoring/api/
3132
module MonitoringV3

generated/google-apis-monitoring_v3/lib/google/apis/monitoring_v3/classes.rb

Lines changed: 77 additions & 68 deletions
Original file line numberDiff line numberDiff line change
@@ -674,8 +674,9 @@ class Condition
674674
# @return [Google::Apis::MonitoringV3::MetricAbsence]
675675
attr_accessor :condition_absent
676676

677-
# A condition type that checks whether a log message from any project monitored
678-
# by the alert policy’s workspace satisfies the given filter.
677+
# A condition type that checks whether a log message in the scoping project (
678+
# https://cloud.google.com/monitoring/api/v3#project_name) satisfies the given
679+
# filter. Logs from other projects in the metrics scope are not evaluated.
679680
# Corresponds to the JSON property `conditionMatchedLog`
680681
# @return [Google::Apis::MonitoringV3::LogMatch]
681682
attr_accessor :condition_matched_log
@@ -2162,8 +2163,9 @@ def update!(**args)
21622163
end
21632164
end
21642165

2165-
# A condition type that checks whether a log message from any project monitored
2166-
# by the alert policy’s workspace satisfies the given filter.
2166+
# A condition type that checks whether a log message in the scoping project (
2167+
# https://cloud.google.com/monitoring/api/v3#project_name) satisfies the given
2168+
# filter. Logs from other projects in the metrics scope are not evaluated.
21672169
class LogMatch
21682170
include Google::Apis::Core::Hashable
21692171

@@ -2646,7 +2648,8 @@ class MonitoredResource
26462648
# Required. The monitored resource type. This field must match the type field of
26472649
# a MonitoredResourceDescriptor object. For example, the type of a Compute
26482650
# Engine VM instance is gce_instance. For a list of types, see Monitoring
2649-
# resource types and Logging resource types.
2651+
# resource types (https://cloud.google.com/monitoring/api/resources) and Logging
2652+
# resource types (https://cloud.google.com/logging/docs/api/v2/resource-list).
26502653
# Corresponds to the JSON property `type`
26512654
# @return [String]
26522655
attr_accessor :type
@@ -3124,28 +3127,30 @@ class Point
31243127

31253128
# A closed time interval. It extends from the start time to the end time, and
31263129
# includes both: [startTime, endTime]. Valid time intervals depend on the
3127-
# MetricKind of the metric value. The end time must not be earlier than the
3128-
# start time. When writing data points, the start time must not be more than 25
3129-
# hours in the past and the end time must not be more than five minutes in the
3130-
# future. For GAUGE metrics, the startTime value is technically optional; if no
3131-
# value is specified, the start time defaults to the value of the end time, and
3132-
# the interval represents a single point in time. If both start and end times
3133-
# are specified, they must be identical. Such an interval is valid only for
3134-
# GAUGE metrics, which are point-in-time measurements. The end time of a new
3130+
# MetricKind (https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.
3131+
# metricDescriptors#MetricKind) of the metric value. The end time must not be
3132+
# earlier than the start time. When writing data points, the start time must not
3133+
# be more than 25 hours in the past and the end time must not be more than five
3134+
# minutes in the future. For GAUGE metrics, the startTime value is technically
3135+
# optional; if no value is specified, the start time defaults to the value of
3136+
# the end time, and the interval represents a single point in time. If both
3137+
# start and end times are specified, they must be identical. Such an interval is
3138+
# valid only for GAUGE metrics, which are point-in-time measurements. The end
3139+
# time of a new interval must be at least a millisecond after the end time of
3140+
# the previous interval. For DELTA metrics, the start time and end time must
3141+
# specify a non-zero interval, with subsequent points specifying contiguous and
3142+
# non-overlapping intervals. For DELTA metrics, the start time of the next
31353143
# interval must be at least a millisecond after the end time of the previous
3136-
# interval. For DELTA metrics, the start time and end time must specify a non-
3137-
# zero interval, with subsequent points specifying contiguous and non-
3138-
# overlapping intervals. For DELTA metrics, the start time of the next interval
3139-
# must be at least a millisecond after the end time of the previous interval.
3140-
# For CUMULATIVE metrics, the start time and end time must specify a a non-zero
3141-
# interval, with subsequent points specifying the same start time and increasing
3142-
# end times, until an event resets the cumulative value to zero and sets a new
3143-
# start time for the following points. The new start time must be at least a
3144-
# millisecond after the end time of the previous interval. The start time of a
3145-
# new interval must be at least a millisecond after the end time of the previous
3146-
# interval because intervals are closed. If the start time of a new interval is
3147-
# the same as the end time of the previous interval, then data written at the
3148-
# new start time could overwrite data written at the previous end time.
3144+
# interval. For CUMULATIVE metrics, the start time and end time must specify a a
3145+
# non-zero interval, with subsequent points specifying the same start time and
3146+
# increasing end times, until an event resets the cumulative value to zero and
3147+
# sets a new start time for the following points. The new start time must be at
3148+
# least a millisecond after the end time of the previous interval. The start
3149+
# time of a new interval must be at least a millisecond after the end time of
3150+
# the previous interval because intervals are closed. If the start time of a new
3151+
# interval is the same as the end time of the previous interval, then data
3152+
# written at the new start time could overwrite data written at the previous end
3153+
# time.
31493154
# Corresponds to the JSON property `interval`
31503155
# @return [Google::Apis::MonitoringV3::TimeInterval]
31513156
attr_accessor :interval
@@ -3174,28 +3179,30 @@ class PointData
31743179

31753180
# A closed time interval. It extends from the start time to the end time, and
31763181
# includes both: [startTime, endTime]. Valid time intervals depend on the
3177-
# MetricKind of the metric value. The end time must not be earlier than the
3178-
# start time. When writing data points, the start time must not be more than 25
3179-
# hours in the past and the end time must not be more than five minutes in the
3180-
# future. For GAUGE metrics, the startTime value is technically optional; if no
3181-
# value is specified, the start time defaults to the value of the end time, and
3182-
# the interval represents a single point in time. If both start and end times
3183-
# are specified, they must be identical. Such an interval is valid only for
3184-
# GAUGE metrics, which are point-in-time measurements. The end time of a new
3182+
# MetricKind (https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.
3183+
# metricDescriptors#MetricKind) of the metric value. The end time must not be
3184+
# earlier than the start time. When writing data points, the start time must not
3185+
# be more than 25 hours in the past and the end time must not be more than five
3186+
# minutes in the future. For GAUGE metrics, the startTime value is technically
3187+
# optional; if no value is specified, the start time defaults to the value of
3188+
# the end time, and the interval represents a single point in time. If both
3189+
# start and end times are specified, they must be identical. Such an interval is
3190+
# valid only for GAUGE metrics, which are point-in-time measurements. The end
3191+
# time of a new interval must be at least a millisecond after the end time of
3192+
# the previous interval. For DELTA metrics, the start time and end time must
3193+
# specify a non-zero interval, with subsequent points specifying contiguous and
3194+
# non-overlapping intervals. For DELTA metrics, the start time of the next
31853195
# interval must be at least a millisecond after the end time of the previous
3186-
# interval. For DELTA metrics, the start time and end time must specify a non-
3187-
# zero interval, with subsequent points specifying contiguous and non-
3188-
# overlapping intervals. For DELTA metrics, the start time of the next interval
3189-
# must be at least a millisecond after the end time of the previous interval.
3190-
# For CUMULATIVE metrics, the start time and end time must specify a a non-zero
3191-
# interval, with subsequent points specifying the same start time and increasing
3192-
# end times, until an event resets the cumulative value to zero and sets a new
3193-
# start time for the following points. The new start time must be at least a
3194-
# millisecond after the end time of the previous interval. The start time of a
3195-
# new interval must be at least a millisecond after the end time of the previous
3196-
# interval because intervals are closed. If the start time of a new interval is
3197-
# the same as the end time of the previous interval, then data written at the
3198-
# new start time could overwrite data written at the previous end time.
3196+
# interval. For CUMULATIVE metrics, the start time and end time must specify a a
3197+
# non-zero interval, with subsequent points specifying the same start time and
3198+
# increasing end times, until an event resets the cumulative value to zero and
3199+
# sets a new start time for the following points. The new start time must be at
3200+
# least a millisecond after the end time of the previous interval. The start
3201+
# time of a new interval must be at least a millisecond after the end time of
3202+
# the previous interval because intervals are closed. If the start time of a new
3203+
# interval is the same as the end time of the previous interval, then data
3204+
# written at the new start time could overwrite data written at the previous end
3205+
# time.
31993206
# Corresponds to the JSON property `timeInterval`
32003207
# @return [Google::Apis::MonitoringV3::TimeInterval]
32013208
attr_accessor :time_interval
@@ -3734,28 +3741,30 @@ def update!(**args)
37343741

37353742
# A closed time interval. It extends from the start time to the end time, and
37363743
# includes both: [startTime, endTime]. Valid time intervals depend on the
3737-
# MetricKind of the metric value. The end time must not be earlier than the
3738-
# start time. When writing data points, the start time must not be more than 25
3739-
# hours in the past and the end time must not be more than five minutes in the
3740-
# future. For GAUGE metrics, the startTime value is technically optional; if no
3741-
# value is specified, the start time defaults to the value of the end time, and
3742-
# the interval represents a single point in time. If both start and end times
3743-
# are specified, they must be identical. Such an interval is valid only for
3744-
# GAUGE metrics, which are point-in-time measurements. The end time of a new
3744+
# MetricKind (https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.
3745+
# metricDescriptors#MetricKind) of the metric value. The end time must not be
3746+
# earlier than the start time. When writing data points, the start time must not
3747+
# be more than 25 hours in the past and the end time must not be more than five
3748+
# minutes in the future. For GAUGE metrics, the startTime value is technically
3749+
# optional; if no value is specified, the start time defaults to the value of
3750+
# the end time, and the interval represents a single point in time. If both
3751+
# start and end times are specified, they must be identical. Such an interval is
3752+
# valid only for GAUGE metrics, which are point-in-time measurements. The end
3753+
# time of a new interval must be at least a millisecond after the end time of
3754+
# the previous interval. For DELTA metrics, the start time and end time must
3755+
# specify a non-zero interval, with subsequent points specifying contiguous and
3756+
# non-overlapping intervals. For DELTA metrics, the start time of the next
37453757
# interval must be at least a millisecond after the end time of the previous
3746-
# interval. For DELTA metrics, the start time and end time must specify a non-
3747-
# zero interval, with subsequent points specifying contiguous and non-
3748-
# overlapping intervals. For DELTA metrics, the start time of the next interval
3749-
# must be at least a millisecond after the end time of the previous interval.
3750-
# For CUMULATIVE metrics, the start time and end time must specify a a non-zero
3751-
# interval, with subsequent points specifying the same start time and increasing
3752-
# end times, until an event resets the cumulative value to zero and sets a new
3753-
# start time for the following points. The new start time must be at least a
3754-
# millisecond after the end time of the previous interval. The start time of a
3755-
# new interval must be at least a millisecond after the end time of the previous
3756-
# interval because intervals are closed. If the start time of a new interval is
3757-
# the same as the end time of the previous interval, then data written at the
3758-
# new start time could overwrite data written at the previous end time.
3758+
# interval. For CUMULATIVE metrics, the start time and end time must specify a a
3759+
# non-zero interval, with subsequent points specifying the same start time and
3760+
# increasing end times, until an event resets the cumulative value to zero and
3761+
# sets a new start time for the following points. The new start time must be at
3762+
# least a millisecond after the end time of the previous interval. The start
3763+
# time of a new interval must be at least a millisecond after the end time of
3764+
# the previous interval because intervals are closed. If the start time of a new
3765+
# interval is the same as the end time of the previous interval, then data
3766+
# written at the new start time could overwrite data written at the previous end
3767+
# time.
37593768
class TimeInterval
37603769
include Google::Apis::Core::Hashable
37613770

generated/google-apis-monitoring_v3/lib/google/apis/monitoring_v3/gem_version.rb

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,13 @@ module Google
1616
module Apis
1717
module MonitoringV3
1818
# Version of the google-apis-monitoring_v3 gem
19-
GEM_VERSION = "0.11.0"
19+
GEM_VERSION = "0.12.0"
2020

2121
# Version of the code generator used to generate this client
2222
GENERATOR_VERSION = "0.4.0"
2323

2424
# Revision of the discovery document this client was generated from
25-
REVISION = "20210702"
25+
REVISION = "20210712"
2626
end
2727
end
2828
end

generated/google-apis-monitoring_v3/lib/google/apis/monitoring_v3/service.rb

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,8 @@ module MonitoringV3
2626
# associated with a Workspace, with a few exceptions as noted on the individual
2727
# method pages. The table entries below are presented in alphabetical order, not
2828
# in order of common use. For explanations of the concepts found in the table
29-
# entries, read the Cloud Monitoring documentation.
29+
# entries, read the Cloud Monitoring documentation (https://cloud.google.com/
30+
# monitoring/docs).
3031
#
3132
# @example
3233
# require 'google/apis/monitoring_v3'

generated/google-apis-monitoring_v3/synth.metadata

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
"git": {
55
"name": ".",
66
"remote": "https://github.com/googleapis/google-api-ruby-client.git",
7-
"sha": "1de6cb5e8ac205a8b13b033d432aa1def5e1e2db"
7+
"sha": "822eddf3148d1d7c214d4bcedd480f06744c5a84"
88
}
99
}
1010
]

0 commit comments

Comments
 (0)