Test Connector Locally
SkillCloud & infraThe test-locally skill builds and deploys a full local OpenMetadata stack with Docker so you can test a data connector in the OpenMetadata UI. It runs code generation, picks between a full or fast Maven build based on what changed, waits for health checks, and guides you through testing your connector. It can also tear the stack down when you are done.
Then ask your AI: use the Test Connector Locally skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Have Docker running and docker compose available.
What your AI can do with it
- Build and deploy a full local OpenMetadata stack with Docker
- Run code generation with make generate before deploying
- Choose a full or fast Maven build based on changed files
- Wait for health checks before guiding UI testing
- Guide testing of a connector in the OpenMetadata UI
- Tear down and remove containers with docker compose down -v
Getting started
- Have Docker running and docker compose available.
- Be in the OpenMetadata repository root, where docker/run_local_docker.sh exists.
- Activate the environment with source env/bin/activate.
- Run the skill; it runs make generate, detects what changed, and builds and deploys the stack.
- Follow the guided steps to test your connector in the OpenMetadata UI, or pass --teardown to stop and remove containers.
What this skill tells your AI
The instructions your AI receives, as published by open-metadata/openmetadata in skills/test-locally/SKILL.md and read by Ahel’s review.
Build, deploy, and test a connector in a full local OpenMetadata stack with Docker.
When to Activate
When a user asks to "test locally", "start docker", "deploy locally", "test in the UI", "bring up the stack", or "run local docker".
Arguments
--skip-mavenor--fast: Skip the Maven build (use when only ingestion Python code changed)--rebuild: Tear down existing containers and rebuild--teardownor--down: Just stop and remove containers- No arguments: Auto-detect what changed and choose the optimal build strategy
Process
Step 0: Handle Teardown
If the user asked to tear down / stop:
cd docker/development && docker compose down -v
Report success and exit.
Step 1: Check Prerequisites
Verify the environment is ready:
# Check Docker is running
docker info > /dev/null 2>&1 || echo "Docker is not running"
# Check docker compose is available
docker compose version > /dev/null 2>&1 || echo "docker compose not found"
# Check we're in the repo root
test -f docker/run_local_docker.sh || echo "Not in OpenMetadata repo root"
If any check fails, tell the user what to fix and stop.
Step 2: Activate Environment
source env/bin/activate
Step 3: Run Code Generation
Always run code generation to ensure models are up to date:
make generate
If make generate fails, check if the venv is set up:
make install_dev generate
Step 4: Detect Build Strategy
Decide whether to skip the Maven build. Check what files changed:
# Check for Java/schema/UI changes since last build
git diff --name-only HEAD~5 | grep -E "^(openmetadata-spec|openmetadata-service|openmetadata-ui)" | head -5
Skip Maven if:
- User passed
--skip-mavenor--fast - Only files under
ingestion/changed (Python-only changes) - No changes to
openmetadata-spec/,openmetadata-service/, oropenmetadata-ui/
Full build if:
- JSON Schema files changed (
openmetadata-spec/) - Java service code changed (
openmetadata-service/) - UI code changed (
openmetadata-ui/) - First time running (no existing Docker images)
- User explicitly asked for full build
Step 5: Check for Running Containers
docker compose -f docker/development/docker-compose.yml ps --format json 2>/dev/null | head -5
If containers are already running:
- Ask the user if they want to rebuild or just open the UI
- If rebuild, tear down first:
cd docker/development && docker compose down
Step 6: Build and Deploy
Full build:
./docker/run_local_docker.sh -m ui -d mysql -s false -i true -r true
Fast rebuild (ingestion-only):
./docker/run_local_docker.sh -m ui -d mysql -s true -i true -r false
Tell the user which strategy was chosen and why. The build takes:
- Full build: ~5-8 minutes
- Fast rebuild: ~2-3 minutes
Step 7: Wait for Health
The run_local_docker.sh script handles waiting internally. After it completes, verify the services are up:
# Check OpenMetadata server is responding
curl -s -o /dev/null -w "%{http_code}" http://localhost:8585/api/v1/system/version
# Check Elasticsearch
curl -s -o /dev/null -w "%{http_code}" http://localhost:9200
Step 8: Guide the User
Once services are up, tell the user:
The local OpenMetadata stack is running.
Services:
- OpenMetadata UI: http://localhost:8585
- Airflow: http://localhost:8080 (admin / admin)
- Elasticsearch: http://localhost:9200
- MySQL: localhost:3306
To test your connector:
1. Open http://localhost:8585
2. Go to Settings -> Services -> {your service type}
3. Click "Add New Service"
4. Select your connector from the dropdown
5. Fill in connection details and click "Test Connection"
6. If test passes, run metadata ingestion
To tear down when done:
/test-locally --teardown
Troubleshooting
If the user reports issues, check these:
Connector not in dropdown?
# Check service schema registration
grep -l "YourConnector" openmetadata-spec/src/main/resources/json/schema/entity/services/*Service.json
# Need to rebuild without skip-maven
./docker/run_local_docker.sh -m ui -d mysql -s false -i true -r true
Test connection fails?
# Check ingestion container logs
docker compose -f docker/development/docker-compose.yml logs ingestion --tail 50
# Check test_fn keys match test connection JSON
cat openmetadata-service/src/main/resources/json/data/testConnections/{service_type}/{name}.json
Container won't start?
# Check Docker resources (need at least 6GB memory)
docker system info | grep "Total Memory"
# Check port conflicts
lsof -i :8585 -i :8080 -i :9200 -i :3306 | grep LISTEN
# Full reset
cd docker/development && docker compose down -v && docker system prune -f
Build fails?
# Format first, then rebuild
make py_format
mvn spotless:apply
./docker/run_local_docker.sh -m ui -d mysql -s false -i true -r true
Signals
- GitHub stars
- 15k
- Forks
- 2k
- Last commit
- Oct 2026
Questions
- How do I test my connector locally?
- Run the skill from the OpenMetadata repo root. It checks Docker, runs make generate, builds and deploys the local stack, waits for health checks, then guides you through testing the connector in the OpenMetadata UI.
- Can I skip the Maven build?
- Yes. Pass --skip-maven or --fast to skip it, which is useful when only ingestion Python code changed. With no arguments, the skill auto-detects what changed and chooses the build strategy.
- How do I tear down the stack?
- Pass --teardown or --down. The skill runs docker compose down -v in docker/development, reports success, and exits.
Advanced
- Item type
- skill
- Key
test-locally- Source
- github.com/open-metadata/openmetadata
github.com/open-metadata/openmetadata
Related picks
Skill · a5c-ai
The pick for Java110-java-maven-best-practices
Skill · jabrena
The pick for Javadbos-python
Skill · sickn33
The pick for Pythonpython-design-patterns
Skill · wshobson
The pick for Pythonmysql-query
Skill · hashgraph-online
The pick for MySQLmysql-best-practices
Skill · mindrally
The pick for MySQL