test-locally

Deploy a local OpenMetadata stack with Docker for connector testing.

2|Updated Jul 18, 2023
One-click install
npx skills add https://github.com/Jason-Clark-FG/OpenMetadata-FG --skill test-locally
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-locally
Source: https://github.com/Jason-Clark-FG/OpenMetadata-FG/tree/main/skills/test-locally
Command: npx skills add https://github.com/Jason-Clark-FG/OpenMetadata-FG --skill test-locally

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of building, deploying, and testing custom data connectors within a complete local OpenMetadata environment, ensuring seamless integration and functionality.

Core Features & Use Cases

  • Local Stack Deployment: Sets up a full OpenMetadata instance using Docker for isolated testing.
  • Automated Build & Health Checks: Manages code generation, build optimization, and service health verification.
  • Guided Testing Workflow: Provides clear instructions for testing connectors directly within the OpenMetadata UI.
  • Use Case: A developer working on a new connector for a database can use this Skill to quickly deploy OpenMetadata locally, test their connector's connection and metadata ingestion capabilities without impacting production environments.

Quick Start

Use the test-locally skill to build and deploy the local OpenMetadata stack.

Frequently Asked Questions about test-locally

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a custom data connector locally in OpenMetadata?

You can test a custom data connector locally by deploying a full OpenMetadata stack using Docker, which builds the environment and provides guided testing instructions within the UI.

Can I skip Maven builds when redeploying my local OpenMetadata stack?

Yes, you can skip Maven builds and rebuild existing containers directly, which optimizes the build process when iterating on connector development and testing.

What is the best way to set up an isolated OpenMetadata environment for ingestion testing?

Deploying a local OpenMetadata instance using Docker provides an isolated environment for safely testing metadata ingestion and connector connections without impacting production.

Does this local deployment workflow handle service health verification automatically?

Yes, the local deployment workflow includes automated health checks to verify service availability and manage code generation during the OpenMetadata stack setup.

Why do I need a local OpenMetadata stack for connector development?

A local stack allows you to safely validate connection logic and metadata ingestion capabilities for new databases before integrating the connector into a production environment.

Are there limitations to testing connectors with a local Docker deployment?

The local Docker deployment is specifically designed for isolated connector testing and build optimization, meaning it functions as a development environment rather than a production-ready deployment.