Skip to content
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

Prefix migration guide #4844

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from
Draft

Prefix migration guide #4844

wants to merge 5 commits into from

Conversation

EuroLew
Copy link
Contributor

@EuroLew EuroLew commented Jan 13, 2025

Description

Currently the image used for creating harmonised indices is SNAPSHOT however when camunda/camunda#26972 makes it into a pre-release the image tag will be changed to that version.

PR for bash script is here camunda/camunda#26971
relates to #4498

When should this change go live?

  • This is a bug fix, security concern, or something that needs urgent release support.
  • This is already available but undocumented and should be released within a week.
  • This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
  • This is part of a scheduled alpha or minor. (apply alpha or minor label)
  • There is no urgency with this change and can be released at any time.

PR Checklist

Copy link
Contributor

github-actions bot commented Jan 13, 2025

👋 🤖 🤔 Hello, @EuroLew! 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.6/.

  • docs/self-managed/operational-guides/update-guide/860-to-870.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.

Copy link
Contributor

@conceptualshark conceptualshark left a comment

Choose a reason for hiding this comment

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

Knowing this is still in progress, I took a quick pass at some minor updates for wording consistency and style. Happy to go over things again once it is out of draft/finalized, or at any other point! I left a few questions and notes as to some of my edits so you could ensure they're still correct.

Copy link
Member

@ChrisKujawa ChrisKujawa left a comment

Choose a reason for hiding this comment

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

Thanks @EuroLew good first version. I have some comments and thoughts, see below.

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

When running the StandaloneSchemaManager currently the prefix for the
created indices cannot be configured, this allows that.

## Related issues

relates to camunda/camunda-docs#4844
@akeller akeller added the component:self-managed Docs and issues related to Camunda Platform 8 Self-Managed label Jan 24, 2025
Comment on lines +177 to +189
### Update to 8.7

With the Elasticsearch migration finished, There are mandatory configuration changes to be made prior to updating to 8.7.

:::note
Without these configuration changes the update to 8.7 will fail.
:::

Given a new desired prefix of `some-prefix`

- The configured `CAMUNDA_OPERATE_ELASTICSEARCH_INDEX_PREFIX` must now be `some-prefix`.
- The configured `CAMUNDA_TASKLIST_ELASTICSEARCH_INDEX_PREFIX` must now be `some-prefix`.
- The prefix for the [Camunda exporter](/self-managed/zeebe-deployment/exporters/camunda-exporter.md) should be configured using `ZEEBE_BROKER_EXPORTERS_CAMUNDA_ARGS_INDEX_PREFIX` to `some-prefix`.
Copy link
Member

Choose a reason for hiding this comment

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

Are these changes part of 8.7 or 8.8?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:self-managed Docs and issues related to Camunda Platform 8 Self-Managed
Projects
Status: 👀 In Review
Development

Successfully merging this pull request may close these issues.

5 participants