-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
User Story (Required on creation):
Camunda's create, drop and update scripts are manually maintained and must be manually applied with patch- and minor-level updates. This is error-prone and not feature-rich. Database migration tools like Flyway or Liquibase provide this functionality. Instead of re-building these components in the process engine, it is better to integrate with one of the tools.
Functional Requirements (Required before implementation):
- The platform integrates with a database migration tool so that a schema can be migrated with it
- Requirements based on user input (support and community)
- Users do not need to know the current version of their database schema before they start the migration
- The tool takes care of applying on the schema changes that haven't been applied yet (i.e. migrations do not fail because tables, indexes, etc. already exist)
- Should not break workflows that users have established based on the current SQL scripts (e.g. not force users on a completely different solution)
Technical Requirements (Required before implementation):
- Potential tools are identified (Liquibase, Flyway, ...)
- Tools are evaluated with respect to our technical requirements as well as non-functional requirements (licensing, maintenance activity, ...)
Limitations of Scope (Optional):
- Only one tool will be supported
Hints (Optional):
This is the controller panel for Smart Panels app
1.
|
Add Liquibase support to all distros |
|
Closed | Unassigned |
2.
|
Test Liquibase changelog for equality against manual scripts |
|
Closed | Unassigned |
3.
|
Document Liquibase usage |
|
Closed | Unassigned |
Integration with a Database Migration Tool
-
-
Resolution: Fixed
-
L3 - Default
-
None
User Story (Required on creation):
Camunda's create, drop and update scripts are manually maintained and must be manually applied with patch- and minor-level updates. This is error-prone and not feature-rich. Database migration tools like Flyway or Liquibase provide this functionality. Instead of re-building these components in the process engine, it is better to integrate with one of the tools.
Functional Requirements (Required before implementation):
- The platform integrates with a database migration tool so that a schema can be migrated with it
- Requirements based on user input (support and community)
- Users do not need to know the current version of their database schema before they start the migration
- The tool takes care of applying on the schema changes that haven't been applied yet (i.e. migrations do not fail because tables, indexes, etc. already exist)
- Should not break workflows that users have established based on the current SQL scripts (e.g. not force users on a completely different solution)
Technical Requirements (Required before implementation):
- Potential tools are identified (Liquibase, Flyway, ...)
- Tools are evaluated with respect to our technical requirements as well as non-functional requirements (licensing, maintenance activity, ...)
Limitations of Scope (Optional):
- Only one tool will be supported
Hints (Optional):
This is the controller panel for Smart Panels app
1.
|
Add Liquibase support to all distros |
|
Closed | Unassigned |
2.
|
Test Liquibase changelog for equality against manual scripts |
|
Closed | Unassigned |
3.
|
Document Liquibase usage |
|
Closed | Unassigned |
-
Unassigned
-
Nico Rehwaldt
-
Tobias Metzke-Bernstein
-
- Votes:
-
0 Vote for this issue
- Watchers:
-
8 Start watching this issue
- Created:
- Updated:
- Resolved: