Deploying to gh-pages from @ 46a5a83 🚀

TheThingsIndustries · Dec 10, 2024 · 9c46289 · 9c46289
1 parent 3966b77
commit 9c46289
Show file tree

Hide file tree

Showing 86 changed files with 736 additions and 286 deletions.
diff --git a/api/reference/http/messages/index.html b/api/reference/http/messages/index.html
diff --git a/api/reference/http/routes/index.html b/api/reference/http/routes/index.html
@@ -177,7 +177,7 @@ <h1 class="title is-size-2">Routes</h1>
 <div>
   <div class="api-page-header">
     <h3>The Things Stack HTTP (REST) API Reference</h3>
-    <p>Version: <code> 3.32.2 </code></p>
+    <p>Version: <code> 3.32.3 </code></p>
   </div>
   <div class="api-tags-table">
     <table>
@@ -123057,54 +123057,7 @@ <h5 class="api-item-content-section-headers">Request Body</h5>
                 "type": "string"
               },
               "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\".",
-                "properties": {
-                  "attributes": {
-                    "description": "Attributes that should be filled into the message format. Any extra attributes\ncan be displayed as error details.",
-                    "type": "object"
-                  },
-                  "cause": {
-                    "$ref": "#/definitions/v3ErrorDetails",
-                    "description": "The error that caused this error."
-                  },
-                  "code": {
-                    "description": "The status code of the error.",
-                    "format": "int64",
-                    "type": "integer"
-                  },
-                  "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.",
-                    "items": {
-                      "additionalProperties": {},
-                      "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    }",
-                      "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"
-                        }
-                      },
-                      "type": "object"
-                    },
-                    "type": "array"
-                  },
-                  "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"
-                  }
-                },
-                "type": "object"
+                "$ref": "#/definitions/v3ErrorDetails"
               }
             },
             "type": "object"
@@ -123685,54 +123638,7 @@ <h5 class="api-item-content-section-headers">Request Body</h5>
                 "type": "string"
               },
               "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\".",
-                "properties": {
-                  "attributes": {
-                    "description": "Attributes that should be filled into the message format. Any extra attributes\ncan be displayed as error details.",
-                    "type": "object"
-                  },
-                  "cause": {
-                    "$ref": "#/definitions/v3ErrorDetails",
-                    "description": "The error that caused this error."
-                  },
-                  "code": {
-                    "description": "The status code of the error.",
-                    "format": "int64",
-                    "type": "integer"
-                  },
-                  "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.",
-                    "items": {
-                      "additionalProperties": {},
-                      "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    }",
-                      "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"
-                        }
-                      },
-                      "type": "object"
-                    },
-                    "type": "array"
-                  },
-                  "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"
-                  }
-                },
-                "type": "object"
+                "$ref": "#/definitions/v3ErrorDetails"
               }
             },
             "type": "object"

diff --git a/index.html b/index.html
@@ -89,7 +89,7 @@
 
     <div class="item-5 md:item-12 grid sm:mb-ls-l">
       <div class="mb-ls-l item-12 md:item-6 sm:item-8 xs:item-12">
-        <p class="bg-tts-primary-main d-inline-block c-white ttui-body p-sides-cs-s pt-cs-xxs pb-cs-xxs br-xxl mb-cs-m">v3.32.2</p>
+        <p class="bg-tts-primary-main d-inline-block c-white ttui-body p-sides-cs-s pt-cs-xxs pb-cs-xxs br-xxl mb-cs-m">v3.32.3</p>
         <h1 class="mb-cs-s c-interactive-03">The Things Stack Documentation</h1>
         <p class="ttui-body fs-l mb-cs-xl">The Things Stack is a robust, yet flexible LoRaWAN® Network Server that caters to the needs of demanding LoRaWAN deployments, from covering the essentials to advanced security configurations and device life cycle management.</p>
       </div>
@@ -250,22 +250,14 @@ <h1 class="mb-cs-s c-interactive-03">The Things Stack Documentation</h1>
 <section class="section-whats-new ttui-container grid pt-ls-xl pb-ls-xl">
 
 <div class="container-whats-new item-12 br-l p-ls-s">
-  <p class="ttui-body fs-xl fw-bolder mb-cs-xl c-text-01">What's new in v3.32.2</p>
+  <p class="ttui-body fs-xl fw-bolder mb-cs-xl c-text-01">What's new in v3.32.3</p>
   <div class="grid mb-cs-xl">
 
 
 
-
-    <a href="https://www.thethingsindustries.com/docs/whats-new/3.32.2/" class="item-whats-new b-line-01 item-6 md:item-12 br-l p-cs-l grid">
-      <div class="item-10">
-        <p class="bg-tts-primary-main d-inline-block c-white ttui-body fs-s pl-cs-m pr-cs-m pt-cs-xxs pb-cs-xxs br-xxl mb-cs-m">Fixed</p>
-        <p class="ttui-body fs-m">Potential leak of end devices of other (owned) applications in the top end devices panel in the application overview of the Console.</p>
-      </div>
-      <div class="item-1 item-start-12 d-flex al-center j-center">
-        <p class="ttui-body fs-l">&#8594</p>
-      </div>
-    </a>
-
+
+
+
 
 
   </div>

diff --git a/sitemap.xml b/sitemap.xml
@@ -652,6 +652,9 @@
   </url><url>
     <loc>https://www.thethingsindustries.com/docs/integrations/cloud-integrations/aws-iot/troubleshooting/</loc>
     <lastmod>2023-05-29T17:11:56+02:00</lastmod>
+  </url><url>
+    <loc>https://www.thethingsindustries.com/docs/whats-new/3.32.3/</loc>
+    <lastmod>2024-12-10T20:46:13+01:00</lastmod>
   </url><url>
     <loc>https://www.thethingsindustries.com/docs/whats-new/3.32.2/</loc>
     <lastmod>2024-11-19T17:43:42+01:00</lastmod>
@@ -1467,7 +1470,7 @@
     <lastmod>2022-03-10T13:21:42+01:00</lastmod>
   </url><url>
     <loc>https://www.thethingsindustries.com/docs/the-things-stack/host/aws/ecs/changelog/</loc>
-    <lastmod>2024-11-19T17:43:42+01:00</lastmod>
+    <lastmod>2024-12-10T20:46:13+01:00</lastmod>
   </url><url>
     <loc>https://www.thethingsindustries.com/docs/api/reference/grpc/tenant/</loc>
     <lastmod>2024-08-05T11:34:25+02:00</lastmod>