Add project infrastructure tutorial

.cspell.json

@@ -5,14 +5,13 @@
   "language": "en",
   // words - list of words to be always considered correct
   "words": [
-    "agentic",
-    "Agentic",
-    "reinit",
     "ABAC",
     "Additionals",
     "Adyen",
     "affordance",
     "affordances",
+    "agentic",
+    "Agentic",
     "Agricolo",
     "AKHQ",
     "ANIA",
@@ -128,6 +127,7 @@
     "kustomize",
     "Linkerd",
     "locustfile",
+    "LOINC",
     "Lucene",
     "luxon",
     "makeitapp",
@@ -201,6 +201,7 @@
     "servlet",
     "sharded",
     "signup",
+    "SNOMED",
     "stato",
     "storer",
     "struct",

301redirects.json

@@ -2006,5 +2006,21 @@
   "/docs/tools/overview_service_tools": {
     "destination": "/docs/runtime_suite_tools/mlp/overview",
     "addedOn": "2025-05-21"
+  },
+    "/docs/runtime_suite/audit-trail/security": {
+    "destination": "/docs/runtime_suite_sidecars/audit-trail/security",
+    "addedOn": "2025-06-05"
+  },
+  "/docs/runtime_suite/audit-trail/overview": {
+    "destination": "/docs/runtime_suite_sidecars/audit-trail/overview",
+    "addedOn": "2025-06-05"
+  },
+  "/docs/runtime_suite/audit-trail/configuration": {
+    "destination": "/docs/runtime_suite_sidecars/audit-trail/configuration",
+    "addedOn": "2025-06-05"
+  },
+  "/docs/runtime_suite/audit-trail/changelog": {
+    "destination": "/docs/runtime_suite_sidecars/audit-trail/changelog",
+    "addedOn": "2025-06-05"
   }
 }

check-content.js

@@ -11,6 +11,7 @@ const filesToExcludeFromSidebarCheck = [
   "monitoring/paas_alerting_rules",
   "info/licenses-reports/.gitkeep",
   'cli/miactl/*',
+  'mcp/mcp-server/*',
   "info/licenses/*",
   "runtime_suite/*",
   "runtime_suite_applications/*",

docs/cli/miactl/20_setup.md

@@ -38,7 +38,7 @@ If you have [Golang] installed with a version >= 1.13 in your system and you hav
 install `miactl` like this:
 
 ```sh
-go install github.com/mia-platform/miactl/cmd/miactl@v0.17.3
+go install github.com/mia-platform/miactl/cmd/miactl@v0.18.0
 ```
 
 Or like this if the `install` command is not available
@@ -53,11 +53,11 @@ You can install `miactl` with the use of `curl` or `wget` and downloading the la
 choosing the correct platform and operating system:
 
 ```sh
-curl -fsSL --proto '=https' --tlsv1.2 https://github.com/mia-platform/miactl/releases/download/v0.17.3/miactl-linux-amd64 -o /tmp/miactl
+curl -fsSL --proto '=https' --tlsv1.2 https://github.com/mia-platform/miactl/releases/download/v0.18.0/miactl-linux-amd64 -o /tmp/miactl
 ```
 
 ```sh
-wget -q --https-only --secure-protocol=TLSv1_2 https://github.com/mia-platform/miactl/releases/download/v0.17.3/miactl-linux-amd64 -O /tmp/miactl
+wget -q --https-only --secure-protocol=TLSv1_2 https://github.com/mia-platform/miactl/releases/download/v0.18.0/miactl-linux-amd64 -O /tmp/miactl
 ```
 
 After you have downloaded the file you can validate it against the checksum you can find at this [url] running the
@@ -85,7 +85,7 @@ sudo mv /tmp/miactl /usr/local/bin
 If you want to run the cli in its environment or you want to test the cli you can use the Docker image:
 
 ```sh
-docker run ghcr.io/mia-platform/miactl:v0.17.3 miactl
+docker run ghcr.io/mia-platform/miactl:v0.18.0 miactl
 ```
 
 ### Windows
@@ -184,7 +184,7 @@ only via APIs.
 
 [Homebrew]: https://brew.sh "The Missing Package Manager for macOS (or Linux)"
 [Golang]: https://go.dev "Build simple, secure, scalable systems with Go"
-[url]: https://github.com/mia-platform/miactl/releases/download/v0.17.3/checksums.txt "miactl checksums"
+[url]: https://github.com/mia-platform/miactl/releases/download/v0.18.0/checksums.txt "miactl checksums"
 [`bash-completion`]: https://github.com/scop/bash-completion "Programmable completion functions for bash"
 [`oh-my-zsh`]: https://ohmyz.sh "Oh My Zsh is a delightful, open source, community-driven
 	framework for managing your Zsh configuration"

docs/cli/miactl/40_examples.md

@@ -82,33 +82,38 @@ miactl deploy development --no-semver --revision tags/v1.0.0
 
 ## Deploy Project using a service account from a CD pipeline
 
-The commands are the same used above in the [Deploy Project](#deploy-project) section, but you need to use a _Service Account_ for that.
+The commands are the same used above in the [Deploy Project](#deploy-project) section, but you need to use a
+_Service Account_ for that.  
 If you don't know how to create a _Service Account_, read the [dedicated documentation](../../development_suite/identity-and-access-management/manage-service-accounts).
 
 The _Service Account_ can be created with [two different authentication methods](../../development_suite/identity-and-access-management/manage-service-accounts#adding-a-service-account):
+
 * _Client Secret Basic_: the service account authenticates by presenting its `client_id` and `client_secret`;
 * _Private Key JWT_: the service account authenticates by signing a `JWT` (JSON Web Token) using its private key.
 
-
 After creating the _Service Account_, the first step to setup the `miactl` is **create an auth context**.
-With an _auth context_ you can choose how to be authenticated with the Mia-Platform APIs in all your different contexts you create with the `miactl`.
+With an _auth context_ you can choose how to be authenticated with the Mia-Platform APIs in all your different contexts
+you create with the `miactl`.
 
 Based on the authentication method of your _Service Account_, you can create the auth context with the following command:
 
 * _Client Secret Basic_:
+
   ```sh
   miactl context auth <miactl-auth-name> --client-id <sa-client-id> --client-secret <sa-client-secret>
   ```
 
 * _Private Key JWT_:
+
   ```sh
   miactl context auth <miactl-auth-name> --jwt-json <path-to-json-containing-the-json-config-of-a-jwt-service-account>
   ```
 
 Now you can create the context you want use the `miactl` to.
 
 :::warning
-Remember to specify the auth context to be used with the `---auth-name` flag, otherwise the `miactl` will try to perform a user authentication through the default browser.
+Remember to specify the auth context to be used with the `---auth-name` flag, otherwise the `miactl` will try to perform
+a user authentication through the default browser.
 :::
 
 ```sh
@@ -133,7 +138,7 @@ Finally, you can group the commands above and run them inside a pipeline, e.g. a
 # Insert that after your pipeline stages
 delivery:
     stage: deploy
-    image: ghcr.io/mia-platform/miactl:v0.17.3
+    image: ghcr.io/mia-platform/miactl:v0.18.0
 
     script:
       - miactl version

docs/cli/miactl/changelog.md

@@ -15,6 +15,21 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [v0.18.0] - 2025-06-03
+
+### Changed
+
+- deprecated `marketplace` when console version is greater than or equal 14.0.0
+- update go version to 1.24.3
+- update mergo to 1.0.2
+- update oauth2 to 0.30.0
+- update sync to 0.14.0
+- update text to 0.25.0
+
+### Added
+
+- new command: `catalog`
+
 ## [v0.17.3] - 2025-03-20
 
 ### Changed
@@ -363,7 +378,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - create cli sdk
 - create cli renderer
 
-[unreleased]: https://github.com/mia-platform/miactl/compare/v0.17.3...HEAD
+[unreleased]: https://github.com/mia-platform/miactl/compare/v0.18.0...HEAD
+[v0.18.0]: https://github.com/mia-platform/miactl/compare/v0.17.3...v0.18.0
 [v0.17.3]: https://github.com/mia-platform/miactl/compare/v0.17.2...v0.17.3
 [v0.17.2]: https://github.com/mia-platform/miactl/compare/v0.17.1...v0.17.2
 [v0.17.1]: https://github.com/mia-platform/miactl/compare/v0.17.0...v0.17.1

docs/console/console-extensibility/sso.md

@@ -83,7 +83,7 @@ It doesn't matter which of these techniques you will choose. What matters is tha
 
 The Console endpoint that handles extension authorization is the following one, preceded by the Console base URL:
 
-`/tenants/{tenantId}/extension/{extensionId}/authz?state={state}`
+`/oauth/authorize?tenantId={tenantId}&extensionId={extensionId}&state={state}`
 
 Here an example of a frontend page that starts the login flow when the user clicks on a Login button:
 
@@ -95,7 +95,9 @@ function performExtensionLogin() {
    // Remember to store the state and validate it throughout the login flow
    const state = crypto.randomUUID()
 
-   window.location.replace(`https://<CONSOLE_URL>/tenants/${tenantId}/extension/${extensionId}/authz?state=${state}`)
+   window.location.replace(
+     `https://<CONSOLE_URL>/oauth/authorize?tenantId=${tenantId}&extensionId=${extensionId}&state=${state}`
+   )
 }
 ```