Skip to content

Commit 0cc2ba0

Browse files
dsotirho-ucscdsotirho-ucsc
committed
[a] Remove the Retry-After header from 504 responses from API Gateway (#7469)
1 parent c52a4ed commit 0cc2ba0

File tree

6 files changed

+45
-62
lines changed

6 files changed

+45
-62
lines changed

‎lambdas/indexer/app.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@
5353
# changes and reset the minor version to zero. Otherwise, increment only
5454
# the minor version for backwards compatible changes. A backwards
5555
# compatible change is one that does not require updates to clients.
56-
'version': '3.3',
56+
'version': '3.4',
5757
'description': fd('''
5858
This is the internal API for Azul's indexer component.
5959
''')

‎lambdas/indexer/openapi.json‎

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22
"openapi": "3.0.1",
33
"info": {
44
"title": "azul-indexer-dev",
5-
"version": "3.3",
5+
"version": "3.4",
66
"description": "\nThis is the internal API for Azul's indexer component.\n\n\n## Contact us\n\nFor technical support please file an issue at\n[GitHub](https://github.com/DataBiosphere/azul/issues) or email\n`[email protected]`. To report a security concern or misconduct please email\n`[email protected]`.\n"
77
},
88
"paths": {
99
"/": {
1010
"get": {
1111
"responses": {
1212
"504": {
13-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
13+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
1414
},
1515
"301": {
1616
"description": "A redirect to the Swagger UI"
@@ -26,7 +26,7 @@
2626
"get": {
2727
"responses": {
2828
"504": {
29-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
29+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
3030
},
3131
"200": {
3232
"description": "The response body is an HTML page containing the Swagger UI"
@@ -42,7 +42,7 @@
4242
"get": {
4343
"responses": {
4444
"504": {
45-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
45+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
4646
},
4747
"200": {
4848
"description": "The response body is JavaScript used internally by the Swagger UI"
@@ -69,7 +69,7 @@
6969
"get": {
7070
"responses": {
7171
"504": {
72-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
72+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
7373
},
7474
"200": {
7575
"description": "The response body is the contents of the requested file"
@@ -88,7 +88,7 @@
8888
"get": {
8989
"responses": {
9090
"504": {
91-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
91+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
9292
},
9393
"200": {
9494
"description": "200 response",
@@ -151,7 +151,7 @@
151151
"get": {
152152
"responses": {
153153
"504": {
154-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
154+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
155155
},
156156
"200": {
157157
"description": "Version endpoint is reachable.",
@@ -196,7 +196,7 @@
196196
"get": {
197197
"responses": {
198198
"504": {
199-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
199+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
200200
},
201201
"200": {
202202
"description": "\nThe robots.txt resource according to\n[RFC9309](https://datatracker.ietf.org/doc/html/rfc9309)\n"
@@ -212,7 +212,7 @@
212212
"get": {
213213
"responses": {
214214
"504": {
215-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
215+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
216216
},
217217
"200": {
218218
"description": "\nThe checked resources\nare healthy.\n\nThe response consists of the following keys:\n\n* `other_lambdas` \nIndicates whether the companion REST API responds to HTTP requests.\n* `queues` \nReturns information about the SQS queues used by the indexer and the\nmirror.\n* `progress` \nThe number of Data Store bundles pending to be indexed and the number\nof index documents in need of updating.\n* `api_endpoints` \nIndicates whether important service API endpoints are operational.\n* `elasticsearch` \nIndicates whether the Elasticsearch cluster is responsive.\n* `up` \nindicates the overall result of the health check\n\n\nThe top-level `up` key of the response is\n`true`.\n\n\nAll of the nested `up` keys\nare `true`.\n",
@@ -314,7 +314,7 @@
314314
"get": {
315315
"responses": {
316316
"504": {
317-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
317+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
318318
},
319319
"200": {
320320
"description": "\nThe checked resources\nare healthy.\n\nThe response consists of the following keys:\n\n* `up` \nindicates the overall result of the health check\n\n\nThe top-level `up` key of the response is\n`true`.\n\n",
@@ -406,7 +406,7 @@
406406
"get": {
407407
"responses": {
408408
"504": {
409-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
409+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
410410
},
411411
"200": {
412412
"description": "\nThe checked resources\nare healthy.\n\nThe response consists of the following keys:\n\n* `elasticsearch` \nIndicates whether the Elasticsearch cluster is responsive.\n* `queues` \nReturns information about the SQS queues used by the indexer and the\nmirror.\n* `progress` \nThe number of Data Store bundles pending to be indexed and the number\nof index documents in need of updating.\n* `up` \nindicates the overall result of the health check\n\n\nThe top-level `up` key of the response is\n`true`.\n\n\nAll of the nested `up` keys\nare `true`.\n",
@@ -504,7 +504,7 @@
504504
"get": {
505505
"responses": {
506506
"504": {
507-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
507+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
508508
},
509509
"200": {
510510
"description": "\nThe checked resources\nare healthy.\n\nThe response consists of the following keys:\n\n* `elasticsearch` \nIndicates whether the Elasticsearch cluster is responsive.\n* `queues` \nReturns information about the SQS queues used by the indexer and the\nmirror.\n* `progress` \nThe number of Data Store bundles pending to be indexed and the number\nof index documents in need of updating.\n* `up` \nindicates the overall result of the health check\n\n\nThe top-level `up` key of the response is\n`true`.\n\n\nAll of the nested `up` keys\nare `true`.\n",
@@ -623,7 +623,7 @@
623623
"get": {
624624
"responses": {
625625
"504": {
626-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
626+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
627627
},
628628
"200": {
629629
"description": "\nThe checked resources\nare healthy.\n\nThe response consists of the following keys:\n\n* `other_lambdas` \nIndicates whether the companion REST API responds to HTTP requests.\n* `queues` \nReturns information about the SQS queues used by the indexer and the\nmirror.\n* `progress` \nThe number of Data Store bundles pending to be indexed and the number\nof index documents in need of updating.\n* `api_endpoints` \nIndicates whether important service API endpoints are operational.\n* `elasticsearch` \nIndicates whether the Elasticsearch cluster is responsive.\n* `up` \nindicates the overall result of the health check\n\n\nThe top-level `up` key of the response is\n`true`.\n\n\nAll of the nested `up` keys\nare `true`.\n",
@@ -725,7 +725,7 @@
725725
"post": {
726726
"responses": {
727727
"504": {
728-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
728+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
729729
},
730730
"200": {
731731
"description": "Notification was successfully queued for processing"
@@ -834,7 +834,7 @@
834834
"get": {
835835
"responses": {
836836
"504": {
837-
"description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n"
837+
"description": "Gateway timeout. The server did not respond in time. Please try again later."
838838
},
839839
"200": {
840840
"description": "Contents of the schema",

0 commit comments

Comments
 (0)