looprpc: additional_bindings for /v1/lsat/tokens

Provide backward compatibility for clients using this API endpoint.

Author: starius

looprpc/client.pb.gw.go

@@ -538,6 +538,29 @@
           "SwapClient"
         ]
       }
+    },
+    "/v1/lsat/tokens": {
+      "get": {
+        "summary": "loop: `listauth`\nGetL402Tokens returns all L402 tokens the daemon ever paid for.",
+        "operationId": "SwapClient_GetL402Tokens2",
+        "responses": {
+          "200": {
+            "description": "A successful response.",
+            "schema": {
+              "$ref": "#/definitions/looprpcTokensResponse"
+            }
+          },
+          "default": {
+            "description": "An unexpected error response.",
+            "schema": {
+              "$ref": "#/definitions/rpcStatus"
+            }
+          }
+        },
+        "tags": [
+          "SwapClient"
+        ]
+      }
     }
   },
   "definitions": {

looprpc/client.swagger.json

@@ -28,6 +28,8 @@ http:
       get: "/v1/loop/info"
     - selector: looprpc.SwapClient.GetL402Tokens
       get: "/v1/l402/tokens"
+      additional_bindings:
+        - get: "/v1/lsat/tokens"
     - selector: looprpc.SwapClient.GetLiquidityParams
       get: "/v1/liquidity/params"
     - selector: looprpc.SwapClient.SetLiquidityParams

looprpc/client.yaml

@@ -26,6 +26,8 @@ encouraged to change the options to new names if they have been changed locally.
 The path in looprpc "/v1/lsat/tokens" was renamed to "/v1/l402/tokens" and
 the corresponding method was renamed from `GetLsatTokens` to `GetL402Tokens`.
 Update `loop` and `loopd` simultaneously otherwise this RPC won't work.
+HTTP endpoint "/v1/l402/tokens" is now an additional binding for API
+"/v1/lsat/tokens", so it still works.
 
 #### Bug Fixes