@toa.io/extensions.exposition 1.0.0-alpha.292 → 1.0.0-alpha.293

package/features/io.feature

@@ -1,204 +0,0 @@
-@security
-Feature: IO restrictions
-
-  Background:
-    Given the `pots` database contains:
-      | _id                              | title      | volume | temperature |
-      | 4c4759e6f9c74da989d64511df42d6f4 | First pot  | 100    | 80          |
-      | 99988d785d7d445cad45dbf8531f560b | Second pot | 200    | 30          |
-
-  Scenario: Output is omitted by default
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          GET: enumerate
-          /:id:
-            GET: observe
-      """
-    When the following request is received:
-      """
-      GET /pots/4c4759e6f9c74da989d64511df42d6f4/ HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-length: 0
-      """
-    When the following request is received:
-      """
-      GET /pots/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-length: 0
-      """
-
-  Scenario: Output is omitted by intention
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:id:
-          io:output: false
-          GET: observe
-      """
-    When the following request is received:
-      """
-      GET /pots/4c4759e6f9c74da989d64511df42d6f4/ HTTP/1.1
-      host: nex.toa.io
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-length: 0
-      """
-
-  Scenario: Output permissions
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          io:output: [id, volume]
-          GET: enumerate
-          /:id:
-            GET: observe
-      """
-    When the following request is received:
-      """
-      GET /pots/4c4759e6f9c74da989d64511df42d6f4/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-
-      id: 4c4759e6f9c74da989d64511df42d6f4
-      volume: 100
-      """
-    And the reply does not contain:
-      """
-      title:
-      temperature:
-      """
-    When the following request is received:
-      """
-      GET /pots/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
-
-      - id: 4c4759e6f9c74da989d64511df42d6f4
-        volume: 100
-      - id: 99988d785d7d445cad45dbf8531f560b
-        volume: 200
-      """
-    And the reply does not contain:
-      """
-      title:
-      temperature:
-      """
-
-  Scenario: Input is unrestricted by default
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          io:output: true
-          POST: create
-      """
-    When the following request is received:
-      """
-      POST /pots/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      content-type: application/yaml
-
-      title: Hello
-      volume: 1.5
-      temperature: 80
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-
-      title: Hello
-      volume: 1.5
-      temperature: 80
-      """
-
-  Scenario: Input permissions
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          io:input: [title, volume]
-          io:output: [id]
-          POST: create
-      """
-    When the following request is received:
-      """
-      POST /pots/ HTTP/1.1
-      host: nex.toa.io
-      accept: text/plain
-      content-type: application/yaml
-
-      title: Hello
-      volume: 1.5
-      temperature: 80
-      """
-    Then the following reply is sent:
-      """
-      400 Bad Request
-
-      Unexpected input: temperature
-      """
-    When the following request is received:
-      """
-      POST /pots/ HTTP/1.1
-      host: nex.toa.io
-      content-type: application/yaml
-
-      title: Hello
-      volume: 1.5
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-      """
-
-  Scenario: IO shortcuts
-    Given the `pots` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          input: [title, volume]
-          output: [id, title, volume]
-          POST: create
-      """
-    When the following request is received:
-      """
-      POST /pots/ HTTP/1.1
-      host: nex.toa.io
-      accept: application/yaml
-      content-type: application/yaml
-
-      title: Hello
-      volume: 1.5
-      """
-    Then the following reply is sent:
-      """
-      201 Created
-
-      id:
-      title: Hello
-      volume: 1.5
-      """

package/features/io.throttle.feature

@@ -1,166 +0,0 @@
-@timing
-Feature: Request throttling
-
-  Scenario: Throttle requests to a path
-    Given the `echo.beacon` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          io:throttle:
-            key: [path]
-            requests: 1
-            interval: 1
-          GET:
-            endpoint: hello
-      """
-    When the following request is received:
-      """
-      GET /echo/beacon/ HTTP/1.1
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """
-    When the following request is received:
-      """
-      GET /echo/beacon/ HTTP/1.1
-      """
-    # an emission is a second, which is what the budget takes to earn one back
-    Then the following reply is sent:
-      """
-      429 Too Many Requests
-      retry-after: 1
-      """
-    Then after 2 seconds
-    When the following request is received:
-      """
-      GET /echo/beacon/ HTTP/1.1
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """
-
-  Scenario: Throttle requests to a route, whichever path they came in on
-    Given the `echo.beacon` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          /:id:
-            io:throttle:
-              key: [route]
-              requests: 1
-              interval: 5
-            GET:
-              dev:stub:
-                hello: true
-      """
-    When the following request is received:
-      """
-      GET /echo/beacon/1/ HTTP/1.1
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """
-    # a different path of the same route, and the budget is already spent —
-    # keyed on `path` this would be 200
-    When the following request is received:
-      """
-      GET /echo/beacon/2/ HTTP/1.1
-      """
-    Then the following reply is sent:
-      """
-      429 Too Many Requests
-      """
-
-  Scenario: Throttle requests per route segment
-    Given the `echo.beacon` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          /:id:
-            io:throttle:
-              key:
-                - segment: id
-              requests: 1
-              interval: 5
-            GET:
-              dev:stub:
-                hello: true
-      """
-    When the following request is received:
-      """
-      GET /echo/beacon/1/ HTTP/1.1
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """
-    When the following request is received:
-      """
-      GET /echo/beacon/1/ HTTP/1.1
-      """
-    Then the following reply is sent:
-      """
-      429 Too Many Requests
-      """
-    # another segment value, another budget
-    When the following request is received:
-      """
-      GET /echo/beacon/2/ HTTP/1.1
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """
-
-  Scenario: Throttle requests per identity
-    Given the `echo.beacon` is running with the following manifest:
-      """yaml
-      exposition:
-        /:
-          auth:anyone: true
-          GET:
-            # declared after `auth:` on the node, and mandatory families run in
-            # their own order regardless: `auth` has to resolve the identity
-            # before `io` can key a quota on it
-            io:throttle:
-              key: [identity]
-              requests: 1
-              interval: 5
-            endpoint: hello
-      """
-    And transient identity alice
-    And transient identity bob
-    When the following request is received:
-      """
-      GET /echo/beacon/ HTTP/1.1
-      host: nex.toa.io
-      authorization: Token ${{ alice.token }}
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """
-    When the following request is received:
-      """
-      GET /echo/beacon/ HTTP/1.1
-      host: nex.toa.io
-      authorization: Token ${{ alice.token }}
-      """
-    Then the following reply is sent:
-      """
-      429 Too Many Requests
-      """
-    # bob's own budget, which requires auth to have resolved him before io keyed on him
-    When the following request is received:
-      """
-      GET /echo/beacon/ HTTP/1.1
-      host: nex.toa.io
-      authorization: Token ${{ bob.token }}
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      """