Skip to content

Commit

Permalink
docs: [google-cloud-servicehealth] update proto comments (#12320)
Browse files Browse the repository at this point in the history
- [ ] Regenerate this pull request now.

PiperOrigin-RevId: 607453590

Source-Link:
googleapis/googleapis@f65b9f2

Source-Link:
googleapis/googleapis-gen@31d0d15
Copy-Tag:
eyJwIjoicGFja2FnZXMvZ29vZ2xlLWNsb3VkLXNlcnZpY2VoZWFsdGgvLk93bEJvdC55YW1sIiwiaCI6IjMxZDBkMTVhY2ZlMzEyMDQ2MjdmNzk3ZmM3ZGY2Nzk0YTVmYmUwYzAifQ==

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
  • Loading branch information
gcf-owl-bot[bot] and gcf-owl-bot[bot] committed Feb 16, 2024
1 parent 20cd51c commit db4e692
Showing 1 changed file with 26 additions and 12 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -213,13 +213,20 @@ class DetailedState(proto.Enum):
updates will be published to the parent only. The
``parent_event`` field contains the name of the parent.
AUTO_CLOSED (9):
The incident was automatically closed because
the issues couldn’t be confirmed or is no longer
impacting Google Cloud Products and/or
Locations.
The incident was automatically closed because of the
following reasons:
- The impact of the incident could not be confirmed.
- The incident was intermittent or resolved itself.
The incident does not have a resolution because no action or
investigation happened. If it is intermittent, the incident
may reopen.
FALSE_POSITIVE (10):
The incident was verified as non-impactful.
No further action required.
Upon investigation, Google engineers
concluded that the incident is not affecting a
Google Cloud product. This state can change if
the incident is reviewed again.
"""
DETAILED_STATE_UNSPECIFIED = 0
EMERGING = 1
Expand Down Expand Up @@ -467,13 +474,20 @@ class DetailedState(proto.Enum):
updates will be published to the parent only. The
``parent_event`` contains the name of the parent.
AUTO_CLOSED (9):
The incident was automatically closed because
the issues couldn’t be confirmed or is no longer
impacting Google Cloud Products and/or
Locations.
The incident was automatically closed because of the
following reasons:
- The impact of the incident could not be confirmed.
- The incident was intermittent or resolved itself.
The incident does not have a resolution because no action or
investigation happened. If it is intermittent, the incident
may reopen.
FALSE_POSITIVE (10):
The incident was verified as non-impactful.
No further action required.
Upon investigation, Google engineers
concluded that the incident is not affecting a
Google Cloud product. This state can change if
the incident is reviewed again.
"""
DETAILED_STATE_UNSPECIFIED = 0
EMERGING = 1
Expand Down

0 comments on commit db4e692

Please sign in to comment.