Retry Policy converts any input Duration to milliseconds

[bigdefect]

Description

We've identified a bug in Retry Policy (#7) in the preview channel API. The duration input into the api gets converted to milliseconds regardless of the input value. The duration itself and the resulting behavior is the same, but it is stored and returned as milliseconds. We're working on fixing the API to persist and return the same value as was put in.

e.g. With an input of:

{
  "virtualRouterName": "my-router",
  "routeName": "my-route",
  "spec": {
      ...
      "retryPolicy" : {
        "maxRetries" : 4,
        "perRetryTimeout" : {
          "unit" : "s",
          "value" : 2
        },
        "httpRetryEvents" : [
          "server-error"
        ]
      }
    }
  }
}

The output will be:

{
  "virtualRouterName": "my-router",
  "routeName": "my-route",
  "spec": {
      ...
      "retryPolicy" : {
        "maxRetries" : 4,
        "perRetryTimeout" : {
          "unit" : "ms",
          "value" : 2000
        },
        "httpRetryEvents" : [
          "server-error"
        ]
      }
    }
  }
}

Workaround

Until the behavior is corrected, you can choose to exclusively use ms durations.

[bigdefect]

The fix for this has been deployed to all production regions. If you experience any issues, feel free to open this back up.