Skip to content

Conversation

rodrigo-lourenco-lopes
Copy link
Contributor

@rodrigo-lourenco-lopes rodrigo-lourenco-lopes commented Sep 19, 2025

Description

This PR adds the cluster ID to the /topology responses in the next version of the documents.

closes: camunda/camunda#37663

When should this change go live?

  • This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
  • This is already available but undocumented and should be released within a week. (add available & undocumented label)
  • This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
  • This is part of a scheduled alpha or minor. (add alpha or minor label)
  • There is no urgency with this change (add low prio label)

PR Checklist

  • My changes are for an upcoming minor release and are in the /docs directory (version 8.8).
  • My changes are for an already released minor and are in a /versioned_docs directory.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 19, 2025

👋 🤖 🤔 Hello, @mesellings! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.8/.

  • docs/apis-tools/build-your-own-client.md
  • docs/apis-tools/orchestration-cluster-api-rest/specifications/get-topology.api.mdx
  • docs/apis-tools/zeebe-api-rest/specifications/get-cluster-topology.api.mdx
  • docs/apis-tools/zeebe-api-rest/zeebe-api-rest-authentication.md
  • docs/apis-tools/zeebe-api/gateway-service.md
  • docs/self-managed/components/orchestration-cluster/zeebe/operations/cluster-scaling.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

@rodrigo-lourenco-lopes
Copy link
Contributor Author

@lenaschoenburg @camunda/tech-writers do you have time to review this PR this week? :)

lenaschoenburg
lenaschoenburg previously approved these changes Oct 9, 2025
@mesellings
Copy link
Collaborator

@rodrigo-lourenco-lopes shouldn't this be done in the API so that it is then picked up in the generated docs? If we change it directly in the docs, it will get overwritten when the docs are next generated?

@rodrigo-lourenco-lopes
Copy link
Contributor Author

rodrigo-lourenco-lopes commented Oct 13, 2025

@mesellings the changes in the API were made in this PR but some of the files I changed here are just examples of the topology response, while others are part of the api definition. Which of these files are generated from the API?
And how does one go about generating these?

github-merge-queue bot pushed a commit to camunda/camunda that referenced this pull request Oct 14, 2025
## Description

The goal of this PR is firstly to fix the starter and worker
configuration to allow it again to run against saas when configuring the
helm benchmark to do so. This requires that we override the credentials
necessary to connect with saas.
I created a
[benchmark](https://grafana.dev.zeebe.io/d/zeebe-dashboard/zeebe?orgId=1&var-DS_PROMETHEUS=prometheus&var-cluster=$__all&var-namespace=rl-starter-and-worker-fix&var-pod=$__all&var-partition=$__all&var-memory_state=committed&from=now-6h&to=now&timezone=browser)
based on this branch to make sure that we dont break the base case where
the starter connects to the cluster in its own namespace. The fix works
in conjuction with this
[PR](camunda/camunda-docs#6794) in the benchmar
repo.

I also changed the name of the variables to be in line with the ones
generated when we create the Saas API client so that we can copy
directly the env variables to our local environment and deploy the
worker and starter this way to run against saas, only needing to
additionally add `ZEEBE_AUTH_TYPE=OAUTH`.

## Checklist

<!--- Please delete options that are not relevant. Boxes should be
checked by reviewer. -->
- [ ] Enable backports when necessary (fex. [for bug
fixes](https://github.com/camunda/camunda/blob/main/CONTRIBUTING.md#backporting-changes)
or [for CI
changes](https://github.com/camunda/camunda/wiki/CI-&-Automation#when-to-backport-ci-changes)).

## Related issues

closes #
Copy link
Collaborator

@mesellings mesellings left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rodrigo-lourenco-lopes all lgtm - does this need to be backported to the 8.8 docs as well now that these docs are for 8.9?

@rodrigo-lourenco-lopes rodrigo-lourenco-lopes merged commit 4345b88 into main Oct 15, 2025
7 checks passed
@rodrigo-lourenco-lopes rodrigo-lourenco-lopes deleted the rl-cluster-id-api branch October 15, 2025 09:07
@github-project-automation github-project-automation bot moved this from 👀 In Review to ✅ Done in Documentation Team Oct 15, 2025
@rodrigo-lourenco-lopes
Copy link
Contributor Author

@mesellings no, the cluster ID functionality is not present in 8.8.

tsedekey pushed a commit to camunda/camunda that referenced this pull request Oct 15, 2025
## Description

The goal of this PR is firstly to fix the starter and worker
configuration to allow it again to run against saas when configuring the
helm benchmark to do so. This requires that we override the credentials
necessary to connect with saas.
I created a
[benchmark](https://grafana.dev.zeebe.io/d/zeebe-dashboard/zeebe?orgId=1&var-DS_PROMETHEUS=prometheus&var-cluster=$__all&var-namespace=rl-starter-and-worker-fix&var-pod=$__all&var-partition=$__all&var-memory_state=committed&from=now-6h&to=now&timezone=browser)
based on this branch to make sure that we dont break the base case where
the starter connects to the cluster in its own namespace. The fix works
in conjuction with this
[PR](camunda/camunda-docs#6794) in the benchmar
repo.

I also changed the name of the variables to be in line with the ones
generated when we create the Saas API client so that we can copy
directly the env variables to our local environment and deploy the
worker and starter this way to run against saas, only needing to
additionally add `ZEEBE_AUTH_TYPE=OAUTH`.

## Checklist

<!--- Please delete options that are not relevant. Boxes should be
checked by reviewer. -->
- [ ] Enable backports when necessary (fex. [for bug
fixes](https://github.com/camunda/camunda/blob/main/CONTRIBUTING.md#backporting-changes)
or [for CI
changes](https://github.com/camunda/camunda/wiki/CI-&-Automation#when-to-backport-ci-changes)).

## Related issues

closes #
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

Fix Docs for API changes

3 participants