zitadel/internal/integration/config/postgres.yaml

Database:
  EventPushConnRatio: 0.2 # 4
  ProjectionSpoolerConnRatio: 0.3 # 6
  postgres:
    Host: localhost
    Port: 5432
    Database: zitadel
    MaxOpenConns: 20
    MaxIdleConns: 20
    MaxConnLifetime: 1h
    MaxConnIdleTime: 5m
    User:
      Username: zitadel
      SSL:
        Mode: disable
    Admin:
      Username: zitadel
      SSL:
        Mode: disable
add github action for integration tests 2023-04-25 18:11:04 +03:00			`Database:`
chore(tests): use a coverage server binary (#8407) # Which Problems Are Solved Use a single server instance for API integration tests. This optimizes the time taken for the integration test pipeline, because it allows running tests on multiple packages in parallel. Also, it saves time by not start and stopping a zitadel server for every package. # How the Problems Are Solved - Build a binary with `go build -race -cover ....` - Integration tests only construct clients. The server remains running in the background. - The integration package and tested packages now fully utilize the API. No more direct database access trough `query` and `command` packages. - Use Makefile recipes to setup, start and stop the server in the background. - The binary has the race detector enabled - Init and setup jobs are configured to halt immediately on race condition - Because the server runs in the background, races are only logged. When the server is stopped and race logs exist, the Makefile recipe will throw an error and print the logs. - Makefile recipes include logic to print logs and convert coverage reports after the server is stopped. - Some tests need a downstream HTTP server to make requests, like quota and milestones. A new `integration/sink` package creates an HTTP server and uses websockets to forward HTTP request back to the test packages. The package API uses Go channels for abstraction and easy usage. # Additional Changes - Integration test files already used the `//go:build integration` directive. In order to properly split integration from unit tests, integration test files need to be in a `integration_test` subdirectory of their package. - `UseIsolatedInstance` used to overwrite the `Tester.Client` for each instance. Now a `Instance` object is returned with a gRPC client that is connected to the isolated instance's hostname. - The `Tester` type is now `Instance`. The object is created for the first instance, used by default in any test. Isolated instances are also `Instance` objects and therefore benefit from the same methods and values. The first instance and any other us capable of creating an isolated instance over the system API. - All test packages run in an Isolated instance by calling `NewInstance()` - Individual tests that use an isolated instance use `t.Parallel()` # Additional Context - Closes #6684 - https://go.dev/doc/articles/race_detector - https://go.dev/doc/build-cover --------- Co-authored-by: Stefan Benz <46600784+stebenz@users.noreply.github.com> 2024-09-06 15:47:57 +03:00			`EventPushConnRatio: 0.2 # 4`
			`ProjectionSpoolerConnRatio: 0.3 # 6`
add github action for integration tests 2023-04-25 18:11:04 +03:00			`postgres:`
			`Host: localhost`
			`Port: 5432`
			`Database: zitadel`
chore(tests): use a coverage server binary (#8407) # Which Problems Are Solved Use a single server instance for API integration tests. This optimizes the time taken for the integration test pipeline, because it allows running tests on multiple packages in parallel. Also, it saves time by not start and stopping a zitadel server for every package. # How the Problems Are Solved - Build a binary with `go build -race -cover ....` - Integration tests only construct clients. The server remains running in the background. - The integration package and tested packages now fully utilize the API. No more direct database access trough `query` and `command` packages. - Use Makefile recipes to setup, start and stop the server in the background. - The binary has the race detector enabled - Init and setup jobs are configured to halt immediately on race condition - Because the server runs in the background, races are only logged. When the server is stopped and race logs exist, the Makefile recipe will throw an error and print the logs. - Makefile recipes include logic to print logs and convert coverage reports after the server is stopped. - Some tests need a downstream HTTP server to make requests, like quota and milestones. A new `integration/sink` package creates an HTTP server and uses websockets to forward HTTP request back to the test packages. The package API uses Go channels for abstraction and easy usage. # Additional Changes - Integration test files already used the `//go:build integration` directive. In order to properly split integration from unit tests, integration test files need to be in a `integration_test` subdirectory of their package. - `UseIsolatedInstance` used to overwrite the `Tester.Client` for each instance. Now a `Instance` object is returned with a gRPC client that is connected to the isolated instance's hostname. - The `Tester` type is now `Instance`. The object is created for the first instance, used by default in any test. Isolated instances are also `Instance` objects and therefore benefit from the same methods and values. The first instance and any other us capable of creating an isolated instance over the system API. - All test packages run in an Isolated instance by calling `NewInstance()` - Individual tests that use an isolated instance use `t.Parallel()` # Additional Context - Closes #6684 - https://go.dev/doc/articles/race_detector - https://go.dev/doc/build-cover --------- Co-authored-by: Stefan Benz <46600784+stebenz@users.noreply.github.com> 2024-09-06 15:47:57 +03:00			`MaxOpenConns: 20`
			`MaxIdleConns: 20`
chore(test): set connection lifetimes for postgresql (#8586) # Which Problems Are Solved defaults.yaml only specifies defaults for cockroach. Therefore, options omitted for postgresql are actually set to `0`. This means that the connections timeouts are set to `0` and connections were not reused, resulting in a performance penalty while running the integration tests. # How the Problems Are Solved Set MaxConnLifeTime and MaxConnIdleTime options in postgres # Additional Changes - none # Additional Context - none Co-authored-by: Silvan <silvan.reusser@gmail.com> Co-authored-by: Livio Spring <livio.a@gmail.com> 2024-09-11 10:45:02 +03:00			`MaxConnLifetime: 1h`
			`MaxConnIdleTime: 5m`
add github action for integration tests 2023-04-25 18:11:04 +03:00			`User:`
			`Username: zitadel`
			`SSL:`
			`Mode: disable`
			`Admin:`
			`Username: zitadel`
			`SSL:`
			`Mode: disable`