@toa.io/extensions.exposition 1.0.0-alpha.6 → 1.0.0-alpha.61

package/features/octets.feature

@@ -11,8 +11,6 @@ Feature: Octets directive family
           octets:store: ~
         GET:
           octets:list: ~
-        PUT:
-          octets:permute: ~
         /*:
           GET:
             octets:fetch: ~
@@ -33,12 +31,24 @@ Feature: Octets directive family
             POST:
               octets:store:
                 accept: image/*
+            /*:
+              GET:
+                octets:fetch: ~
+        /limit-1kb:
+          POST:
+            octets:store:
+              limit: 1kb
+        /limit-100kb:
+          POST:
+            octets:store:
+              limit: 100kb
       """
 
   Scenario: Basic storage operations
     When the stream of `lenna.ascii` is received with the following headers:
       """
       POST / HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       content-type: application/octet-stream
       """
@@ -54,6 +64,7 @@ Feature: Octets directive family
     When the following request is received:
       """
       GET /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
+      host: nex.toa.io
       """
     Then the stream equals to `lenna.ascii` is sent with the following headers:
       """
@@ -65,6 +76,7 @@ Feature: Octets directive family
     When the following request is received:
       """
       GET /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
+      host: nex.toa.io
       if-none-match: ${{ ETAG }}
       """
     Then the following reply is sent:
@@ -74,6 +86,7 @@ Feature: Octets directive family
     When the following request is received:
       """
       GET / HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       """
     Then the following reply is sent:
@@ -86,6 +99,7 @@ Feature: Octets directive family
     When the following request is received:
       """
       GET /10cf16b458f759e0d617f2f3d83599ff?foo=bar HTTP/1.1
+      host: nex.toa.io
       """
     Then the following reply is sent:
       """
@@ -94,6 +108,7 @@ Feature: Octets directive family
     When the following request is received:
       """
       DELETE /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
+      host: nex.toa.io
       """
     Then the following reply is sent:
       """
@@ -102,113 +117,122 @@ Feature: Octets directive family
     When the following request is received:
       """
       GET /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
+      host: nex.toa.io
       """
     Then the following reply is sent:
       """
       404 Not Found
       """
 
-  Scenario: Entries permutation
-    When the stream of `lenna.ascii` is received with the following headers:
+  Scenario: Media type control
+    When the stream of `lenna.png` is received with the following headers:
       """
-      POST / HTTP/1.1
-      accept: application/yaml
-      content-type: application/octet-stream
+      POST /media/jpeg-or-png/ HTTP/1.1
+      host: nex.toa.io
+      content-type: image/jpeg
       """
-    And the stream of `lenna.png` is received with the following headers:
+    Then the following reply is sent:
       """
-      POST / HTTP/1.1
-      accept: application/yaml
-      content-type: application/octet-stream
+      400 Bad Request
       """
-    When the following request is received:
+    When the stream of `lenna.png` is received with the following headers:
       """
-      GET / HTTP/1.1
-      accept: application/yaml
+      POST /media/jpeg/ HTTP/1.1
+      host: nex.toa.io
       """
     Then the following reply is sent:
       """
-      200 OK
-      content-type: application/yaml
-
-      - 10cf16b458f759e0d617f2f3d83599ff
-      - 814a0034f5549e957ee61360d87457e5
+      415 Unsupported Media Type
       """
-    When the following request is received:
+    When the stream of `lenna.png` is received with the following headers:
       """
-      PUT / HTTP/1.1
-      content-type: application/yaml
-
-      - 814a0034f5549e957ee61360d87457e5
-      - 10cf16b458f759e0d617f2f3d83599ff
+      POST /media/jpeg-or-png/ HTTP/1.1
+      host: nex.toa.io
       """
     Then the following reply is sent:
       """
-      204 No Content
+      201 Created
       """
-    When the following request is received:
+
+  Scenario: Size limit
+    When the stream of `albert.jpg` is received with the following headers:
       """
-      GET / HTTP/1.1
-      accept: application/yaml
+      POST /limit-1kb/ HTTP/1.1
+      host: nex.toa.io
+      content-type: image/jpeg
+      accept: text/plain
       """
     Then the following reply is sent:
       """
-      200 OK
-      content-type: application/yaml
+      413 Request Entity Too Large
 
-      - 814a0034f5549e957ee61360d87457e5
-      - 10cf16b458f759e0d617f2f3d83599ff
+      Size limit is 1kb
       """
 
-  Scenario: Media type control
-    When the stream of `lenna.png` is received with the following headers:
+    When the stream of `albert.jpg` is received with the following headers:
       """
-      POST /media/jpeg-or-png/ HTTP/1.1
+      POST /limit-100kb/ HTTP/1.1
+      host: nex.toa.io
       content-type: image/jpeg
       """
     Then the following reply is sent:
       """
-      400 Bad Request
+      201 Created
       """
-    When the stream of `lenna.png` is received with the following headers:
+
+  Scenario Outline: Detecting `<type>`
+    When the stream of `sample.<ext>` is received with the following headers:
       """
-      POST /media/jpeg/ HTTP/1.1
+      POST /media/images/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
       """
     Then the following reply is sent:
       """
-      415 Unsupported Media Type
+      201 Created
+
+      type: <type>
       """
-    When the stream of `lenna.png` is received with the following headers:
+    Examples:
+      | ext  | type       |
+      | jpeg | image/jpeg |
+      | jxl  | image/jxl  |
+      | gif  | image/gif  |
+      | heic | image/heic |
+      | avif | image/avif |
+      | webp | image/webp |
+
+  Scenario: Accepting `image/svg+xml`
+    When the stream of `sample.svg` is received with the following headers:
       """
-      POST /media/jpeg-or-png/ HTTP/1.1
+      POST /media/images/ HTTP/1.1
+      host: nex.toa.io
+      content-type: image/svg+xml
+      accept: application/yaml
       """
     Then the following reply is sent:
       """
       201 Created
+
+      type: image/svg+xml
       """
 
-  Scenario Outline: Receiving <format> images
-    When the stream of `sample.<format>` is received with the following headers:
+  Scenario: Rejection video/avi
+    When the stream of `sample.avi` is received with the following headers:
       """
       POST /media/images/ HTTP/1.1
+      host: nex.toa.io
       """
     Then the following reply is sent:
       """
-      201 Created
+      415 Unsupported Media Type
       """
-    Examples:
-      | format |
-      | jpeg   |
-      | jxl    |
-      | gif    |
-      | heic   |
-      | avif   |
-      | webp   |
 
   Scenario: Fetching non-existent BLOB
     When the following request is received:
       """
       GET /whatever HTTP/1.1
+      host: nex.toa.io
       """
     Then the following reply is sent:
       """
@@ -219,12 +243,14 @@ Feature: Octets directive family
     When the stream of `lenna.ascii` is received with the following headers:
       """
       POST / HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       content-type: application/octet-stream
       """
     And the following request is received:
       """
       GET /10cf16b458f759e0d617f2f3d83599ff/ HTTP/1.1
+      host: nex.toa.io
       accept: text/plain
       """
     Then the following reply is sent:
@@ -235,7 +261,7 @@ Feature: Octets directive family
       Trailing slash is redundant.
       """
 
-  Scenario: Original BLOLB is not accessible
+  Scenario: Original BLOB is not accessible
     Given the annotation:
       """yaml
       /:
@@ -253,6 +279,7 @@ Feature: Octets directive family
     When the stream of `lenna.ascii` is received with the following headers:
       """
       POST / HTTP/1.1
+      host: nex.toa.io
       """
     Then the following reply is sent:
       """
@@ -261,6 +288,7 @@ Feature: Octets directive family
     When the following request is received:
       """
       GET /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
+      host: nex.toa.io
       accept: text/plain
       """
     Then the following reply is sent:

package/features/octets.meta.feature

@@ -19,6 +19,7 @@ Feature: Octets `content-meta` header
     When the stream of `lenna.ascii` is received with the following headers:
       """
       POST /meta-header/ HTTP/1.1
+      host: nex.toa.io
       content-type: application/octet-stream
       content-meta: foo, bar=baz=1
       content-meta: baz=1
@@ -30,6 +31,7 @@ Feature: Octets `content-meta` header
     When the following request is received:
       """
       GET /meta-header/10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
+      host: nex.toa.io
       accept: application/vnd.toa.octets.entry+yaml
       """
     Then the following reply is sent:
@@ -56,6 +58,7 @@ Feature: Octets `content-meta` header
     When the following request is received:
       """
       OPTIONS / HTTP/1.1
+      host: nex.toa.io
       origin: https://example.com
       """
     Then the following reply is sent:

package/features/octets.workflows.feature

@@ -23,7 +23,8 @@ Feature: Octets storage workflows
     When the stream of `lenna.ascii` is received with the following headers:
       """
       POST / HTTP/1.1
-      accept: application/yaml
+      host: nex.toa.io
+      accept: application/yaml, multipart/yaml
       content-type: application/octet-stream
       """
     Then the following reply is sent:
@@ -32,23 +33,35 @@ Feature: Octets storage workflows
       content-type: multipart/yaml; boundary=cut
 
       --cut
+
       id: 10cf16b458f759e0d617f2f3d83599ff
       type: application/octet-stream
       size: 8169
       --cut
-      add-foo: null
+
+      step: add-foo
+      status: completed
       --cut
-      add-bar:
+
+      step: add-bar
+      output:
         bar: baz
+      status: completed
       --cut
-      add-baz: null
+
+      step: add-baz
+      status: completed
       --cut
-      diversify: null
+
+      step: diversify
+      output: hello
+      status: completed
       --cut--
       """
     When the following request is received:
       """
       GET /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
+      host: nex.toa.io
       accept: application/vnd.toa.octets.entry+yaml
       """
     Then the following reply is sent:
@@ -67,6 +80,7 @@ Feature: Octets storage workflows
     When the following request is received:
       """
       GET /10cf16b458f759e0d617f2f3d83599ff.hello.png HTTP/1.1
+      host: nex.toa.io
       """
     Then the stream equals to `lenna.png` is sent with the following headers:
       """
@@ -85,14 +99,15 @@ Feature: Octets storage workflows
         POST:
           octets:store:
             workflow:
-              add-foo: octets.tester.foo
-              add-bar: octets.tester.err
-              add-baz: octets.tester.baz
+              - add-foo: octets.tester.foo
+              - add-bar: octets.tester.err
+              - add-baz: octets.tester.baz
       """
     When the stream of `lenna.ascii` is received with the following headers:
       """
       POST / HTTP/1.1
-      accept: application/yaml
+      host: nex.toa.io
+      accept: application/yaml, multipart/yaml
       content-type: application/octet-stream
       """
     Then the following reply is sent:
@@ -105,12 +120,16 @@ Feature: Octets storage workflows
       type: application/octet-stream
       size: 8169
       --cut
-      add-foo: null
+
+      step: add-foo
+      status: completed
       --cut
+
+      step: add-bar
       error:
-        step: add-bar
         code: ERROR
         message: Something went wrong
+      status: completed
       --cut--
       """
 
@@ -134,6 +153,7 @@ Feature: Octets storage workflows
     When the stream of `lenna.ascii` is received with the following headers:
       """
       POST / HTTP/1.1
+      host: nex.toa.io
       content-type: application/octet-stream
       """
     Then the following reply is sent:
@@ -143,7 +163,8 @@ Feature: Octets storage workflows
     When the following request is received:
       """
       DELETE /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
-      accept: application/yaml
+      host: nex.toa.io
+      accept: application/yaml, multipart/yaml
       """
     Then the following reply is sent:
       """
@@ -151,12 +172,15 @@ Feature: Octets storage workflows
       content-type: multipart/yaml; boundary=cut
 
       --cut
-      echo: 10cf16b458f759e0d617f2f3d83599ff
+      step: echo
+      status: completed
+      output: 10cf16b458f759e0d617f2f3d83599ff
       --cut--
       """
     When the following request is received:
       """
       GET /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
+      host: nex.toa.io
       """
     Then the following reply is sent:
       """
@@ -183,6 +207,7 @@ Feature: Octets storage workflows
     When the stream of `lenna.ascii` is received with the following headers:
       """
       POST / HTTP/1.1
+      host: nex.toa.io
       content-type: application/octet-stream
       """
     Then the following reply is sent:
@@ -192,7 +217,8 @@ Feature: Octets storage workflows
     When the following request is received:
       """
       DELETE /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
-      accept: application/yaml
+      host: nex.toa.io
+      accept: application/yaml, multipart/yaml
       """
     Then the following reply is sent:
       """
@@ -200,8 +226,10 @@ Feature: Octets storage workflows
       content-type: multipart/yaml; boundary=cut
 
       --cut
+
+      step: err
+      status: completed
       error:
-        step: err
         code: ERROR
         message: Something went wrong
       --cut--
@@ -209,6 +237,7 @@ Feature: Octets storage workflows
     When the following request is received:
       """
       GET /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
+      host: nex.toa.io
       """
     Then the following reply is sent:
       """
@@ -231,7 +260,8 @@ Feature: Octets storage workflows
     When the stream of `lenna.ascii` is received with the following headers:
       """
       POST /hello/world/ HTTP/1.1
-      accept: application/yaml
+      host: nex.toa.io
+      accept: application/yaml, multipart/yaml
       content-type: application/octet-stream
       """
     Then the following reply is sent:
@@ -240,11 +270,53 @@ Feature: Octets storage workflows
       content-type: multipart/yaml; boundary=cut
 
       --cut
+
       id: 10cf16b458f759e0d617f2f3d83599ff
       type: application/octet-stream
       size: 8169
       --cut
-      concat: hello world
+
+      step: concat
+      status: completed
+      output: hello world
+      --cut--
+      """
+
+  Scenario: Passing authority to the workflow
+    Given the `octets.tester` is running
+    And the annotation:
+      """yaml
+      /:
+        /:a/:b:
+          auth:anonymous: true
+          octets:context: octets
+          POST:
+            octets:store:
+              workflow:
+                authority: octets.tester.authority
+      """
+    When the stream of `lenna.ascii` is received with the following headers:
+      """
+      POST /hello/world/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml, multipart/yaml
+      content-type: application/octet-stream
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      content-type: multipart/yaml; boundary=cut
+
+      --cut
+
+      id: 10cf16b458f759e0d617f2f3d83599ff
+      type: application/octet-stream
+      size: 8169
+      --cut
+
+      step: authority
+      status: completed
+      output: nex
       --cut--
       """
 
@@ -265,6 +337,7 @@ Feature: Octets storage workflows
     When the stream of `lenna.ascii` is received with the following headers:
       """
       POST / HTTP/1.1
+      host: nex.toa.io
       content-type: application/octet-stream
       """
     Then the following reply is sent:
@@ -274,7 +347,8 @@ Feature: Octets storage workflows
     When the following request is received:
       """
       DELETE /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
-      accept: application/yaml
+      host: nex.toa.io
+      accept: application/yaml, multipart/yaml
       """
     Then the following reply is sent:
       """
@@ -282,6 +356,152 @@ Feature: Octets storage workflows
       content-type: multipart/yaml; boundary=cut
 
       --cut
-      echo: 10cf16b458f759e0d617f2f3d83599ff
+
+      step: echo
+      status: completed
+      output: 10cf16b458f759e0d617f2f3d83599ff
+
+      --cut--
+      """
+
+  Scenario: Workflow with streaming response
+    Given the `octets.tester` is running
+    And the annotation:
+      """yaml
+      /:
+        auth:anonymous: true
+        octets:context: octets
+        POST:
+          octets:store:
+            workflow:
+              - foo: octets.tester.foo
+              - yield: octets.tester.yield
+      """
+    When the stream of `lenna.ascii` is received with the following headers:
+      """
+      POST / HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml, multipart/yaml
+      content-type: application/octet-stream
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      content-type: multipart/yaml; boundary=cut
+
+      --cut
+
+      id: 10cf16b458f759e0d617f2f3d83599ff
+      type: application/octet-stream
+
+      --cut
+
+      step: foo
+      status: completed
+
+      --cut
+
+      step: yield
+      output: hello
+
+      --cut
+
+      step: yield
+      output: world
+
+      --cut
+
+      step: yield
+      status: completed
+
+      --cut--
+      """
+
+  Scenario: Workflow with streaming response and an exception
+    Given the `octets.tester` is running
+    And the annotation:
+      """yaml
+      /:
+        auth:anonymous: true
+        octets:context: octets
+        POST:
+          octets:store:
+            workflow:
+              yield: octets.tester.yex
+      """
+    When the stream of `lenna.ascii` is received with the following headers:
+      """
+      POST / HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml, multipart/yaml
+      content-type: application/octet-stream
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      content-type: multipart/yaml; boundary=cut
+
+      --cut
+
+      id: 10cf16b458f759e0d617f2f3d83599ff
+      type: application/octet-stream
+
+      --cut
+
+      step: yield
+      output: hello
+
+      --cut
+
+      step: yield
+      output: world
+
+      --cut
+
+      step: yield
+      status: exception
+
+      --cut--
+      """
+
+  Scenario: Task workflow
+    Given the `octets.tester` is running
+    And the annotation:
+      """yaml
+      /:
+        auth:anonymous: true
+        octets:context: octets
+        POST:
+          octets:store:
+            workflow:
+              foo: task:octets.tester.foo
+        /*:
+          io:output: true
+          GET:
+            octets:fetch:
+              meta: true
+      """
+    When the stream of `lenna.ascii` is received with the following headers:
+      """
+      POST / HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml, multipart/yaml
+      content-type: application/octet-stream
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      content-type: multipart/yaml; boundary=cut
+
+      --cut
+
+      id: 10cf16b458f759e0d617f2f3d83599ff
+
+      --cut
+
+      step: foo
+      status: completed
+      output: null
+
       --cut--
       """