From b06dbf0bd3bb15712ffa632a61770d169cbef2d5 Mon Sep 17 00:00:00 2001 From: Houssain Barouni <146710021+houssain-barouni@users.noreply.github.com> Date: Tue, 1 Oct 2024 13:17:50 +0200 Subject: [PATCH] docs: update Announcement doc with new Operate and Tasklist webapp urls (#4334) * docs: update Announcement doc with new Operate and Tasklist webapp urls * style(formatting): technical review * docs: code review, differentiate between separated and combined ingress * doc: replace components by web applications --------- Co-authored-by: Christina Ausley --- docs/reference/announcements.md | 27 ++++++++++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/docs/reference/announcements.md b/docs/reference/announcements.md index 727081bd90..cd05d257d9 100644 --- a/docs/reference/announcements.md +++ b/docs/reference/announcements.md @@ -118,7 +118,7 @@ The separated Ingress Helm configuration for Camunda 8 Self-Managed has been dep #### Helm chart - `global.multiregion.installationType` deprecation -The `global.multiregion.installationType` option is used in failover and failback scenarios. This option in the Helm chart has been deprecated in 8.6, and will be removed from the Helm chart in 8.7. `global.multiregion.installationType` was replaced with a set of API endpoints called while following the ([dual-region operational procdure](/self-managed/operational-guides/multi-region/dual-region-ops.md)) +The `global.multiregion.installationType` option is used in failover and failback scenarios. This option in the Helm chart has been deprecated in 8.6, and will be removed from the Helm chart in 8.7. `global.multiregion.installationType` was replaced with a set of API endpoints called while following the ([dual-region operational procedure](/self-managed/operational-guides/multi-region/dual-region-ops.md)) #### Helm chart - Elasticsearch nodes number @@ -140,6 +140,31 @@ Starting with Camunda 8.6, the Camunda Optimize artifact has been split into two Make sure to update your Docker configurations accordingly to ensure compatibility. +### New base path for Operate and Tasklist web applications + +We are introducing a new base path for both the Operate and Tasklist **web applications**. This change applies to both Self-Managed and SaaS environments. + +#### For Self-Managed + +- The new base path for Operate is `/operate`, and for Tasklist, it is `/tasklist`. +- For a [Separated Ingress](/self-managed/setup/guides/ingress-setup.md?ingress=separated) configuration: + - for Operate, the full URL will be `{operate-host}/operate`. Any calls to `{operate-host}` will automatically be redirected to `{operate-host}/operate` + - for Tasklist, the full URL will be `{tasklist-host}/tasklist`. Any calls to `{tasklist-host}` will automatically be redirected to `{tasklist-host}/tasklist`. +- For a [Combined Ingress](/self-managed/setup/guides/ingress-setup.md?ingress=combined) configuration: + - for Operate, the full URL will be `{common-host}/{operate-contextPath}/operate`. Any calls to `{common-host}/{operate-contextPath}` will be automatically redirected to `{common-host}/{operate-contextPath}/operate`. + - for Tasklist, the full URL will be `{common-host}/{tasklist-contextPath}/tasklist`. Any calls to `{common-host}/{tasklist-contextPath}` will be automatically redirected to `{common-host}/{tasklist-contextPath}/tasklist`. + +#### For SaaS + +- The full URL for Operate is now structured as `https://{region}.operate.camunda.io/{clusterId}/operate`. +- The full URL for Tasklist is now structured as `https://{region}.tasklist.camunda.io/{clusterId}/tasklist`. +- Any calls to `https://{region}.operate.camunda.io/{clusterId}` will be redirected to `https://{region}.operate.camunda.io/{clusterId}/operate`. +- Any calls to `https://{region}.tasklist.camunda.io/{clusterId}` will be redirected to `https://{region}.tasklist.camunda.io/{clusterId}/tasklist`. + +:::note +**API URLs** for both Operate and Tasklist remain **unchanged**. +::: + ## Camunda 8.5 Release date: 9th of April 2024