Update patch set 1
Patch Set 1: (1 comment) Patch-set: 1 Reviewer: Gerrit User 6926 <6926@4a232e18-c5a9-48ee-94c0-e04e7cca6543>
This commit is contained in:
parent
6754a0e43c
commit
f2ce566b99
|
@ -128,6 +128,30 @@
|
|||
"revId": "c70c9249249504b39cde5ea95caa86f2df921acb",
|
||||
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
|
||||
"unresolved": true
|
||||
},
|
||||
{
|
||||
"key": {
|
||||
"uuid": "4df053b1_4b1001fa",
|
||||
"filename": "specs/xena/healthcheck-new-way.rst",
|
||||
"patchSetId": 1
|
||||
},
|
||||
"lineNbr": 46,
|
||||
"author": {
|
||||
"id": 6926
|
||||
},
|
||||
"writtenOn": "2021-08-05T13:15:58Z",
|
||||
"side": 1,
|
||||
"message": "\u003e If we want to actually check/verify if an API is working, that API has to test its own dependencies\n\nRight, but the healthcheck status of a container is binary - it is either healthy or not. How would you be sure what that\u0027s the API service is not functional in your container or some of the external dependencies? There is no way to be sure.",
|
||||
"parentUuid": "570af206_c2aa90f7",
|
||||
"range": {
|
||||
"startLine": 45,
|
||||
"startChar": 0,
|
||||
"endLine": 46,
|
||||
"endChar": 63
|
||||
},
|
||||
"revId": "c70c9249249504b39cde5ea95caa86f2df921acb",
|
||||
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
|
||||
"unresolved": true
|
||||
}
|
||||
]
|
||||
}
|
Loading…
Reference in New Issue