-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Plausibility check of new Optimize 7 docs #4797
Comments
Hey @PHWaechtler, do you mind checking the content I migrated for the docs for any inconsistencies? You can find out what was migrated from this ticket. Please also take a look at the most important parts (supported environments, configuration properties, update guides). The base version I used was 3.8. Then I migrated the content from the respective version branch from docs.camunda.io. There might be stuff that I missed. |
Hi @mboskamp , Migration & upgrade instructions: Dashboards KPI: This addition that’s listed as ignored I think we can also migrate, it adds more clarification: camunda/camunda-docs@8872f99 Backup: General opensearch terminology: Object variables Third party libraries Telemetry: Security instructions: Let me know if you have any questions! |
Hey Helene Thank you for checking the migrated content and your detailed feedback. Super helpful!
👍 Agree! This is the correct table: https://docs.camunda.io/optimize/self-managed/optimize-deployment/migration-update/camunda-7/instructions/
👍 Agree!
I agree, the browser does not scroll all the way down. But I don't think this is something we can easily fix. I would not spend time to investigate this now.
👍 It makes sense to reverse the order. For Camunda 7 the newest version is the first in the list. However, I would not prioritize this. I will create a follow-up task for it.
👍 I think I misunderstood that section. I thought it was only for Optimize 8. I will add the missing pages for 3.13 and 3.14
👍 Agree. Same as above. I will migrate the additional content.
👍 Will reach out to the Optimize 8 team to find out if the backup/restore API works with Opensearch.
👍 I agree. I will create a follow-up issue.
👍 Sure, this page should be removed.
❓ I checked a few dependencies (frontend and backend) and I believe the pages are up to date for latest/3.14. I compared 3.14 backend and frontend with this page from the C8 docs. Can you point me to the pages that you think are not in sync?
👍 Makes sense. I will remove that page for 3.14/latest.
👍 Let's remove the section and point to the Security section of the configuration guide. I will create a follow-up ticket for the necessary changes and another follow-up for the low-prio/nice-to-have changes. |
OpenSearch will support this feature with 3.15. Documentation will be handled with camunda/camunda#23615. |
You're right those are in sync. I realise now I made the mistake of comparing the versions from the docs with what we have in the pom on current master but the docs are still for 3.14 obviously 😬 |
Acceptance Criteria (Required on creation)
Hints
The following branches have been updated:
Links
Breakdown
Pull Requests
The text was updated successfully, but these errors were encountered: