Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changeset Consistency Naming conventions #3041

Closed
molivasdat opened this issue Jul 5, 2022 · 0 comments · Fixed by #3042
Closed

Changeset Consistency Naming conventions #3041

molivasdat opened this issue Jul 5, 2022 · 0 comments · Fixed by #3042
Assignees

Comments

@molivasdat
Copy link
Contributor

Environment

Liquibase Version:4.12

Liquibase Integration & Version: All

Liquibase Extension(s) & Version: NA

Database Vendor & Version: All

Operating System Type & Version: All

Infrastructure Type/Provider: NA

Description

liquibase history command uses changeset(s) to identify changes

liquibase status command uses change sets

Steps To Reproduce

Run
liquibase history
against a database that has been updated by at least one changeset

Run
liquibase status
against a database that has at least one changeset needed to be updated.

Actual Behavior

The history command uses the name changesets
Database updated at 1/28/22, 4:53 PM. Applied 97 changeset(s) in 82.304s, DeploymentId: 3410389992

The status command calls uses the name change sets
2 change sets have not been applied to

Expected/Desired Behavior

Both commands use the same terminology
I recommend using changeset.

Screenshots (if appropriate)

If applicable, add screenshots to help explain your problem.

Additional Context

Add any other context about the problem here.

@kataggart kataggart self-assigned this Jul 5, 2022
@kataggart kataggart added this to To Do in Conditioning++ via automation Jul 5, 2022
kataggart added a commit that referenced this issue Jul 5, 2022
Changeset Consistency Naming conventions #3041
@kataggart kataggart linked a pull request Jul 5, 2022 that will close this issue
2 tasks
Conditioning++ automation moved this from To Do to Done Jul 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants