Michal Landsman

@jouni thanks, it is actually even free for OSS project I think. Let me know if I can help with that - I did many github actions workflows similar to...

The mention of another dependency in the documentation also surprised me. I would like to have it straight as a `liquibase-gradle-plugin` dependency and not really worry about it.

But you are talking about versions where there is some BC break, right? It's still a much better solution than letting this effort to users, to be honest.

@ZooToby yes, please! What about starting with a quick YouTube video where you show it and the community can help thanks to that? I ended up with JPA Buddy to...

That sounds good. I'd like to take a look at the configuration and provide some feedback.

Yeah, the current approach is overcomplicated. It should be loaded from properties as a plugin for Maven in an ideal world.

There is still not a good example I see. What am I missing is also option how to load configuration from properties.

@nbrugger-tgm are you using spring framework, spring boot? I don't like that configuration with db details in gradle task when I have this convered already in property / yml files...

> Could you specify how you think this should work with spring? just put there path to property file and support replacement for env variables, for example: ```properties spring.datasource.username=${DB_USER} spring.datasource.password=${DB_PASS}...

I can use it to generate diff with real db for example.