zuplo 6.69.9 → 6.69.11

package/docs/guides/user-based-backend-routing.mdx

@@ -77,8 +77,9 @@ export default async function policy(
 }
 ```
 
-When creating API keys in the Zuplo portal, set the metadata to include the
-environment:
+When creating API keys under
+[Services](https://portal.zuplo.com/+/account/project/services) in the Zuplo
+Portal, set the metadata to include the environment:
 
 ```json
 {

package/docs/policies/api-key-inbound/schema.json

@@ -46,6 +46,11 @@
               "x-show-example": false,
               "description": "The scheme used on the header."
             },
+            "bucketId": {
+              "type": "string",
+              "x-show-example": false,
+              "description": "The ID of the API Key service bucket. Preferred over bucketName. Defaults to the autogenerated bucket ID for your project."
+            },
             "bucketName": {
               "type": "string",
               "x-show-example": false,

package/docs/programmable-api/environment.mdx

@@ -313,12 +313,13 @@ context.log.info("Config loaded", {
 
 ## Setting Environment Variables
 
-Environment variables are set in the Zuplo Portal:
+Set environment variables in the Zuplo Portal:
 
-1. Navigate to your project
-2. Go to Settings → Environment Variables
-3. Add variables for each environment (production, preview, development)
-4. Variables are encrypted at rest and in transit
+1. Open the
+   [**Environments**](https://portal.zuplo.com/+/account/project/environments)
+   tab of your project.
+2. Select an environment and add variables under **Environment Variables**.
+3. Zuplo encrypts variables at rest and in transit.
 
 ## See Also
 

package/docs/programmable-api/zuplo-context.mdx

@@ -89,9 +89,9 @@ context.log.info({
 ### `log`
 
 A logger instance for debugging and monitoring. Logs appear in your log tail in
-the portal and in your integrated log solution (for example Datadog).
-Pre-production environments are typically set to **Info** log level, while
-production is set to **Error**.
+the [Zuplo Portal](https://portal.zuplo.com/+/account/project/) and in your
+integrated log solution (for example Datadog). Pre-production environments are
+typically set to **Info** log level, while production is set to **Error**.
 
 :::tip
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zuplo",
-  "version": "6.69.9",
+  "version": "6.69.11",
   "type": "module",
   "description": "The programmable API Gateway",
   "author": "Zuplo, Inc.",
@@ -19,9 +19,9 @@
     "zuplo": "zuplo.js"
   },
   "dependencies": {
-    "@zuplo/cli": "6.69.9",
-    "@zuplo/core": "6.69.9",
-    "@zuplo/runtime": "6.69.9",
+    "@zuplo/cli": "6.69.11",
+    "@zuplo/core": "6.69.11",
+    "@zuplo/runtime": "6.69.11",
     "@zuplo/test": "1.4.0"
   }
 }