Migrate important content from Optimize 8 documentation to Optimize 7 3.14

[mboskamp]

Acceptance Criteria (Required on creation)

The Optimize 3.14 documentation branch is a copy of the 3.8 branch. We need to identify major updates and migrate them on a best-effort basis. We can always iterate and migrate more in the future.

Hints

Links

Breakdown

Pull Requests

Beta Give feedback

1. https://github.com/camunda/camunda-docs-optimize/pull/342
2. https://github.com/camunda/camunda-docs-optimize/pull/343
3. https://github.com/camunda/camunda-docs-optimize/pull/344
4. https://github.com/camunda/camunda-docs-optimize/pull/345

[mboskamp]

What content do we want to migrate?

• Update/Migration guides
• Dependency Information
• Installation guide
• Features
  • OpenSearch support: This feature has impact on many aspects of the documentation. It's an alternative DB (next to Elasticsearch), so in all places where we talk about Elasticsearch, we need to include OpenSearch or generically talk about "databases".
  • other features?

What happened so far?

• Updated configuration properties for 3.11-3.14
• Updated dependency information for 3.11-3.14
• Updated migration guide for 3.7-3.14
• Cherry-pick migration guides to 3.11-3.13 feature branches
• Added information about OpenSearch for 3.14 and 3.13
• Went through completed features in the GitHub issue tracker and Jira (which was used until 3.11.0) looking for completed features that introduced documentation.
  • Ignored:
    • hint about session storage
    • clarification about export data
    • camunda-maintained dashboards
  • Already covered (e.g. config flags):
    • Skip hostname verification
    • Proxy settings for webhook notifications
  • Additionally migrated:
    • JSON logging
      • Released with 3.10
      • C8 docs
      • C7 docs
    • non-superusers can export
      • Released with 3.10.0
      • C8 docs
      • C7 docs
    • ML-ready dataset
      • Released with 3.10
      • C8 docs
    • Backup/Restore (several commits, e.g. but we should migrate the full page)
      • Released with 3.10
      • C8 docs
      • Documents REST endpoint -> Should go into REST docs

[mboskamp]

I don't intend to squash the commits in the PRs. It will be helpful to have the history on the branches. We would have a similar history if the branches had been created through a regular release.