As-is this default hurts local dev - one more setting you need to
export. Let's keep the setup simple instead.
Also the new default would have broken helm chart and production
when updating with new migrations - the cluster name there is `posthog`
for both it seems.
Let's force other deploys to be explicit instead.
* Make DDLs more friendly towards running on a cluster
* Use primary CLICKHOUSE host for migrations and DDL
* loose ends on person kafka create
* posthog -> cluster typo
* add cluster to KAFKA create for plugin logs
* Feed the type monster
* clusterfy local clickhouse
* test docker-compose backed github action
* run just clickhouse and postgres from docker-compose
* move option to between up and <services>
* posthog all the things
* suggest tests run on cluster
* posthog cluster for ci
* use deploy path for docker-compose
* fix for a clickhouse bug 🐛
* complete CH bug fixes
* 5439 the github actions pg configs
* remove CLICKHOUSE_DATABASE (handled automatically)
* update DATABASE_URL for code quality checks
* Missed a few DDLs on Person
* 5439 -> 5432 to please the people
* cleanup persons and use f strings <3 f strings
* remove auto parens
* Update requirements to use our fork of infi.clickhouse_orm
* fix person.py formatting
* Include boilerplate macros for a cluster
* Fix docker dev environment
- Use postgres 12 to fix a failing test
- Leverage a yaml anchor to share worker/web services configuration
- Add psql
- Configure psql
* Don't use :cached
* Use Postgres 12 in docker-compose everywhere
* Use postgresql-client-12
* Remove extraneous whitespace
* Clean up dev.Dockerfile
* Clean up EE dev/test docker-compose
* Simplify docker-compose.ch.test.yml
Co-authored-by: Michael Matloka <dev@twixes.com>
* Make PLUGIN_SERVER_INGESTION True by default
* Disable plugin server ingestion in tests by default
This is so that ingestion tests in here, which rely on old ingestion, don't fail. Plugin server ingestion itself is covered well in the plugin server repo.
* Compile requirements-dev.txt with latest pip-tools
* Install pytest
* Avoid picking up factories as tests
* New runner
* Always set TEST env variable running tests
Some of our tests rely on it.
* Remove repetition
* Fix a broken test
* Cut down noise from bin/tests
* Rename test factory
* Fix stickiness filter
* Skip a broken test
This has been broken since numpy removal PR. Sadly tests were not
running for this submodule
* Fix import on ee
* Run ee tests properly
The django_db_setup fixture will be automatically run when running ee/
module tests.
* Make tests run on CI
* Include REDIS_URL, fix cloud
* Set TEST env variable
* Hack cloud tests to work
* Attempt at workflow fix
* Import Person model when running ee tests
This module implicitly adds hooks, so this is needed when running tests
* Respect reuse-db for clickhouse
* Add custom markers to avoid warnings
* pytest: use ch test database always
Accidentally wiped by ch setup a few times without this. Oops
* Remove repetition in tests
* Pytest: Always run migrations
Testing a state cleanup fix
* Use same DB in conftest and main code
* Pytest: autoset TEST setting without env variable
* fix broken test
Co-authored-by: eric <eeoneric@gmail.com>
* Emit timing gauge to statsd for sync_execute on clickhouse
* take out of block for SHELL_PLUS_PRINT_SQL
* add docker testing for ease
* comment out cypress projectid
