Skip to content

Truncate Liquibase changelogs prior to GA release #1792

@nscuro

Description

@nscuro

Current Behavior

The Liquibase changelog has accumulated a lot of (verbose) changesets, and will continue to do so until we reach GA status.

Proposed Behavior

To make maintenance easier past GA, truncate all existing changesets into a single one.

Care must be taken to ensure that instances that ran all previous changesets will continue to work as if the truncation never happened.

Checklist

Metadata

Metadata

Assignees

No one assigned

    Labels

    blockedcomponent/api-serverenhancementNew feature or requestp2Non-critical bugs, and features that help organizations to identify and reduce risksize/MMedium effort

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions