Removing database support from the Zally

[beena-yatin-kanyal]

can someone from the community please guide me as to how one can remove the database dependency from the zally (i.e. both from the containerize setup and during the localhost development)?

I know the database is required to save violations results but we would like to avoid it? I have gone through the documentation but found no way to do that?

[ePaul]

Hi,

I'm not a specialist for Zally-internals, but I would look into where ApiReviewRepository is used. From a first look, that seems to be in ReviewStatisticsController, ApiViolationsController and a few tests. If this is removed, I suspect there is a good chance that this would work.

Though the Operational/Administrator Manual says that by default an in-memory DB is provided, so just removing all references to Postgres from the docker-compose.yaml (including the SPRING_DATASOURCE properties) might be enough?

[beena-yatin-kanyal]

I am not sure about such behavior. I think I will have to try this to confirm here. I will update this thread once I have done the analysis. Thanks, @ePaul for your time :)

Have a great Christmas and new year ahead.

[tkrop]

@beena-yatin-kanyal It definitely makes sense to run Zally also standalone without using a storage, since the core feature would not be affected by this. If you would provide a pull request that disables the storage providing a sensible error message for effected operations and having the necessary tests, I would support and merge it.

[cemo]

I support this as well. Moreover It can be very cool to just run as github action without any server dependencies. UI seems fancy but the core value can be brought by running with just a cli and give output as an action.