operaton / operaton/documentation
Migration Guide
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 15
- Avg merge
- 7d 18h
- Merged PRs (30d)
- 6
Description
The documentation should contain a detailed guide for migration from Camunda 7.
This issue is to collect known things to document. Add comments for things to add to this description.
- When upgrading the database schema with Liquibase it might occur that Liquibase complains about changed checksums. This is especially happening when Operaton beta versions have been used for the database upgrade. In this case start the server once with option
spring.liquibase.clear-checksums=true - The admin user has changed its name from
camunda-admintooperaton-admin.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No documentation files or tests are named. Start by locating the migration documentation structure and reviewing the listed Liquibase checksum and admin-user changes. Done means adding a detailed Camunda 7 migration guide that covers these items and any additional confirmed migration notes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spring
- Domain
- database, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100