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

Addition of liquibase.update() Enhancement Request #1614 #1638

Merged
merged 9 commits into from
Sep 28, 2022

Conversation

Betlista
Copy link
Contributor

@Betlista Betlista commented Jan 20, 2021

Added .update()

  • some JavaDocs.

Environment

Liquibase Version: 4.3.0

Liquibase Integration & Version: maven

Liquibase Extension(s) & Version: N/A

Database Vendor & Version: N/A

Operating System Type & Version: Win 10

Pull Request Type

  • Bug fix (non-breaking change which fixes an issue.)
  • Enhancement/New feature (non-breaking change which adds functionality) closes Addition of liquibase.update() #1614
  • Breaking change (fix or feature that would cause existing functionality to change)

Description

Described in issue itself.

Steps To Reproduce

Described in issue itself.

Actual Behavior

Described in issue itself.

Expected/Desired Behavior

Described in issue itself.

Screenshots (if appropriate)

N/A

Additional Context

N/A

Fast Track PR Acceptance Checklist:

Need Help?

Come chat with us on our discord channel

@molivasdat
Copy link
Contributor

Hi @Betlista
Thanks for providing this PR.

Here’s what happens next:

A member of the Liquibase team will take a look at your contribution and may suggest:

The PR will be prioritized according to our internal development and testing capacity.

We’ll let you know when it’s ready to move to the next step or if any changes are needed.

@kataggart kataggart changed the title Enhancement #1614 Addition of liquibase.update() Enhancement Request #1614 Aug 12, 2022
@liquibase liquibase deleted a comment from codecov bot Sep 6, 2022
@nvoxland nvoxland self-requested a review as a code owner September 6, 2022 17:34
@nvoxland nvoxland added the SafeToBuild Indicates that a particular PR contains changes which are safe to build using GitHub actions label Sep 6, 2022
Copy link
Contributor

@nvoxland nvoxland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the changes, @Betlista

I hadn't originally had the no-arg update() in order to force people to be thinking about context/label usage. But, that's probably an unneeded force to think about and adding the extra function is good. The extra javadocs are good as well.

Code review and test results:

Things to be aware of:

  • Adds a method we are not using, only 3rd party code
  • Failure in test-harness is not related to change

Things to worry about:

  • Nothing

@github-actions
Copy link

github-actions bot commented Sep 6, 2022

Unit Test Results

  4 644 files  ±  0    4 644 suites  ±0   33m 43s ⏱️ - 2m 42s
  4 627 tests +  1    4 412 ✔️ +  5     215 💤  - 4  0 ±0 
54 696 runs  +12  49 676 ✔️ +16  5 020 💤  - 4  0 ±0 

Results for commit b9d2a37. ± Comparison against base commit 165c594.

♻️ This comment has been updated with latest results.

@nvoxland nvoxland added SafeToBuild Indicates that a particular PR contains changes which are safe to build using GitHub actions and removed SafeToBuild Indicates that a particular PR contains changes which are safe to build using GitHub actions labels Sep 21, 2022
liquibase#3277)

* [DAT-11291] Adds snowflake as supported database for snapshot command.

* [DAT-11291] Removes duplicated code.

* [DAT-11291] Adds comment
@nvoxland nvoxland self-assigned this Sep 21, 2022
@nvoxland nvoxland added SafeToBuild Indicates that a particular PR contains changes which are safe to build using GitHub actions and removed SafeToBuild Indicates that a particular PR contains changes which are safe to build using GitHub actions labels Sep 21, 2022
@nvoxland nvoxland removed their assignment Sep 27, 2022
Copy link
Contributor

@XDelphiGrl XDelphiGrl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix allows integrations to call liquibase update without requiring contexts and/or labels.

  • Adds Java docs to several methods.
  • Removes duplicated logUnsupportedDatabase method from SnapshotCommandStep.java, calling the method from InternalSnapshotCommand.java instead.
  • Tests extended to validate communication with Hub using an update that does not pass contexts and/or labels.
  • No additional testing required.

APPROVED

Note: Test failure in harness related to environment setup failure; not related to this change.

@nvoxland nvoxland merged commit c9dd8da into liquibase:master Sep 28, 2022
@nvoxland nvoxland added this to the 1NEXT milestone Sep 30, 2022
@tabbyf00
Copy link

Thanks for your PR submission! We just finished reviewing and merging it into the 4.17.0 release on October 10, 2022. When you get a chance, could you please Star the Liquibase project? The star button is in the upper right corner of the screen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Addition of liquibase.update()
8 participants