@toa.io/extensions.exposition 1.0.0-alpha.9 → 1.0.0-alpha.91

package/features/octets.workflows.feature

@@ -8,22 +8,22 @@ Feature: Octets storage workflows
         auth:anonymous: true
         octets:context: octets
         POST:
-          octets:store:
+          octets:put:
             workflow:
               - add-foo: octets.tester.foo
                 add-bar: octets.tester.bar
               - add-baz: octets.tester.baz
-              - diversify: octets.tester.diversify
         /*:
           io:output: true
           GET:
-            octets:fetch:
+            octets:get:
               meta: true
       """
     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,47 +32,25 @@ 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
-      --cut
-      diversify: null
-      --cut--
-      """
-    When the following request is received:
-      """
-      GET /10cf16b458f759e0d617f2f3d83599ff HTTP/1.1
-      accept: application/vnd.toa.octets.entry+yaml
-      """
-    Then the following reply is sent:
-      """
-      200 OK
-      content-type: application/yaml
 
-      id: 10cf16b458f759e0d617f2f3d83599ff
-      type: application/octet-stream
-      size: 8169
-      meta:
-        foo: bar
-        bar: baz
-        baz: qux
-      """
-    When the following request is received:
-      """
-      GET /10cf16b458f759e0d617f2f3d83599ff.hello.png HTTP/1.1
-      """
-    Then the stream equals to `lenna.png` is sent with the following headers:
-      """
-      200 OK
-      content-type: image/png
-      content-length: 473831
+      step: add-baz
+      status: completed
+      --cut--
       """
 
   Scenario: Getting error when running workflow on `store`
@@ -83,16 +61,17 @@ Feature: Octets storage workflows
         auth:anonymous: true
         octets:context: octets
         POST:
-          octets:store:
+          octets:put:
             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 +84,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--
       """
 
@@ -122,10 +105,10 @@ Feature: Octets storage workflows
         auth:anonymous: true
         octets:context: octets
         POST:
-          octets:store: ~
+          octets:put: ~
         /*:
           GET:
-            octets:fetch: ~
+            octets:get: ~
           DELETE:
             octets:delete:
               workflow:
@@ -134,6 +117,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 +127,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 +136,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:
       """
@@ -171,10 +159,10 @@ Feature: Octets storage workflows
         auth:anonymous: true
         octets:context: octets
         POST:
-          octets:store: ~
+          octets:put: ~
         /*:
           GET:
-            octets:fetch: ~
+            octets:get: ~
           DELETE:
             octets:delete:
               workflow:
@@ -183,6 +171,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 +181,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 +190,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 +201,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:
       """
@@ -224,14 +217,53 @@ Feature: Octets storage workflows
           auth:anonymous: true
           octets:context: octets
           POST:
-            octets:store:
+            octets:put:
               workflow:
                 concat: octets.tester.concat
       """
     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:
+      """
+      201 Created
+      content-type: multipart/yaml; boundary=cut
+
+      --cut
+
+      id: 10cf16b458f759e0d617f2f3d83599ff
+      type: application/octet-stream
+      size: 8169
+      --cut
+
+      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:put:
+              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:
@@ -240,11 +272,15 @@ Feature: Octets storage workflows
       content-type: multipart/yaml; boundary=cut
 
       --cut
+
       id: 10cf16b458f759e0d617f2f3d83599ff
       type: application/octet-stream
       size: 8169
       --cut
-      concat: hello world
+
+      step: authority
+      status: completed
+      output: nex
       --cut--
       """
 
@@ -256,7 +292,7 @@ Feature: Octets storage workflows
         auth:anonymous: true
         octets:context: octets
         POST:
-          octets:store: ~
+          octets:put: ~
         /*:
           DELETE:
             octets:workflow:
@@ -265,6 +301,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 +311,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 +320,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:put:
+            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:put:
+            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:put:
+            workflow:
+              foo: task:octets.tester.foo
+        /*:
+          io:output: true
+          GET:
+            octets:get:
+              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--
       """

package/features/probes.feature

@@ -0,0 +1,14 @@
+Feature: Probes
+
+  Scenario: Startup probe
+    Given the Gateway is running
+    And after 1 second
+    When the following request is received:
+      """
+      GET /.ready HTTP/1.1
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      cache-control: no-store
+      """

package/features/{queries.feature → query.feature}

@@ -19,6 +19,7 @@ Feature: Queries
     When the following request is received:
       """
       GET /pots/pot/?id=99988d785d7d445cad45dbf8531f560b HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       """
     Then the following reply is sent:
@@ -42,6 +43,7 @@ Feature: Queries
     When the following request is received:
       """
       GET /pots/?criteria=volume<300&limit=10 HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       """
     Then the following reply is sent:
@@ -68,6 +70,7 @@ Feature: Queries
     When the following request is received:
       """
       GET /pots/?omit=1&limit=2 HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       """
     Then the following reply is sent:
@@ -94,6 +97,7 @@ Feature: Queries
     When the following request is received:
       """
       GET /pots/?sort=volume:desc&limit=2 HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       """
     Then the following reply is sent:
@@ -109,7 +113,7 @@ Feature: Queries
         volume: 300
       """
 
-  Scenario: Request to a route with a path variable
+  Scenario: Request to a route with path variable
     Given the `pots` is running with the following manifest:
       """yaml
       exposition:
@@ -120,6 +124,7 @@ Feature: Queries
     When the following request is received:
       """
       GET /pots/99988d785d7d445cad45dbf8531f560b/ HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       """
     Then the following reply is sent:
@@ -132,6 +137,37 @@ Feature: Queries
       volume: 200
       """
 
+  Scenario: Request to a route with path variable using OR operator
+    Given the `pots` is running with the following manifest:
+      """yaml
+      exposition:
+        /:volume:
+          io:output: true
+          GET:
+            query:
+              criteria: ',volume==100'
+            endpoint: enumerate
+      """
+    When the following request is received:
+      """
+      GET /pots/200/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      content-type: application/yaml
+
+      - id: 4c4759e6f9c74da989d64511df42d6f4
+        title: First pot
+        volume: 100
+        temperature: 80
+      - id: 99988d785d7d445cad45dbf8531f560b
+        title: Second pot
+        volume: 200
+      """
+
   Scenario: Request to a route with predefined criteria
     Given the `pots` is running with the following manifest:
       """yaml
@@ -146,6 +182,7 @@ Feature: Queries
     When the following request is received:
       """
       GET /pots/big/ HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       """
     Then the following reply is sent:
@@ -161,7 +198,7 @@ Feature: Queries
         volume: 400
       """
 
-  Scenario: Request to a route with combined criteria
+  Scenario: Request to a route with open criteria
     Given the `pots` is running with the following manifest:
       """yaml
       exposition:
@@ -175,6 +212,7 @@ Feature: Queries
     When the following request is received:
       """
       GET /pots/big/?criteria=temperature>50 HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       """
     Then the following reply is sent:
@@ -204,6 +242,7 @@ Feature: Queries
     When the following request is received:
       """
       GET /pots/hottest2/ HTTP/1.1
+      host: nex.toa.io
       accept: application/yaml
       """
     Then the following reply is sent:
@@ -220,3 +259,39 @@ Feature: Queries
         volume: 100
         temperature: 80
       """
+
+  Scenario: Query parameters
+    Given the `echo` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          GET:
+            io:output: true
+            query:
+              parameters: [name]
+            endpoint: compute
+      """
+    When the following request is received:
+      """
+      GET /echo/?name=John HTTP/1.1
+      host: nex.toa.io
+      accept: text/plain
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+
+      Hello John
+      """
+    When the following request is received:
+      """
+      GET /echo/?foo=bar HTTP/1.1
+      host: nex.toa.io
+      accept: text/plain
+      """
+    Then the following reply is sent:
+      """
+      400 Bad Request
+
+      Query parameter 'foo' is not allowed
+      """

package/features/realtime.feature

@@ -0,0 +1,34 @@
+Feature: Realtime events
+
+  Background:
+    Given the Realtime is running with the following annotation:
+      """yaml
+      users.properties.sync: id
+      """
+    And the identity Bob is consuming realtime events
+
+  Scenario: Getting realtime events
+    Given the `users.properties` is running with the following manifest:
+      """yaml
+      exposition:
+        /:id:
+          anonymous: true
+          io:output: false
+          PATCH: transit
+      """
+    When the following request is received:
+      """
+      PATCH /users/properties/${{ Bob.id }}/ HTTP/1.1
+      host: nex.toa.io
+      content-type: application/yaml
+
+      newbie: false
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      """
+    And the following event `users.properties.sync` is received by Bob:
+      """yaml
+      newbie: false
+      """