Release 3.34.3 documentation

doc/config/_default/config.toml

@@ -23,7 +23,7 @@ pygmentsUseClasses = true
   github_repository = "https://github.com/TheThingsIndustries/lorawan-stack-docs"
   github_repository_edit = "https://github.com/TheThingsIndustries/lorawan-stack-docs/blob/master/doc/content"
   tts_github_repository = "https://github.com/TheThingsNetwork/lorawan-stack"
-  version = "3.34.2"
+  version = "3.34.3"
 
 [markup]
   [markup.goldmark]

doc/content/enterprise/aws/ecs/changelog/index.md

@@ -2,11 +2,16 @@
 title: "Template Changelog"
 aliases: [/getting-started/aws/ecs/changelog]
 ---
+
 # Upgrading
 
 All meaningful changes to templates are documented in this file.
 
-## Unreleased
+## 3.34.3
+
+### 5-1-ecs-cluster
+
+- Fix `AWSRegionToAMI` arm64 mappings.
 
 ## 3.34.2
 
@@ -528,7 +533,7 @@ All meaningful changes to templates are documented in this file.
 
 ## 3.23.0
 
-For mTLS termination, check the upgrading guide at https://thethingsindustries.com/docs/getting-started/aws/ecs/mutual-tls/.
+For mTLS termination, check the upgrading guide at <https://thethingsindustries.com/docs/getting-started/aws/ecs/mutual-tls/>.
 
 ## `1-2-bastion`
 
@@ -842,7 +847,7 @@ Add versioning to S3 buckets. Versioning is enabled by default.
 
 ### `3-2-load-balancer-rules`
 
-- The `InteropEnabled` parameter has different values. Deployments that used value `false` should now choose `disabled`. Deployments that used value `true` should now choose `mutual-authentication`. `server-only-authentication` is a new option, please refer to documentation: https://www.thethingsindustries.com/docs/getting-started/aws/ecs/interop/.
+- The `InteropEnabled` parameter has different values. Deployments that used value `false` should now choose `disabled`. Deployments that used value `true` should now choose `mutual-authentication`. `server-only-authentication` is a new option, please refer to documentation: <https://www.thethingsindustries.com/docs/getting-started/aws/ecs/interop/>.
 
 ### `5-3a-ecs-is-service`
 
@@ -1007,7 +1012,7 @@ Add versioning to S3 buckets. Versioning is enabled by default.
 ### `2-5-db-timescale`
 
 - Created a hosted zone for internal use.
-- This template has been reworked so that updates are now possible. Before updating make a backup of the volume. For more information, please refer to the documentation at https://www.thethingsindustries.com/docs/getting-started/aws/ecs/updating/#2-5-db-timescale.
+- This template has been reworked so that updates are now possible. Before updating make a backup of the volume. For more information, please refer to the documentation at <https://www.thethingsindustries.com/docs/getting-started/aws/ecs/updating/#2-5-db-timescale>.
 - Added `EBSKmsKeyId` parameter to choose EBS volume encryption key. From now on, EBS volumes are encrypted. Previously only data volume would be encrypted using the default key. Encrypting boot drive does not significantly increase security, and is mainly targeted towards compliance with regulations. If you wish to encrypt your boot drive, please:
   1. Change the `ApplicationServerStorageEnabled` parameter in `5-2-ocs-ops` and `5-4-ecs-services` to `false`.
   2. Create a snapshot of the TimescaleDB EBS volume.

doc/content/whats-new/3.34.3.md

@@ -0,0 +1,21 @@
+---
+date: 2025-10-16T05:25:01Z
+title: "3.34.3"
+featured:
+  {
+    added: ["Parsers for newly added normalized payload fields"],
+    changed: [],
+    fixed:
+      [
+        "ADR respects the MAC settings `adr.mode.dynamic.min-data-rate-index` and `adr.mode.dynamic.max-data-rate-index` values",
+      ],
+  }
+---
+
+### Added
+
+- Parsers for newly added normalized payload fields.
+
+### Fixed
+
+- ADR respects the MAC settings `adr.mode.dynamic.min-data-rate-index` and `adr.mode.dynamic.max-data-rate-index` values

doc/data/api/tts.swagger.json

@@ -8,7 +8,7 @@
   "swagger": "2.0",
   "info": {
     "title": "The Things Stack for LoRaWAN® OpenAPI 2.0 Reference",
-    "version": "3.34.2"
+    "version": "3.34.3"
   },
   "paths": {
     "/alerts/notifications/profiles": {
@@ -553927,54 +553927,7 @@
           "format": "date-time"
         },
         "last_failed_attempt_details": {
-          "description": "Error details that are communicated over gRPC (and HTTP) APIs.\nThe messages (for translation) are stored as \"error:\u003cnamespace\u003e:\u003cname\u003e\".",
-          "type": "object",
-          "properties": {
-            "attributes": {
-              "description": "Attributes that should be filled into the message format. Any extra attributes\ncan be displayed as error details.",
-              "type": "object"
-            },
-            "cause": {
-              "description": "The error that caused this error.",
-              "$ref": "#/definitions/v3ErrorDetails"
-            },
-            "code": {
-              "description": "The status code of the error.",
-              "type": "integer",
-              "format": "int64"
-            },
-            "correlation_id": {
-              "description": "The correlation ID of the error can be used to correlate the error to stack\ntraces the network may (or may not) store about recent errors.",
-              "type": "string"
-            },
-            "details": {
-              "description": "The details of the error.",
-              "type": "array",
-              "items": {
-                "description": "`Any` contains an arbitrary serialized protocol buffer message along with a\nURL that describes the type of the serialized message.\n\nProtobuf library provides support to pack/unpack Any values in the form\nof utility functions or additional generated methods of the Any type.\n\nExample 1: Pack and unpack a message in C++.\n\n    Foo foo = ...;\n    Any any;\n    any.PackFrom(foo);\n    ...\n    if (any.UnpackTo(\u0026foo)) {\n      ...\n    }\n\nExample 2: Pack and unpack a message in Java.\n\n    Foo foo = ...;\n    Any any = Any.pack(foo);\n    ...\n    if (any.is(Foo.class)) {\n      foo = any.unpack(Foo.class);\n    }\n    // or ...\n    if (any.isSameTypeAs(Foo.getDefaultInstance())) {\n      foo = any.unpack(Foo.getDefaultInstance());\n    }\n\n Example 3: Pack and unpack a message in Python.\n\n    foo = Foo(...)\n    any = Any()\n    any.Pack(foo)\n    ...\n    if any.Is(Foo.DESCRIPTOR):\n      any.Unpack(foo)\n      ...\n\n Example 4: Pack and unpack a message in Go\n\n     foo := \u0026pb.Foo{...}\n     any, err := anypb.New(foo)\n     if err != nil {\n       ...\n     }\n     ...\n     foo := \u0026pb.Foo{}\n     if err := any.UnmarshalTo(foo); err != nil {\n       ...\n     }\n\nThe pack methods provided by protobuf library will by default use\n'type.googleapis.com/full.type.name' as the type URL and the unpack\nmethods only use the fully qualified type name after the last '/'\nin the type URL, for example \"foo.bar.com/x/y.z\" will yield type\nname \"y.z\".\n\nJSON\n====\nThe JSON representation of an `Any` value uses the regular\nrepresentation of the deserialized, embedded message, with an\nadditional field `@type` which contains the type URL. Example:\n\n    package google.profile;\n    message Person {\n      string first_name = 1;\n      string last_name = 2;\n    }\n\n    {\n      \"@type\": \"type.googleapis.com/google.profile.Person\",\n      \"firstName\": \u003cstring\u003e,\n      \"lastName\": \u003cstring\u003e\n    }\n\nIf the embedded message type is well-known and has a custom JSON\nrepresentation, that representation will be embedded adding a field\n`value` which holds the custom JSON in addition to the `@type`\nfield. Example (for message [google.protobuf.Duration][]):\n\n    {\n      \"@type\": \"type.googleapis.com/google.protobuf.Duration\",\n      \"value\": \"1.212s\"\n    }",
-                "type": "object",
-                "properties": {
-                  "@type": {
-                    "description": "A URL/resource name that uniquely identifies the type of the serialized\nprotocol buffer message. This string must contain at least\none \"/\" character. The last segment of the URL's path must represent\nthe fully qualified name of the type (as in\n`path/google.protobuf.Duration`). The name should be in a canonical form\n(e.g., leading \".\" is not accepted).\n\nIn practice, teams usually precompile into the binary all types that they\nexpect it to use in the context of Any. However, for URLs which use the\nscheme `http`, `https`, or no scheme, one can optionally set up a type\nserver that maps type URLs to message definitions as follows:\n\n* If no scheme is provided, `https` is assumed.\n* An HTTP GET on the URL must yield a [google.protobuf.Type][]\n  value in binary format, or produce an error.\n* Applications are allowed to cache lookup results based on the\n  URL, or have them precompiled into a binary to avoid any\n  lookup. Therefore, binary compatibility needs to be preserved\n  on changes to types. (Use versioned type names to manage\n  breaking changes.)\n\nNote: this functionality is not currently available in the official\nprotobuf release, and it is not used for type URLs beginning with\ntype.googleapis.com. As of May 2023, there are no widely used type server\nimplementations and no plans to implement one.\n\nSchemes other than `http`, `https` (or the empty scheme) might be\nused with implementation specific semantics.",
-                    "type": "string"
-                  }
-                },
-                "additionalProperties": {}
-              }
-            },
-            "message_format": {
-              "description": "The default (fallback) message format that should be used for the error.\nThis is also used if the client does not have a translation for the error.",
-              "type": "string"
-            },
-            "name": {
-              "description": "Name of the error.",
-              "type": "string"
-            },
-            "namespace": {
-              "description": "Namespace of the error (typically the package name in The Things Stack).",
-              "type": "string"
-            }
-          }
+          "$ref": "#/definitions/v3ErrorDetails"
         }
       }
     },