-
Notifications
You must be signed in to change notification settings - Fork 223
Add cluster ID to the topology API #6794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
0c0d091 to
eaef17c
Compare
|
👋 🤖 🤔 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/.
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. |
|
@lenaschoenburg @camunda/tech-writers do you have time to review this PR this week? :) |
|
@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? |
eaef17c to
1f0c927
Compare
|
@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? |
## 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 #
There was a problem hiding this 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?
|
@mesellings no, the cluster ID functionality is not present in 8.8. |
## 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 #
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?
bugorsupportlabel)available & undocumentedlabel)holdlabel)low priolabel)PR Checklist
{type}(scope): {description}commit message(s)/docsdirectory (version 8.8)./versioned_docsdirectory.@camunda/tech-writersunless working with an embedded writer.