feat(readOnly): support read only datahub deployments

[RyanHolstien]

Support read only deployment mode through configuration. Will drop writes to ES/OS, SQL, and Kafka.

[codecov]

Codecov Report

❌ Patch coverage is 26.82927% with 30 lines in your changes missing coverage. Please review.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
...din/gms/factory/entity/EntityAspectDaoFactory.java	0.00%	9 Missing ⚠️
...ctory/common/ElasticSearchGraphServiceFactory.java	0.00%	8 Missing ⚠️
...n/gms/factory/common/Neo4jGraphServiceFactory.java	0.00%	6 Missing ⚠️
...actory/kafka/DataHubKafkaEventProducerFactory.java	50.00%	2 Missing and 2 partials ⚠️
...ms/factory/search/ElasticSearchServiceFactory.java	60.00%	1 Missing and 1 partial ⚠️
.../gms/factory/telemetry/TrackingServiceFactory.java	0.00%	0 Missing and 1 partial ⚠️

❌ Your patch status has failed because the patch coverage (26.82%) is below the target coverage (75.00%). You can increase the patch coverage or adjust the target coverage.

📢 Thoughts on this report? Let us know!

[esteban]

@RyanHolstien is there a follow up on on this to include some flag on the UI and the logs (probably at warn level) that read only mode is enabled? Since in this case write operations will be ignored completely it might be a bit risky to turn this on without some failure to clients in case an operator forgets to re-enable writes or uses the wrong endpoint (read-only) for writes.

[david-leifker]

I thought there was another producer besides this one?

[RyanHolstien]

There's the one for usage and platform events which should still be relevant even in read mode to capture when someone is making read calls. Unless we think read-only should not produce any analytics about its usage.

[RyanHolstien]

@RyanHolstien is there a follow up on on this to include some flag on the UI and the logs (probably at warn level) that read only mode is enabled? Since in this case write operations will be ignored completely it might be a bit risky to turn this on without some failure to clients in case an operator forgets to re-enable writes or uses the wrong endpoint (read-only) for writes.

Not at the moment, this should basically never be turned on except in very particular deployment scenarios. Not sure how it would work either since it's intentionally built around not throwing errors. You would get indications at the client layer though since it would be responding with an empty list of rows modified.

[esteban]

Can we just add a very obvious log line at least that will make obvious this is on? perhaps log at WARN level for every mutation? IIUC we are expecting on this mode not to see any write when this is enabled, right? so performance shouldn't be a concern when read only is enabled. Thanks!

[codecov]

Bundle Report

Bundle size has no change ✅