Weny Xu
408929ffd8
* feat(event): add trigger context to procedure events
Signed-off-by: WenyXu <wenymedia@gmail.com>
* test(event): fix trigger context event contracts
Signed-off-by: WenyXu <wenymedia@gmail.com>
* fix(event): preserve trigger context origins
Signed-off-by: WenyXu <wenymedia@gmail.com>
* fix(event): preserve lifecycle trigger contexts
Signed-off-by: WenyXu <wenymedia@gmail.com>
* fix(meta): gate enterprise trigger imports
Signed-off-by: WenyXu <wenymedia@gmail.com>
* test(event): assert trigger contexts exactly
Signed-off-by: WenyXu <wenymedia@gmail.com>
* fix(test): restore migration test literals
Signed-off-by: WenyXu <wenymedia@gmail.com>
* feat(event): add trigger context to non-table ddl
Signed-off-by: WenyXu <wenymedia@gmail.com>
* refactor(event): simplify trigger context encoding
Signed-off-by: WenyXu <wenymedia@gmail.com>
* fix(event): preserve auto alter trigger reason
Signed-off-by: WenyXu <wenymedia@gmail.com>
* refactor(event): require explicit trigger context
Signed-off-by: WenyXu <wenymedia@gmail.com>
* refactor(event): derive trigger context at ddl boundary
Signed-off-by: WenyXu <wenymedia@gmail.com>
* refactor(event): propagate DDL trigger reasons
Signed-off-by: WenyXu <wenymedia@gmail.com>
* fix(meta): resolve alter table rebase conflict
Signed-off-by: WenyXu <wenymedia@gmail.com>
* test(meta): fix alter table trigger context setup
Signed-off-by: WenyXu <wenymedia@gmail.com>
* refactor(meta): pass trigger context to region migration
Signed-off-by: WenyXu <wenymedia@gmail.com>
* test(event): fix unknown trigger context assertions
Signed-off-by: WenyXu <wenymedia@gmail.com>
* fix(meta): centralize trigger context protocol mapping
Signed-off-by: WenyXu <wenymedia@gmail.com>
* test(event): fix migration trigger context assertion
Signed-off-by: WenyXu <wenymedia@gmail.com>
* refactor(procedure): rename event runtime context
Signed-off-by: WenyXu <wenymedia@gmail.com>
* refactor(event): rename trigger context
Signed-off-by: WenyXu <wenymedia@gmail.com>
* test(event): fix migration event context assertion
Signed-off-by: WenyXu <wenymedia@gmail.com>
---------
Signed-off-by: WenyXu <wenymedia@gmail.com>
(cherry picked from commit 1f1c9270a8)
Setup tests for multiple storage backend
To run the integration test, please copy .env.example to .env in the project root folder and change the values on need.
Take s3 for example. You need to set your S3 bucket, access key id and secret key:
# Settings for s3 test
GT_S3_BUCKET=S3 bucket
GT_S3_REGION=S3 region
GT_S3_ACCESS_KEY_ID=S3 access key id
GT_S3_ACCESS_KEY=S3 secret access key
Run
Execute the following command in the project root folder:
cargo test integration
Test s3 storage:
cargo test s3
Test oss storage:
cargo test oss
Test azblob storage:
cargo test azblob
Setup tests with Kafka wal
To run the integration test, please copy .env.example to .env in the project root folder and change the values on need.
GT_KAFKA_ENDPOINTS = localhost:9092
Setup kafka standalone
cd tests-integration/fixtures
docker compose -f docker-compose.yml up kafka
Setup tests with etcd TLS
This guide explains how to set up and test TLS-enabled etcd connections in GreptimeDB integration tests.
Quick Start
TLS certificates are already at tests-integration/fixtures/etcd-tls-certs/.
-
Start TLS-enabled etcd:
cd tests-integration/fixtures docker compose up etcd-tls -d -
Start all services (including etcd-tls):
cd tests-integration/fixtures docker compose up -d --wait
Certificate Details
The checked-in certificates include:
ca.crt- Certificate Authority certificateserver.crt/server-key.pem- Server certificate for etcd-tls serviceclient.crt/client-key.pem- Client certificate for connecting to etcd-tls
The server certificate includes SANs for localhost, etcd-tls, 127.0.0.1, and ::1.
Regenerating Certificates (Optional)
If you need to regenerate the etcd certificates:
# Regenerate certificates (overwrites existing ones)
./scripts/generate-etcd-tls-certs.sh
# Or generate in custom location
./scripts/generate-etcd-tls-certs.sh /path/to/cert/directory
If you need to regenerate the mysql and postgres certificates:
# Regenerate certificates (overwrites existing ones)
./scripts/generate_certs.sh
# Or generate in custom location
./scripts/generate_certs.sh /path/to/cert/directory
Note: The checked-in certificates are for testing purposes only and should never be used in production.