Merge branch 'main' into console-sm-byo-oidc

docs/components/console/manage-clusters/manage-api-clients.md

@@ -40,6 +40,14 @@ When the rate limit is triggered, the client will receive an HTTP 429 response.
 
 ## Create a client
 
+Currently, Camunda 8 SaaS supports the following scopes:
+
+- Zeebe - Access to the [Zeebe gRPC](/apis-tools/zeebe-api/grpc.md) and [REST](/apis-tools/zeebe-api-rest/zeebe-api-rest-overview.md) APIs.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
+- Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
+- Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/overview).
+- Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
+
 To create a client, take the following steps:
 
 1. Navigate into the **API** tab.

docs/guides/setup-client-connection-credentials.md

@@ -9,6 +9,16 @@ description: "Set up client connection credentials to create, name, and connect
 
 Here, we'll set up client connection credentials to create, name, and connect your client.
 
+## Create a client
+
+Currently, Camunda 8 SaaS supports the following scopes:
+
+- Zeebe - Access to the [Zeebe gRPC](/apis-tools/zeebe-api/grpc.md) and [REST](/apis-tools/zeebe-api-rest/zeebe-api-rest-overview.md) APIs.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
+- Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
+- Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/overview).
+- Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
+
 To create a new client, take the following steps:
 
 1. Navigate to the API tab [in Camunda Console](https://console.cloud.camunda.io/) by clicking **Clusters > Cluster name > API**.

docs/reference/release-notes/860.md

@@ -2,12 +2,26 @@
 id: 860
 title: "8.6 Release notes"
 description: "Release notes for 8.6, including alphas"
+keywords:
+  ["product development lifecycle", "software development lifecycle", "CI/CD"]
 ---
 
 ## Enhancements
 
 ## 8.6.0-alpha1
 
+### Process development lifecycle (PDLC) blueprint
+
+<!-- https://github.com/camunda/product-hub/issues/2014 -->
+
+Developing and releasing Camunda processes in compliance with your organization's policies often creates a long-running, sometimes complex process across many endpoints - a great use case for an orchestrator like Camunda. Camunda is taking the first steps to orchestrate the development lifecycle using its own engine, relevant Connectors, and a [customizable blueprint](https://marketplace.camunda.com/en-US/apps/439170/cicd-pipeline) that you can modify to fit your needs.
+
+### Process application MVP (SaaS only)
+
+<!-- https://github.com/camunda/product-hub/issues/1983 -->
+
+The [process application](/components/modeler/web-modeler/process-applications.md) is a special type of folder in Web Modeler that enables bulk actions like deploying all assets together. This reduces the risk of having a broken deployment at runtime and makes it more convenient to deploy related files.
+
 ### Instance modification as batch
 
 <!-- Link to main page in https://github.com/camunda/camunda-docs/pull/3747 -->

docs/self-managed/tasklist-deployment/data-retention.md

@@ -54,6 +54,8 @@ Only indices containing dates in their suffix may be deleted.
 
 ### OpenSearch
 
-OpenSearch does not support the Index Lifecycle Management (ILM) Policy, and instead uses Index State Management. Refer to the [AWS documentation](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/ism.html) for configuration guidance.
+OpenSearch does not support the Index Lifecycle Management (ILM) Policy, and instead uses Index State Management (ISM). The same environment variables that are used to activate ILM on Elasticsearch can be used to activate ISM on OpenSearch.
 
+```yaml
 As of the 8.4 release, Tasklist is now compatible with [Amazon OpenSearch](https://aws.amazon.com/de/opensearch-service/) 2.5.x. Note that using Amazon OpenSearch requires [setting up a new Camunda installation](/self-managed/setup/overview.md). A migration from previous versions or Elasticsearch environments is currently not supported.
+```

docusaurus.config.js

@@ -139,6 +139,7 @@ module.exports = {
       "data-modal-disclaimer":
         "Welcome to Camunda 8 Smart docs, powered by AI. Accessing developer docs, forum posts and product blogs from the last year, responses are generated by combining various sources to formulate the best possible answer. If you have feedback please give a thumbs up or down as we continue to improve the AI.",
       "data-modal-example-questions": `What's new in Camunda ${latestVersion}?,What's Camunda SaaS vs Self-Managed?`,
+      "data-search-mode-enabled": "true",
       async: true,
     },
   ],

optimize/self-managed/optimize-deployment/configuration/service-config.yaml

@@ -597,8 +597,3 @@ externalVariable:
     scheduleIntervalInMinutes: 10
     # A rollover is triggered when the size of the current external variable index matches or exceeds the maxIndexSizeGB threshold.
     maxIndexSizeGB: 50
-
-telemetry:
-  # Sets the initial property value of telemetry configuration once when it has never been enabled/disabled before.
-  # Telemetry can later be enabled/disabled in the UI by superusers
-  initializeTelemetry: false

optimize/self-managed/optimize-deployment/configuration/system-configuration.md

@@ -336,16 +336,6 @@ Customize the Optimize UI e.g. by adjusting the logo, head background color etc.
 | externalVariable.variableIngestion.maxBatchRequestBytes          | 10485760      | Content length limit for a variable ingestion REST API bulk request in bytes. Requests will be rejected when exceeding that limit. Defaults to 10MB. In case this limit is raised you should carefully tune the heap memory accordingly, see Adjust Optimize heap size on how to do that.                                 |
 | externalVariable.variableIngestion.maxRequests                   | 5             | The maximum number of variable ingestion requests that can be serviced at any given time.                                                                                                                                                                                                                                 |
 
-### Telemetry configuration
-
-<span class="badge badge--platform">Camunda 7 only</span>
-
-Configuration of initial telemetry settings.
-
-| YAML path                     | Default value | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| ----------------------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| telemetry.initializeTelemetry | false         | Decides whether telemetry is initially enabled or disabled when Optimize starts. Thereafter, telemetry can be turned on and off in the UI by superusers. If enabled, information about the setup and usage of the Optimize is sent to remote Camunda servers for the sake of analytical evaluation. When enabled, the following information is sent every 24 hours: Optimize version, License Key, Optimize installation ID, Database version. <br /><br />Legal note: Before you install Camunda Optimize version >= 3.2.0 or activate the telemetric functionality, please make sure that you are authorized to take this step, and that the installation or activation of the telemetric functionality is not in conflict with any internal company policies, compliance guidelines, any contractual or other provisions or obligations of your company. Camunda cannot be held responsible in the event of unauthorized installation or activation of this function. |
-
 ### Other
 
 Settings of plugin subsystem serialization format, variable import, Camunda endpoint.

optimize/self-managed/optimize-deployment/migration-update/3.13_8.5-to-3.14_8.6.md

@@ -19,6 +19,10 @@ Here you will find information about:
 
 ## Changes in supported environments
 
+### Telemetry
+
+Optimize no longer gathers telemetry data. This change includes removing it from UI and ElasticSearch. The associated key in configuration file (`telemetry.telemetryEndpoint`) was removed.
+
 ### Camunda 7
 
 In Optimize, the minimum supported version of `Java` is 21.

optimize_sidebars.js

@@ -2687,7 +2687,6 @@ module.exports = {
                 "self-managed/optimize-deployment/configuration/multi-tenancy",
                 "self-managed/optimize-deployment/configuration/multiple-engines",
                 "self-managed/optimize-deployment/configuration/setup-event-based-processes",
-                "self-managed/optimize-deployment/configuration/telemetry",
                 "self-managed/optimize-deployment/configuration/common-problems",
               ],
             },

sidebars.js

@@ -1181,10 +1181,6 @@ module.exports = {
                   "Event-based processes",
                   "self-managed/optimize-deployment/configuration/setup-event-based-processes/"
                 ),
-                optimizeLink(
-                  "Telemetry",
-                  "self-managed/optimize-deployment/configuration/telemetry/"
-                ),
                 optimizeLink(
                   "Common problems",
                   "self-managed/optimize-deployment/configuration/common-problems/"

static/.htaccess

@@ -6,6 +6,9 @@ RewriteRule (.*) https://%{SERVER_NAME}/$1 [R=301,L]
 # Disable directory listing and multi views
 Options -Indexes -MultiViews
 
+# Removing telemetry page
+RewriteRule ^optimize/self-managed/optimize-deployment/configuration/telemetry/(.*)$ /optimize/self-managed/optimize-deployment/configuration/getting-started/$1 [R=301,L]
+
 # Remove updating-tasklist pages
 RewriteRule ^docs/components/tasklist/userguide/updating-tasklist-cloud/?$ /docs/self-managed/operational-guides/update-guide/introduction/$1 [R=301,L]
 RewriteRule ^docs/8.5/components/tasklist/userguide/updating-tasklist-cloud/?$ /docs/8.5/self-managed/operational-guides/update-guide/introduction/$1 [R=301,L]
@@ -19,7 +22,6 @@ RewriteRule ^docs/8.4/self-managed/tasklist-deployment/updating-tasklist/?$ /doc
 RewriteRule ^docs/8.3/self-managed/tasklist-deployment/updating-tasklist/?$ /docs/8.3/self-managed/operational-guides/update-guide/introduction/$1 [R=301,L]
 RewriteRule ^docs/8.2/self-managed/tasklist-deployment/updating-tasklist/?$ /docs/8.2/guides/update-guide/introduction/$1 [R=301,L]
 
-
 # Remove community Node Zeebe page
 RewriteRule ^docs/apis-tools/community-clients/javascript/?$ /docs/apis-tools/node-js-sdk/$1 [R=301,L]
 RewriteRule ^docs/8.5/apis-tools/community-clients/javascript/?$ /docs/8.5/apis-tools/node-js-sdk/$1 [R=301,L]

versioned_docs/version-8.2/components/console/manage-clusters/manage-api-clients.md

@@ -24,6 +24,14 @@ The officially offered client libraries (as well as the Node.js client) have alr
 
 ### Create a client
 
+Currently, Camunda 8 SaaS supports the following scopes:
+
+- Zeebe - Access to the [Zeebe gRPC](/apis-tools/grpc.md) API.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
+- Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
+- Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/optimize-api-authorization).
+- Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
+
 To create a client, take the following steps:
 
 1. Navigate into the **API** tab.

versioned_docs/version-8.2/guides/setup-client-connection-credentials.md

@@ -9,6 +9,16 @@ description: "Set up client connection credentials to create, name, and connect
 
 Here, we'll set up client connection credentials to create, name, and connect your client.
 
+## Create a client
+
+Currently, Camunda 8 SaaS supports the following scopes:
+
+- Zeebe - Access to the [Zeebe gRPC](/apis-tools/grpc.md) API.
+- Tasklist - Access to the [Tasklist GraphQL](/apis-tools/tasklist-api/tasklist-api-overview.md) API.
+- Operate - Access to the [Operate REST API](/apis-tools/operate-api/overview.md).
+- Optimize - Access to the [Optimize REST API]($optimize$/apis-tools/optimize-api/optimize-api-authorization).
+- Secrets - Access cluster secrets in a [hybrid setup](/guides/use-connectors-in-hybrid-mode.md).
+
 To create a new client, take the following steps:
 
 1. Navigate to the API tab [in Camunda Console](https://console.cloud.camunda.io/) by clicking **Organization > Cluster name > API**.