doc: testing lambdas

site/_includes/docs/_lambda-limitations.adoc

@@ -0,0 +1,23 @@
+== Limitations
+
+If the Identity Provider linking strategy is set to `Link Anonymously`, no lambdas will be used by FusionAuth. More information about the link:/docs/v1/tech/identity-providers/#linking-strategies[Identity Provider linking strategies is available here].
+
+The FusionAuth lambdas do not have full access to JavaScript modules and libraries. They also cannot import, require or load other libraries currently. These features might be added to our lambda support in the future.
+
+`console.log` and other `console` methods only take one argument; this differs from the `console` method available in web browsers.
+
+=== Lambda HTTP Connect Limitations
+
+include::docs/v1/tech/shared/_advanced-edition-blurb.adoc[]
+
+When using Lambda HTTP Connect to make HTTP requests, do not call a FusionAuth API which invokes the calling lambda, because it will fail. For example, in a JWT Populate lambda, do not invoke the Login API.
+
+Requests from a lambda require the lambda to use the GraalJS engine. HTTP requests will time out after two seconds.
+
+The `fetch` method in a lambda does not implement the https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API[entire `fetch` API] as implemented in a browser.
+The first argument to `fetch` must always be a string URL.
+Only the following options are supported:
+
+* `method`, which defaults to `GET`
+* `headers`, which defaults to null
+* `body`, which must be a string

site/_layouts/doc.liquid

@@ -438,6 +438,7 @@
                       <a href="#" class="sub-menu">Lambdas <i class="fal fa-chevron-{% if page.url contains "/lambdas/" %}up{% else %}down{% endif %} fa-fw"></i></a>
                       <ul>
                         <li {% if page.url == "/docs/v1/tech/lambdas/" %}class="active"{% endif %}><a href="/docs/v1/tech/lambdas/">Overview</a></li>
+                        <li {% if page.url == "/docs/v1/tech/lambdas/testing-lambdas.html" %}class="active"{% endif %}><a href="/docs/v1/tech/lambdas/testing-lambdas">Testing Lambdas</a></li>
                         {% comment %}Don't add a new lambda here. Add it to the site/_data/lambdas.yaml file and the menu item will be generated.{% endcomment %}
                         {% assign lambdas = site.data.lambdas | sort: 'displayName' %}
                         {% for lambda in lambdas %}

site/docs/v1/tech/lambdas/index.adoc

@@ -72,7 +72,7 @@ function populate(jwt, user, registration) {
       "Content-Type": "application/json"
     }
   });
-  
+
   if (response.status === 200) {
     // assuming successful response looks like:
     // {"status":"statusValue"}
@@ -95,7 +95,7 @@ function populate(jwt, user, registration) {
       "Authorization": "bf69486b-4733-4470-a592-f1bfce7af580"
     }
   });
-  
+
   if (response.status === 200) {
     // a successful response as defined in the Groups API
     var jsonResponse = JSON.parse(response.body);
@@ -137,7 +137,7 @@ headers: new Headers([
 ])
 ----
 
-==== Response 
+==== Response
 
 A response object will be returned. It will have the following fields:
 
@@ -221,33 +221,11 @@ In general, exceptions should not be used for flow control and should instead be
 
 To view exception details, enable debugging on the lambda via the [field]#Debug enabled# toggle in the administrative user interface or the API.
 
-== Limitations
-
-If the Identity Provider linking strategy is set to `Link Anonymously`, no lambdas will be used by FusionAuth. More information about the link:/docs/v1/tech/identity-providers/#linking-strategies[Identity Provider linking strategies is available here].
-
-The FusionAuth lambdas do not have full access to JavaScript modules and libraries. They also cannot import, require or load other libraries currently. These features might be added to our lambda support in the future.
-
-`console.log` and other `console` methods only take one argument; this differs from the `console` method available in web browsers.
-
-=== Lambda HTTP Connect Limitations
-
-include::docs/v1/tech/shared/_advanced-edition-blurb.adoc[]
-
-When using Lambda HTTP Connect to make HTTP requests, do not call a FusionAuth API which invokes the calling lambda, because it will fail. For example, in a JWT Populate lambda, do not invoke the Login API.
-
-Requests from a lambda require the lambda to use the GraalJS engine. HTTP requests will time out after two seconds.
-
-The `fetch` method in a lambda does not implement the https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API[entire `fetch` API] as implemented in a browser.
-The first argument to `fetch` must always be a string URL.
-Only the following options are supported:
-
-* `method`, which defaults to `GET`
-* `headers`, which defaults to null
-* `body`, which must be a string
+{% include docs/_lambda-limitations.adoc %}
 
 == Future Engines
 
-The Nashorn engine is being phased out of Java in favor of more robust and advanced engines. 
+The Nashorn engine is being phased out of Java in favor of more robust and advanced engines.
 
 [NOTE.note]
 ====