From 5445e094d993fb7c9e417263c69dd12409c120fe Mon Sep 17 00:00:00 2001
From: Christopher Atkins <catkins@misoenergy.org>
Date: Thu, 14 Nov 2024 13:31:36 +0000
Subject: [PATCH] choosing one Retry-After type to eliminate ambiguity and fix
 redoc parser warnings

---
 docs/_spec/openapi-split.yaml | 20 ++++++--------------
 1 file changed, 6 insertions(+), 14 deletions(-)

diff --git a/docs/_spec/openapi-split.yaml b/docs/_spec/openapi-split.yaml
index f1793be..c0e6271 100644
--- a/docs/_spec/openapi-split.yaml
+++ b/docs/_spec/openapi-split.yaml
@@ -436,20 +436,12 @@ components:
         maximum: 1000
     Retry-After:
       schema:
-        type: object
-        oneOf:
-          - type: integer
-            format: int32
-            minimum: 0
-            maximum: 60
-            example: 60
-            description: The seconds to delay after the response is received.
-          # TODO: the HTTP spec allows for this but we probably should not support it
-          - type: string
-            pattern: "^[A-Z][a-z]{2}, \\d{2} [A-Z][a-z]{2} \\d{4} \\d{2}:\\d{2}:\\d{2} GMT$"
-            maxLength: 30
-            example: 'Wed, 21 Oct 2022 07:28:00 GMT'
-            description: A date after which to retry.
+        type: integer
+        format: int32
+        minimum: 0
+        maximum: 60
+        example: 60
+        description: The seconds to delay after the response is received.
   securitySchemes:
     oauth2-primary-flow:
       type: oauth2