@uns-kit/cli 2.0.20 → 2.0.22

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2023 Aljoša Vister
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2023 Aljoša Vister
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,175 +1,175 @@
-# @uns-kit/cli
-
-Command line scaffolding tool for the UNS toolkit. It bootstraps a new project with `@uns-kit/core` preconfigured and ready to extend with additional plugins.
-
-Note: Apps built with uns-kit are intended to be managed by the **UNS Datahub controller**.
-
-## uns-kit in context
-
-uns-kit is a batteries-included toolkit for Unified Namespace applications. It standardizes MQTT wiring, auth, config schemas, and scaffolding so you can focus on your domain logic. The toolkit packages are:
-
-| Package | Description |
-| --- | --- |
-| [`@uns-kit/core`](https://github.com/uns-datahub/uns-kit/tree/main/packages/uns-core) | Base runtime utilities (UnsProxyProcess, MQTT helpers, configuration tooling, gRPC gateway support). |
-| [`@uns-kit/api`](https://github.com/uns-datahub/uns-kit/tree/main/packages/uns-api) | Express plugin that exposes HTTP endpoints, handles JWT/JWKS auth, and republishes API metadata to UNS. |
-| [`@uns-kit/cron`](https://github.com/uns-datahub/uns-kit/tree/main/packages/uns-cron) | Cron-driven scheduler that emits UNS events on a fixed cadence. |
-| [`@uns-kit/temporal`](https://github.com/uns-datahub/uns-kit/tree/main/packages/uns-temporal) | Temporal.io integration that wires workflows into UnsProxyProcess. |
-| [`@uns-kit/cli`](https://github.com/uns-datahub/uns-kit/tree/main/packages/uns-cli) | Command line tool for scaffolding new UNS applications. |
-
-## Prerequisites
-
-- Node.js 18 or newer (ES2022 runtime features)
-- A package manager such as `pnpm`, `npm`, or `yarn`
-- `git` available on PATH (required for `configure-devops`, used to initialize new projects automatically)
-
-## Usage
-
-```bash
-pnpm --package=@uns-kit/cli dlx uns-kit create my-uns-app
-# or with npx
-npx @uns-kit/cli create my-uns-app
-# or after installing globally
-npm install -g @uns-kit/cli
-uns-kit create my-uns-app
-```
-
-The command creates a new directory, copies the starter template, and pins `@uns-kit/core` to the currently published version. After the scaffold finishes:
-
-```bash
-cd my-uns-app
-pnpm install
-pnpm run dev
-```
-
-When `git` is available on your PATH the scaffold also initializes a fresh repository so you can commit immediately.
-
-### Create from a service bundle
-
-```bash
-uns-kit create --bundle ./service.bundle.json
-uns-kit create --bundle ./service.bundle.json --dest ./my-dir
-uns-kit create --bundle ./service.bundle.json --dest . --allow-existing
-```
-
-Bundle-driven create uses `service.bundle.json` as the source of truth. The CLI:
-
-- scaffolds the base TypeScript app from the existing default template
-- copies the original bundle into the project root as `service.bundle.json`
-- generates `SERVICE_SPEC.md` and `AGENTS.md`
-- applies supported bundle features such as `vscode` and `devops`
-
-When `--bundle` is used, the default destination is `./<metadata.name>`. The TypeScript CLI only accepts bundles with `scaffold.stack = "ts"` and currently supports `scaffold.template = "default"` for this MVP. If the bundle targets Python instead, use `uns-kit-py create --bundle ...`.
-
-## Commands
-
-- `uns-kit create <name>` – create a new UNS project in the specified directory.
-- `uns-kit create --bundle <path> [--dest <dir>] [--allow-existing]` – create a new TypeScript UNS project from `service.bundle.json`.
-- `uns-kit configure [path] [features...]` – run multiple configure templates in sequence (`--all`, `--overwrite`).
-- `uns-kit configure-templates [path] [templates...]` – copy any template directory (`--all`, `--overwrite`).
-- `uns-kit configure-devops [path]` – add Azure DevOps tooling (dependencies, script, config) to an existing project.
-- `uns-kit configure-vscode [path]` – copy VS Code launch/workspace files into an existing project.
-- `uns-kit configure-codegen [path]` – scaffold GraphQL code generation and UNS refresh scripts.
-- `uns-kit configure-api [path]` – copy UNS API examples and add `@uns-kit/api`.
-- `uns-kit configure-cron [path]` – copy UNS cron examples and add `@uns-kit/cron`.
-- `uns-kit configure-temporal [path]` – copy UNS Temporal examples and add `@uns-kit/temporal`.
-- `uns-kit configure-python [path]` – copy Python gateway client scaffolding (no npm dependency required).
-- `uns-kit help` – display usage information.
-
-### Configure multiple features at once
-
-Chain several add-ons without running each subcommand manually:
-
-```bash
-uns-kit configure --all
-uns-kit configure ./apps/gateway devops vscode codegen
-```
-
-Mix and match feature names after an optional target directory. Use `--all` to apply every available template in one shot. Add `--overwrite` to refresh files from newer template versions.
-
-### Copy arbitrary templates
-
-Need a template that is not wired into a configure feature (or added in a newer release)? Use:
-
-```bash
-uns-kit configure-templates --all
-uns-kit configure-templates ./apps/gateway uns-dictionary uns-measurements --overwrite
-```
-
-### Configure Azure DevOps
-
-Run inside a scaffolded project to add the Azure DevOps pull-request tooling:
-
-```bash
-uns-kit configure-devops
-pnpm install
-pnpm run pull-request
-```
-
-The command prompts for your Azure DevOps organization/project, ensures the remote repository exists, and updates `config.json` along with the necessary dev dependencies.
-
-### Configure VS Code workspace
-
-```bash
-uns-kit configure-vscode
-```
-
-Copies `.vscode/launch.json` plus a baseline workspace file into the project. Existing files are skipped unless you pass `--overwrite`.
-
-### Configure GraphQL code generation
-
-```bash
-uns-kit configure-codegen
-pnpm install
-pnpm run codegen
-pnpm run refresh-uns
-```
-
-Adds `codegen.ts`, seeds `src/uns/` placeholder types, and wires the GraphQL Code Generator / `refresh-uns` script into `package.json`. After installing the new dev dependencies you can regenerate strongly-typed operations (`pnpm run codegen`) and rebuild UNS topics/tags from your environment (`pnpm run refresh-uns`).
-After installing the new dev dependencies you can regenerate strongly-typed operations (`pnpm run codegen`) and rebuild UNS metadata (topics/tags/assets) from your environment (`pnpm run generate-uns-metadata`).
-
-### Add UNS API scaffolding
-
-```bash
-uns-kit configure-api
-pnpm install
-```
-
-Copies API-oriented examples (under `src/examples/`) and adds `@uns-kit/api` to your project dependencies.
-Use `--overwrite` to refresh the examples after updating `uns-kit`.
-
-### Add cron-based scaffolding
-
-```bash
-uns-kit configure-cron
-pnpm install
-```
-
-Adds cron-oriented example stubs and installs `@uns-kit/cron`.
-Use `--overwrite` to refresh the examples after updating `uns-kit`.
-
-### Add Temporal scaffolding
-
-```bash
-uns-kit configure-temporal
-pnpm install
-```
-
-Copies Temporal example placeholders and installs `@uns-kit/temporal`.
-Use `--overwrite` to refresh the examples after updating `uns-kit`.
-
-### Add Python gateway scaffolding
-
-```bash
-uns-kit configure-python
-```
-
-Copies the Python gateway client template (examples, scripts, requirements, proto) into your project so you can iterate on the gRPC gateway from Python alongside your TypeScript project.
-Use `--overwrite` to refresh the examples after updating `uns-kit`.
-
-### Extend the Config Schema
-
-Edit `src/config/project.config.extension.ts` inside your generated project and run `pnpm run generate-config-schema`. This regenerates `config.schema.json` and `src/config/app-config.ts`, augmenting `@uns-kit/core`'s `AppConfig` so editors and runtime types stay in sync. If completions lag, reload the TypeScript server in your editor.
-
-## License
-
-MIT © Aljoša Vister
+# @uns-kit/cli
+
+Command line scaffolding tool for the UNS toolkit. It bootstraps a new project with `@uns-kit/core` preconfigured and ready to extend with additional plugins.
+
+Note: Apps built with uns-kit are intended to be managed by the **UNS Datahub controller**.
+
+## uns-kit in context
+
+uns-kit is a batteries-included toolkit for Unified Namespace applications. It standardizes MQTT wiring, auth, config schemas, and scaffolding so you can focus on your domain logic. The toolkit packages are:
+
+| Package | Description |
+| --- | --- |
+| [`@uns-kit/core`](https://github.com/uns-datahub/uns-kit/tree/main/packages/uns-core) | Base runtime utilities (UnsProxyProcess, MQTT helpers, configuration tooling, gRPC gateway support). |
+| [`@uns-kit/api`](https://github.com/uns-datahub/uns-kit/tree/main/packages/uns-api) | Express plugin that exposes HTTP endpoints, handles JWT/JWKS auth, and republishes API metadata to UNS. |
+| [`@uns-kit/cron`](https://github.com/uns-datahub/uns-kit/tree/main/packages/uns-cron) | Cron-driven scheduler that emits UNS events on a fixed cadence. |
+| [`@uns-kit/temporal`](https://github.com/uns-datahub/uns-kit/tree/main/packages/uns-temporal) | Temporal.io integration that wires workflows into UnsProxyProcess. |
+| [`@uns-kit/cli`](https://github.com/uns-datahub/uns-kit/tree/main/packages/uns-cli) | Command line tool for scaffolding new UNS applications. |
+
+## Prerequisites
+
+- Node.js 18 or newer (ES2022 runtime features)
+- A package manager such as `pnpm`, `npm`, or `yarn`
+- `git` available on PATH (required for `configure-devops`, used to initialize new projects automatically)
+
+## Usage
+
+```bash
+pnpm --package=@uns-kit/cli dlx uns-kit create my-uns-app
+# or with npx
+npx @uns-kit/cli create my-uns-app
+# or after installing globally
+npm install -g @uns-kit/cli
+uns-kit create my-uns-app
+```
+
+The command creates a new directory, copies the starter template, and pins `@uns-kit/core` to the currently published version. After the scaffold finishes:
+
+```bash
+cd my-uns-app
+pnpm install
+pnpm run dev
+```
+
+When `git` is available on your PATH the scaffold also initializes a fresh repository so you can commit immediately.
+
+### Create from a service bundle
+
+```bash
+uns-kit create --bundle ./service.bundle.json
+uns-kit create --bundle ./service.bundle.json --dest ./my-dir
+uns-kit create --bundle ./service.bundle.json --dest . --allow-existing
+```
+
+Bundle-driven create uses `service.bundle.json` as the source of truth. The CLI:
+
+- scaffolds the base TypeScript app from the existing default template
+- copies the original bundle into the project root as `service.bundle.json`
+- generates `SERVICE_SPEC.md` and `AGENTS.md`
+- applies supported bundle features such as `vscode` and `devops`
+
+When `--bundle` is used, the default destination is `./<metadata.name>`. The TypeScript CLI only accepts bundles with `scaffold.stack = "ts"` and currently supports `scaffold.template = "default"` for this MVP. If the bundle targets Python instead, use `uns-kit-py create --bundle ...`.
+
+## Commands
+
+- `uns-kit create <name>` – create a new UNS project in the specified directory.
+- `uns-kit create --bundle <path> [--dest <dir>] [--allow-existing]` – create a new TypeScript UNS project from `service.bundle.json`.
+- `uns-kit configure [path] [features...]` – run multiple configure templates in sequence (`--all`, `--overwrite`).
+- `uns-kit configure-templates [path] [templates...]` – copy any template directory (`--all`, `--overwrite`).
+- `uns-kit configure-devops [path]` – add Azure DevOps tooling (dependencies, script, config) to an existing project.
+- `uns-kit configure-vscode [path]` – copy VS Code launch/workspace files into an existing project.
+- `uns-kit configure-codegen [path]` – scaffold GraphQL code generation and UNS refresh scripts.
+- `uns-kit configure-api [path]` – copy UNS API examples and add `@uns-kit/api`.
+- `uns-kit configure-cron [path]` – copy UNS cron examples and add `@uns-kit/cron`.
+- `uns-kit configure-temporal [path]` – copy UNS Temporal examples and add `@uns-kit/temporal`.
+- `uns-kit configure-python [path]` – copy Python gateway client scaffolding (no npm dependency required).
+- `uns-kit help` – display usage information.
+
+### Configure multiple features at once
+
+Chain several add-ons without running each subcommand manually:
+
+```bash
+uns-kit configure --all
+uns-kit configure ./apps/gateway devops vscode codegen
+```
+
+Mix and match feature names after an optional target directory. Use `--all` to apply every available template in one shot. Add `--overwrite` to refresh files from newer template versions.
+
+### Copy arbitrary templates
+
+Need a template that is not wired into a configure feature (or added in a newer release)? Use:
+
+```bash
+uns-kit configure-templates --all
+uns-kit configure-templates ./apps/gateway uns-dictionary uns-measurements --overwrite
+```
+
+### Configure Azure DevOps
+
+Run inside a scaffolded project to add the Azure DevOps pull-request tooling:
+
+```bash
+uns-kit configure-devops
+pnpm install
+pnpm run pull-request
+```
+
+The command prompts for your Azure DevOps organization/project, ensures the remote repository exists, and updates `config.json` along with the necessary dev dependencies.
+
+### Configure VS Code workspace
+
+```bash
+uns-kit configure-vscode
+```
+
+Copies `.vscode/launch.json` plus a baseline workspace file into the project. Existing files are skipped unless you pass `--overwrite`.
+
+### Configure GraphQL code generation
+
+```bash
+uns-kit configure-codegen
+pnpm install
+pnpm run codegen
+pnpm run refresh-uns
+```
+
+Adds `codegen.ts`, seeds `src/uns/` placeholder types, and wires the GraphQL Code Generator / `refresh-uns` script into `package.json`. After installing the new dev dependencies you can regenerate strongly-typed operations (`pnpm run codegen`) and rebuild UNS topics/tags from your environment (`pnpm run refresh-uns`).
+After installing the new dev dependencies you can regenerate strongly-typed operations (`pnpm run codegen`) and rebuild UNS metadata (topics/tags/assets) from your environment (`pnpm run generate-uns-metadata`).
+
+### Add UNS API scaffolding
+
+```bash
+uns-kit configure-api
+pnpm install
+```
+
+Copies API-oriented examples (under `src/examples/`) and adds `@uns-kit/api` to your project dependencies.
+Use `--overwrite` to refresh the examples after updating `uns-kit`.
+
+### Add cron-based scaffolding
+
+```bash
+uns-kit configure-cron
+pnpm install
+```
+
+Adds cron-oriented example stubs and installs `@uns-kit/cron`.
+Use `--overwrite` to refresh the examples after updating `uns-kit`.
+
+### Add Temporal scaffolding
+
+```bash
+uns-kit configure-temporal
+pnpm install
+```
+
+Copies Temporal example placeholders and installs `@uns-kit/temporal`.
+Use `--overwrite` to refresh the examples after updating `uns-kit`.
+
+### Add Python gateway scaffolding
+
+```bash
+uns-kit configure-python
+```
+
+Copies the Python gateway client template (examples, scripts, requirements, proto) into your project so you can iterate on the gRPC gateway from Python alongside your TypeScript project.
+Use `--overwrite` to refresh the examples after updating `uns-kit`.
+
+### Extend the Config Schema
+
+Edit `src/config/project.config.extension.ts` inside your generated project and run `pnpm run generate-config-schema`. This regenerates `config.schema.json` and `src/config/app-config.ts`, augmenting `@uns-kit/core`'s `AppConfig` so editors and runtime types stay in sync. If completions lag, reload the TypeScript server in your editor.
+
+## License
+
+MIT © Aljoša Vister

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uns-kit/cli",
-  "version": "2.0.20",
+  "version": "2.0.22",
   "description": "Command line scaffolding tool for UNS applications",
   "type": "module",
   "license": "MIT",
@@ -26,13 +26,13 @@
   ],
   "dependencies": {
     "azure-devops-node-api": "^15.1.1",
-    "@uns-kit/core": "2.0.20"
+    "@uns-kit/core": "2.0.22"
   },
   "unsKitPackages": {
-    "@uns-kit/core": "2.0.20",
-    "@uns-kit/api": "2.0.20",
-    "@uns-kit/cron": "2.0.20",
-    "@uns-kit/temporal": "2.0.20"
+    "@uns-kit/core": "2.0.22",
+    "@uns-kit/api": "2.0.22",
+    "@uns-kit/cron": "2.0.22",
+    "@uns-kit/temporal": "2.0.22"
   },
   "scripts": {
     "build": "tsc -p tsconfig.build.json",

package/templates/api/src/examples/api-example.ts

@@ -1,91 +1,91 @@
-/**
- * Change this file according to your specifications and rename it to index.ts
- */
-import { UnsProxyProcess, ConfigFile } from "@uns-kit/core";
-import { IApiProxyOptions } from "@uns-kit/core";
-import type { UnsEvents } from "@uns-kit/core";
-import "@uns-kit/api";
-import { type UnsProxyProcessWithApi } from "@uns-kit/api";
-
-/**
- * Load the configuration from a file.
- * On the server, this file is provided by the `uns-datahub-controller`.
- * In the development environment, you are responsible for creating and maintaining this file and its contents.
- */
-const config = await ConfigFile.loadConfig();
-
-/**
- * Connect to the API proxy process
- */
-const unsProxyProcess = new UnsProxyProcess(config.infra.host!, {processName: config.uns.processName}) as UnsProxyProcessWithApi;
-const apiOptions: IApiProxyOptions = config.uns?.jwksWellKnownUrl
-  ? {
-      jwks: {
-        wellKnownJwksUrl: config.uns.jwksWellKnownUrl,
-        ...(config.uns.kidWellKnownUrl !== undefined
-          ? { activeKidUrl: config.uns.kidWellKnownUrl }
-          : {}),
-      },
-    }
-  : {
-      jwtSecret: "CHANGEME",
-    };
-const apiInput = await unsProxyProcess.createApiProxy("templateUnsApiInput", apiOptions);
-
-/**
- * Register an API endpoint and event handler
- */
-apiInput.get(
-  "enterprise/site/area/line/",
-  "line-3-furnace",
-  "energy-resource",
-  "main-bus",
-  "summary-1",
-  {
-    tags: ["Tag1"],
-    apiDescription: "Test API endpoint 1",
-    queryParams: [
-      { name: "filter", type: "string", required: true, description: "Filter za podatke" },
-      { name: "limit", type: "number", required: false, description: "Koliko podatkov želiš" },
-    ],
-  }
-);
-
-apiInput.get(
-  "enterprise/site/area/line/",
-  "line-3-compressor",
-  "utility-resource",
-  "air-loop-1",
-  "summary-2",
-  {
-    tags: ["Tag2"],
-    apiDescription: "Test API endpoint 2",
-    queryParams: [
-      { name: "filter", type: "string", required: true, description: "Filter za podatke" },
-      { name: "limit", type: "number", required: false, description: "Koliko podatkov želiš" },
-    ],
-  }
-);
-
-/**
- * Optional: register a catch-all API mapping for a topic prefix.
- * This does not create per-attribute API nodes; the controller treats it as a fallback handler.
- * You can provide a separate Swagger doc for catch-all so it stays distinct from normal APIs (optional).
- */
-await apiInput.registerCatchAll("sij/acroni/#", {
-  apiDescription: "Catch-all handler for sij/acroni/*",
-  tags: ["CatchAll"],
-  queryParams: [
-    { name: "filter", type: "string", required: false, description: "Filter parameter" },
-  ]
-});
-
-apiInput.event.on("apiGetEvent", (event: UnsEvents["apiGetEvent"]) => {
-  try {
-    const appContext = event.req.appContext;
-    // Add SQL query or any other code here
-    event.res.send("OK");
-  } catch (error) {
-    event.res.status(400).send("Error");
-  }    
-});
+/**
+ * Change this file according to your specifications and rename it to index.ts
+ */
+import { UnsProxyProcess, ConfigFile } from "@uns-kit/core";
+import { IApiProxyOptions } from "@uns-kit/core";
+import type { UnsEvents } from "@uns-kit/core";
+import "@uns-kit/api";
+import { type UnsProxyProcessWithApi } from "@uns-kit/api";
+
+/**
+ * Load the configuration from a file.
+ * On the server, this file is provided by the `uns-datahub-controller`.
+ * In the development environment, you are responsible for creating and maintaining this file and its contents.
+ */
+const config = await ConfigFile.loadConfig();
+
+/**
+ * Connect to the API proxy process
+ */
+const unsProxyProcess = new UnsProxyProcess(config.infra.host!, {processName: config.uns.processName}) as UnsProxyProcessWithApi;
+const apiOptions: IApiProxyOptions = config.uns?.jwksWellKnownUrl
+  ? {
+      jwks: {
+        wellKnownJwksUrl: config.uns.jwksWellKnownUrl,
+        ...(config.uns.kidWellKnownUrl !== undefined
+          ? { activeKidUrl: config.uns.kidWellKnownUrl }
+          : {}),
+      },
+    }
+  : {
+      jwtSecret: "CHANGEME",
+    };
+const apiInput = await unsProxyProcess.createApiProxy("templateUnsApiInput", apiOptions);
+
+/**
+ * Register an API endpoint and event handler
+ */
+apiInput.get(
+  "enterprise/site/area/line/",
+  "line-3-furnace",
+  "energy-resource",
+  "main-bus",
+  "summary-1",
+  {
+    tags: ["Tag1"],
+    apiDescription: "Test API endpoint 1",
+    queryParams: [
+      { name: "filter", type: "string", required: true, description: "Filter za podatke" },
+      { name: "limit", type: "number", required: false, description: "Koliko podatkov želiš" },
+    ],
+  }
+);
+
+apiInput.get(
+  "enterprise/site/area/line/",
+  "line-3-compressor",
+  "utility-resource",
+  "air-loop-1",
+  "summary-2",
+  {
+    tags: ["Tag2"],
+    apiDescription: "Test API endpoint 2",
+    queryParams: [
+      { name: "filter", type: "string", required: true, description: "Filter za podatke" },
+      { name: "limit", type: "number", required: false, description: "Koliko podatkov želiš" },
+    ],
+  }
+);
+
+/**
+ * Optional: register a catch-all API mapping for a topic prefix.
+ * This does not create per-attribute API nodes; the controller treats it as a fallback handler.
+ * You can provide a separate Swagger doc for catch-all so it stays distinct from normal APIs (optional).
+ */
+await apiInput.registerCatchAll("sij/acroni/#", {
+  apiDescription: "Catch-all handler for sij/acroni/*",
+  tags: ["CatchAll"],
+  queryParams: [
+    { name: "filter", type: "string", required: false, description: "Filter parameter" },
+  ]
+});
+
+apiInput.event.on("apiGetEvent", (event: UnsEvents["apiGetEvent"]) => {
+  try {
+    const appContext = event.req.appContext;
+    // Add SQL query or any other code here
+    event.res.send("OK");
+  } catch (error) {
+    event.res.status(400).send("Error");
+  }    
+});

package/templates/azure-pipelines.yml

@@ -1,21 +1,21 @@
-variables:
-  privatePool: 'Azure private pool'
-
-trigger:
-- master
-
-stages:
-- stage: version_tag
-  displayName: Add Version Tag
-  pool: $(privatePool)
-  jobs:
-  - job: add_tags
-    steps:
-    - checkout: self
-      persistCredentials: true
-      clean: true
-    - script: |
-        tag=$(node -pe "require('./package.json').version")
-        git tag $tag
-        git push origin $tag
-      displayName: "Add version tag from package.json"
+variables:
+  privatePool: 'Azure private pool'
+
+trigger:
+- master
+
+stages:
+- stage: version_tag
+  displayName: Add Version Tag
+  pool: $(privatePool)
+  jobs:
+  - job: add_tags
+    steps:
+    - checkout: self
+      persistCredentials: true
+      clean: true
+    - script: |
+        tag=$(node -pe "require('./package.json').version")
+        git tag $tag
+        git push origin $tag
+      displayName: "Add version tag from package.json"