# Overriding Liquibase Spring Boot default behavior

**URL:** <https://forum.liquibase.org/t/overriding-liquibase-spring-boot-default-behavior/9727>\
**Category:** General Discussion\
**Created:** [September 7, 2024, 9:09pm UTC](https://forum.liquibase.org/t/overriding-liquibase-spring-boot-default-behavior/9727 "2024-09-07T21:09:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vballari](https://avatars.discourse-cdn.com/v4/letter/v/9fc348/32.png) [@vballari](https://forum.liquibase.org/u/vballari)\
**Post date:** [September 7, 2024, 9:09pm UTC](https://forum.liquibase.org/t/overriding-liquibase-spring-boot-default-behavior/9727/1 "2024-09-07T21:09:03Z")

</div>

After doing few POCs on db schema management tools, we decided to go with Liquibase. I’m okay with the default behavior of the Spring Boot app - “update”. Is there a way I can override this behavior to a kind of status check, like Liquibase goal - “status” that is used with maven?  
While looking at some documentation, I came across few java classes - liquibase.command.CommandScope, liquibase.command.CommandStep. Can we use these and related classes to achieve overriding? Greatly appreciate, if someone can throw some light on this.  
Thanks  
Ven