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

liquibase tagExists command fails if --tag command argument is not used in v4.4.x #2109

Closed
szandany opened this issue Sep 22, 2021 · 0 comments · Fixed by #2269
Closed

liquibase tagExists command fails if --tag command argument is not used in v4.4.x #2109

szandany opened this issue Sep 22, 2021 · 0 comments · Fixed by #2269

Comments

@szandany
Copy link
Contributor

Description

In Liquibase versions prior to 4.4.x liquibase tag command can be run successfully without using the --tag command argument.
For example:
liquibase tag myTag
However, in 4.4.x it appears that Liquibase throws an error.

Steps To Reproduce

Run the following command in 4.4.3
liquibase tagExists myTag

Actual Behavior

Unexpected argument(s): myTag
For detailed help, try 'liquibase --help' or 'liquibase <command-name> --help'

Expected/Desired Behavior

The behavior should remain the same in 4.4.x where the command does not need the --tag command argument.

Additional Context

The workaround is to use the command with the --tag command argument.
For example:
liquibase tagExists --tag myTag
@szandany created a pull request on Liquibase docs repo here to correct the command to include the --tag argument.

@molivasdat molivasdat added this to To Do in Conditioning++ via automation Sep 29, 2021
@nvoxland nvoxland moved this from To Do to Code Review in Conditioning++ Dec 13, 2021
@nvoxland nvoxland moved this from Code Review to Ready for Handoff (In JIRA) in Conditioning++ Dec 20, 2021
Conditioning++ automation moved this from Ready for Handoff (In JIRA) to Done Jan 10, 2022
@nvoxland nvoxland removed this from Done in Conditioning++ Jan 21, 2022
@nvoxland nvoxland added this to the v4.7.1 milestone Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants