Skip to content

Database Deployments (Migrations): setup Flyway for the project #201

Description

@lsulak

Feature Description

There is no automatic and solid approach for handling database objects (tables, constraints, etc). The original author probably did this manually.

Problem / Opportunity

DB is asset and should be treated as a first class citizen, not like this - I cannot even find a proper DDL for the project let alone apply it onto the DB easily.

Acceptance Criteria

DB is properly and automatically handled in terms of db object migration

Proposed Solution

See what we did in Atum Service: https://github.com/AbsaOSS/atum-service/tree/master/database and https://github.com/absa-group/atum-service-deployment/blob/master/.github/workflows/cd-workflow.yml#L101-L130

Dependencies / Related

No response

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions