OrmMigrationAndLogger

[PooyaRaki]

Summary

Introduces a locking mechanism to TypeORM migrations to prevent conflicts when multiple instances attempt to run the same migration simultaneously.

Adds a custom query logger that logs queries to the console without including bound parameters.

Changes

• Disables migrationsRun in the TypeORM settings.
• Introduces a new query logger to TypeORM.
• Ensures TypeORM migrations run after locking the database during startup.
• If migrations are already running in another instance, it retries a few times to check if they have been completed successfully before throwing an error.

[iamacook]

Regarding usage of "our" configu module. Perhaps we can reconsider usage of the "native" one instead. That should be done separately though.

[PooyaRaki]

@hectorgomezv

Yes, this change is due to the fact the database is requested by the controller tests when the v1 database module is attached to the AppModule.

Done 2ea0e5d

I'd love some documentation on these properties.

Since these are TypeOrm parameters I didn't add comments. Do you want me to add TypeOrm reference?

Exactly, the purpose of passing the loggingService is to use it for logging, instead of using the console. The monitoring tools we have in place consume JSON-formatted logs, so logging directly using the console would not play well with it. By using the loggingService it would send JSON-formatted logs, and will also add the appropriate metadata fields (version, build_number).

Done 2ea0e5d

If DatabaseInitializeHook does not contain any logic, I'd remove the class directly.

I added the initialize call for the sake of consistency.