* fix: don't add cairn-postgresql as a dependency when CAIRN_RUN_POSTGRESQL is false
* fix: don't manage cairn-clickhouse permissions CAIRN_RUN_CLICKHOUSE is false
* fix: add missing CAIRN_POSTGRESQL_HOST and CAIRN_POSTGRESQL_PORT settings to allow usage with external postgresql DBs
This upgrade includes SSO login. Finally! We can now login to Superset
via the LMS. Thanks to OARS for providing the base security manager
implementation!
Superset was ignoring the cairn-redis container, so we decided to remove it.
But the superset celery worker was writing to the /0 database, which conflicts
with the default celery database from the lms/cms. We fix this issue by running
in a different database.
The CELERY_RESULT_BACKEND seemed to be completely useless, so we got rid of it.
Vector is spamming us with messages concerning absent containers. Such messages include:
tutor_local-cairn-vector-1 | 2022-10-07T13:09:27.053010Z INFO source{component_kind="source" component_id=docker_logs component_type=docker_logs component_name=docker_logs}: vector::internal_events::docker_logs: Started watching for container logs. container_id=680c2bf183676caadee2c165b26493f90fb5d02cb15b9f2579a106fdd436f827
Or:
{“log”:“2022-10-07T07:19:17.839042Z INFO vector::internal_events::docker_logs: Started watching for container logs. container_id=a932d5916f9a1d1848224b71070591d16c813e83796d6850fa64b0a5f956d5ed\n”,“stream”:“stderr”,“time”:“2022-10-07T07:19:17.83961548Z”}
{“log”:“2022-10-07T07:19:17.839311Z INFO vector::internal_events::docker_logs: Stopped watching for container logs. container_id=cb9a4330dc154e02f02f6f6b49d9ddb04b5357083becdf6e9c5cbf49f4d01f68\n”,“stream”:“stderr”,“time”:“2022-10-07T07:19:17.83967086Z”}
See also: https://github.com/vectordotdev/vector/issues/8881
This issue has affected multiple users in the past. To address it, we first
tried to upgrade Vector, which did not help. Thus, we decided to reduce the
verbosity of Vector.
