Release v0.4.4

Author: arbourd

atmo/release/version.go

@@ -1,4 +1,4 @@
 package release
 
 // AtmoDotVersion represents the dot version for atmo
-var AtmoDotVersion = "0.4.3"
+var AtmoDotVersion = "0.4.4"

changelogs/v0.4.4.md

@@ -0,0 +1 @@
+Atmo Beta-4.4 updates Reactr to Beta-15.1 and adds OpenTelemetry to Atmo Proxy.

docs/concepts/the-directive.md

@@ -7,18 +7,18 @@ Here's an example Directive:
 ```yaml
 identifier: com.suborbital.guide
 appVersion: v0.0.1
-atmoVersion: v0.4.3
+atmoVersion: v0.4.4
 
 handlers:
   - type: request
     resource: /hello
     method: POST
     steps:
       - group:
-        - fn: modify-url
-        - fn: helloworld-rs
-          onErr:
-            any: continue
+          - fn: modify-url
+          - fn: helloworld-rs
+            onErr:
+              any: continue
 
       - fn: fetch
 
@@ -38,4 +38,3 @@ handlers:
 This directive encapsulates all of the logic for your application. It describes three endpoints and the logic needed to handle them. Each handler describes a set of `steps` that composes a series of Runnables to handle the request.
 
 Atmo uses the Directive to build your application and run it automatically, without any need to write boilerplate yourself.
-

docs/usage/creating-handlers.md

@@ -13,17 +13,17 @@ Each handler tells Atmo how to handle a **resource.** A resource is an input tha
 ```yaml
 identifier: com.suborbital.test
 appVersion: v0.0.1
-atmoVersion: v0.4.3
+atmoVersion: v0.4.4
 
 handlers:
   - type: request
     resource: /hello
     method: POST
     steps:
       - group:
-        - fn: modify-url
-        - fn: helloworld-rs
-          as: hello
+          - fn: modify-url
+          - fn: helloworld-rs
+            as: hello
       - fn: fetch-test
         with:
           url: modify-url
@@ -38,13 +38,14 @@ The second step shown above is a single `fn` , which calls a Runnable that uses
 
 The output of the final function in a handler is used as the response data for the request, by default. If you wish to use the output from a different function, you can include the `response` option in your handler, listing the name of the function to use as a response. If the final step is a group, then the `response` clause must be included.
 
-For example: 
+For example:
+
 ```yaml
 steps:
   - group:
-    - fn: modify-url
-    - fn: helloworld-rs
-      as: hello
+      - fn: modify-url
+      - fn: helloworld-rs
+        as: hello
   - fn: fetch-test
     with:
       url: modify-url
@@ -55,4 +56,3 @@ response: hello
 Your application can contain as many handlers as needed, and functions can be re-used among many handlers. Each Runnable in your project can be called by its name. The `subo` tool will validate your directive to ensure it is not calling any Runnables that don't exist in your project.
 
 The `as` and `with` clauses shown above will be discussed [next](managing-state.md).
-

example-project/Directive.yaml

@@ -1,6 +1,6 @@
 identifier: com.suborbital.test
 appVersion: v0.0.1
-atmoVersion: v0.4.3
+atmoVersion: v0.4.4
 
 # uncomment to try out connections!
 connections: