Hi Senthil,
Liquibase automation is based on layering changes over schemas that already exist, and the link you sent with Nathan's reply is still spot on correct info:
... it is sort of a chicken and egg problem. When starting liquibase, we don't know what initial startup we need to do because we can't check the table in the schema to know what we have already done...
Good to see you are searching the discussion topics. Liquibase automation and automation in general is best for use in repetitive tasks, which assumes a known set of schemas.
Thanks,
Ronak