Jonas Cirotzki

Correct, as you can see in the box, the corresponding CI job will fail and it will report findings to the security tab (if run on development)

@MateStrysewske removed the special casing for Required from the swagger generation. Ready for review :)

@MateStrysewske I will take another testing pass, I absolutely understand that this change is critical. Also we are not in a rush to merge this therefore we should take our...

Alright, the thing here is that the annotation where just cosmetic before, therefore, we need to figure out which values are really "required". In the past I came along fields...

Hey thank you so much for tackling this so fast! One thing that I came up with is that this code (i.e., `GenerateEntity`) maybe could be better located in `sea-orm-codegen`...

On second thought, it is perfectly fine as we just start the CLI programmatically.

Hey just one quick note: `run_migrate_command` takes the sub-command as input while this PR uses a builder style pattern. I do not have a strong preference for either style, however,...

Hey I have a similar use case: Instead of wrapping the CLI in a `Command` call, I want to call a library function which behaves the same way `sea-orm-cli generate...

Hey @billy1624, thank you so much for your work and the prompt reply :+1:

Can confirm. I run `bin/kc.sh import --file data/import/SOME_FILE.json --override=true` in a Dockerfile right before before starting Keycloak in the entrypoint and I get the following exception: ``` WARN [io.agroal.pool] (agroal-11)...