dagster-community-components 0.1.0__tar.gz

dagster_community_components-0.1.0/.gitignore

@@ -0,0 +1,30 @@
+# Python
+__pycache__/
+*.py[cod]
+*.pyo
+.Python
+*.egg-info/
+dist/
+build/
+
+# macOS
+.DS_Store
+.AppleDouble
+.LSOverride
+
+# IDEs
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# Generation scripts (one-off tooling, not part of the library)
+add_*.py
+update_*.py
+create_*.py
+fix_*.py
+generate_*.py
+create_*.sh
+
+# Dagster
+.dagster/

dagster_community_components-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Eric Thomas
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

dagster_community_components-0.1.0/PKG-INFO

@@ -0,0 +1,294 @@
+Metadata-Version: 2.4
+Name: dagster-community-components
+Version: 0.1.0
+Summary: Community-maintained Dagster components — ingestion, transforms, IO managers, sensors, sinks, resources, and more.
+Project-URL: Homepage, https://dagster-component-ui.vercel.app/
+Project-URL: Registry, https://github.com/eric-thomas-dagster/dagster-component-templates
+Project-URL: CLI, https://github.com/eric-thomas-dagster/dagster-community-components-cli
+Project-URL: Issues, https://github.com/eric-thomas-dagster/dagster-component-templates/issues
+Author-email: Eric Thomas <eric.thomas@dagsterlabs.com>
+License: MIT
+License-File: LICENSE
+Keywords: components,dagster,data-engineering,etl
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Requires-Dist: dagster>=1.10.0
+Requires-Dist: pandas>=1.5.0
+Description-Content-Type: text/markdown
+
+# Dagster Component Templates
+
+A community library of 195+ reusable [Dagster component](https://docs.dagster.io/guides/components) templates covering data ingestion, AI/LLM enrichment, orchestration, infrastructure provisioning, reverse ETL, observability, sensors, and enterprise tool integrations — all configurable via YAML with no Python required.
+
+## What are Dagster Components?
+
+Components are reusable, YAML-configurable building blocks that package common data engineering patterns. Drop one into your project's `defs/` folder and configure it in YAML — no boilerplate Python needed.
+
+```yaml
+# defs/components/sqs_ingest.yaml
+type: dagster_component_templates.SQSToDatabaseAssetComponent
+attributes:
+  asset_name: raw_events
+  queue_url_env_var: SQS_QUEUE_URL
+  database_url_env_var: DATABASE_URL
+  table_name: raw_events
+  partition_type: daily
+```
+
+## Component Library
+
+### Assets (143)
+
+**Ingestion — cloud storage**
+`s3_to_database_asset` · `gcs_to_database_asset` · `adls_to_database_asset`
+
+**Ingestion — messaging & streaming**
+`kafka_to_database_asset` · `sqs_to_database_asset` · `kinesis_to_database_asset` · `eventhubs_to_database_asset` · `servicebus_to_database_asset` · `rabbitmq_to_database_asset` · `pubsub_to_database_asset` · `redis_streams_to_database_asset` · `nats_to_database_asset` · `pulsar_to_database_asset` · `mqtt_to_database_asset`
+
+**Ingestion — files & databases**
+`sftp_to_database_asset` · `sql_to_database_asset` · `csv_file_ingestion` · `rest_api_fetcher` · `openapi_asset` · `graphql_asset`
+
+**AI / LLM enrichment**
+`litellm_inference_asset` · `ollama_inference_asset` · `langchain_chain_asset` · `llm_prompt_executor` · `llm_chain_executor` · `document_summarizer` · `entity_extractor` · `embeddings_generator` · `moderation_scorer` · `anthropic_llm` · `conversation_memory` · `snowflake_cortex_asset`
+
+**dbt**
+`dbt_docs_enriched_project` — extends `DbtProjectComponent` with exposures, metrics, semantic models, contracts, source freshness, and clickable dbt docs links on every asset
+
+**Enterprise orchestration**
+`coalesce_run_asset` · `abinitio_run_asset` · `matillion_run_asset` · `rivery_run_asset` · `precisely_run_asset` · `step_functions_asset` · `dataiku_asset` · `autosys_asset`
+
+**Infrastructure as Code** *(provision resources before pipeline runs)*
+`terraform_asset` · `terraform_cloud_asset` · `cloudformation_asset` · `ansible_asset` · `pulumi_asset` · `helm_deploy` · `aws_cdk_asset`
+
+**Secrets & remote execution**
+`ssh_asset` · `hashicorp_vault`
+
+**Notebooks & ML compute**
+`jupyter_notebook_asset` · `modal_asset`
+
+**Vector stores**
+`pinecone_asset` · `pgvector_asset` · `chromadb_asset` · `elasticsearch_asset`
+
+**Feature stores**
+`feast_asset` · `tecton_asset`
+
+**ML experiment tracking**
+`wandb_asset`
+
+**Data versioning**
+`lakefs_asset`
+
+**Reverse ETL**
+`polytomic_asset`
+
+**Schema discovery**
+`warehouse_schema_assets` — introspects a warehouse at prepare time, creates one external AssetSpec per table with full column metadata
+
+**Analytics & ML**
+`anomaly_detection` · `customer_segmentation` · `ltv_prediction` · `lead_scoring` · `propensity_scoring` · `customer_health_score` · `cohort_analysis` · `funnel_analysis` · `ab_test_analysis` · `campaign_performance` · `multi_touch_attribution` · `product_recommendations` · and more
+
+---
+
+### Sensors (30)
+
+**Cloud storage**
+`s3_monitor` · `gcs_monitor` · `adls_monitor`
+
+**Messaging & streaming**
+`kafka_monitor` · `sqs_monitor` · `kinesis_monitor` · `eventhubs_monitor` · `servicebus_monitor` · `rabbitmq_monitor` · `pubsub_monitor` · `redis_streams_monitor` · `nats_monitor` · `pulsar_monitor` · `mqtt_monitor`
+
+**Files**
+`sftp_monitor` · `sql_monitor`
+
+**Enterprise tools**
+`coalesce_job_sensor` · `abinitio_job_sensor` · `matillion_job_sensor` · `rivery_job_sensor` · `precisely_job_sensor`
+
+**Notifications**
+`slack_notification` · `pagerduty_alert` · `teams_notification` · `opsgenie_alert` · `twilio_notification`
+
+**ML triggers**
+`mlflow_model_sensor`
+
+---
+
+### Asset Checks (7)
+
+`dq_check` · `great_expectations_check` · `soda_check` · `monte_carlo_check` · `sifflet_check` · `acceldata_check` · `freshness_check`
+
+---
+
+### Observations (20)
+
+`clickhouse_table_observation_sensor` · `snowflake_table_observation` · `bigquery_table_observation` · `postgres_table_observation` · `redshift_table_observation` and more
+
+---
+
+### External Assets (21)
+
+`external_clickhouse_table` · `external_snowflake_table` · `external_bigquery_table` · `external_postgres_table` · `external_s3_object` · `external_kafka_topic` and more
+
+---
+
+### Integrations (18)
+
+`aws_glue` · `aws_dms` · `aws_kinesis` · `aws_redshift` · `aws_sagemaker` · `azure_data_factory` · `azure_stream_analytics` · `azure_synapse` · `databricks_asset_bundle` · `databricks_workspace` · `google_bigquery` · `google_cloud_functions` · `google_cloud_run_jobs` · `google_dataflow` · `google_datastream` · `google_pubsub` · `google_vertex_ai` · `snowflake_workspace`
+
+---
+
+## Component Structure
+
+Every component follows the same layout:
+
+```
+component_name/
+├── component.py       # Dagster component class
+├── example.yaml       # Working YAML configuration example
+├── README.md          # Documentation and field reference
+├── requirements.txt   # pip dependencies
+└── schema.json        # Component registry metadata
+```
+
+---
+
+## StateBackedComponent
+
+Several components that discover resources from external APIs use Dagster's `StateBackedComponent` pattern. The API call happens **once at prepare time** and is cached to disk — code-server reloads are instant with zero network calls.
+
+Components using this pattern: `coalesce_run_asset`, `azure_data_factory`, `aws_glue`, `databricks_workspace`, `openapi_asset`, `warehouse_schema_assets`, `step_functions_asset`, `dataiku_asset`, `polytomic_asset`, `autosys_asset`, `terraform_cloud_asset`
+
+To refresh the cached state after adding pipelines/jobs in the external system:
+
+```bash
+dg utils refresh-defs-state
+# or simply restart: dagster dev
+```
+
+---
+
+## Asset Dependencies & Lineage
+
+Every asset component supports a `deps` field for declaring upstream dependencies in the asset graph:
+
+```yaml
+type: dagster_component_templates.LiteLLMInferenceAssetComponent
+attributes:
+  asset_name: enriched_tickets
+  upstream_asset_key: raw_tickets   # loads data + draws lineage edge
+  deps:                              # additional lineage-only edges
+    - support_schema/tickets_raw
+    - raw/other_table
+  model: claude-3-5-sonnet-20241022
+  prompt_template: "Classify: {body}"
+  database_url_env_var: DATABASE_URL
+  table_name: enriched_tickets
+```
+
+**`upstream_asset_key`** — for components that *load* upstream data (LiteLLM, Ollama, LangChain, SQL): draws a lineage edge **and** loads the asset value at runtime.
+
+**`deps`** — for all components: draws additional lineage-only edges without loading data. Use this to express that an asset *depends on* another without consuming it directly.
+
+Dependencies can also be wired externally via `map_resolved_asset_specs()` in `definitions.py` — the same approach used by [Dagster Designer](https://github.com/eric-thomas-dagster/dagster_designer).
+
+---
+
+## Partitioning
+
+All ingestion assets support time-based partitioning out of the box:
+
+```yaml
+attributes:
+  partition_type: daily          # none | daily | weekly | monthly
+  partition_start_date: "2024-01-01"
+  table_name: events_{partition_key}   # {partition_key} is substituted at runtime
+```
+
+---
+
+## Sensor → Asset Pairing
+
+Most sensors are designed to trigger a companion ingestion asset. The sensor detects new data and fires a `RunRequest` with source info in `run_config`; the asset reads and ingests it.
+
+| Sensor | Companion Asset |
+|--------|----------------|
+| `s3_monitor` | `s3_to_database_asset` |
+| `kafka_monitor` | `kafka_to_database_asset` |
+| `sqs_monitor` | `sqs_to_database_asset` |
+| `kinesis_monitor` | `kinesis_to_database_asset` |
+| `eventhubs_monitor` | `eventhubs_to_database_asset` |
+| `rabbitmq_monitor` | `rabbitmq_to_database_asset` |
+| `sftp_monitor` | `sftp_to_database_asset` |
+| … | … (all 15 pairs complete) |
+
+---
+
+## dbt Docs Enrichment
+
+The `dbt_docs_enriched_project` component is a drop-in replacement for `DbtProjectComponent` that adds rich metadata from the dbt manifest to every asset in the Dagster UI:
+
+```yaml
+type: dagster_component_templates.DbtDocsEnrichedProjectComponent
+attributes:
+  project: "{{ project_root }}/dbt_project"
+  dbt_docs_url: "https://dbt-docs.internal.mycompany.com"
+  include_exposures: true
+  include_metrics: true
+  include_semantic_models: true
+  include_contracts: true
+  include_source_freshness: true
+```
+
+Each dbt model asset then shows: a clickable link to the dbt docs page, downstream BI exposures, metrics, semantic models, contract status, and source freshness SLAs — all visible in the Dagster Asset Catalog. All `include_*` flags default to `false` — opt in to only what you need.
+
+---
+
+## Quick Start
+
+### 1. Install dagster
+
+```bash
+pip install dagster
+```
+
+### 2. Copy a component into your project
+
+```bash
+cp -r assets/s3_to_database_asset/ my_project/defs/components/
+```
+
+### 3. Configure in YAML
+
+```yaml
+# defs/components/my_s3_ingest.yaml
+type: dagster_component_templates.S3ToDatabaseAssetComponent
+attributes:
+  asset_name: raw_orders
+  bucket_env_var: DATA_BUCKET
+  database_url_env_var: DATABASE_URL
+  table_name: raw_orders
+```
+
+### 4. Load in definitions.py
+
+```python
+import dagster as dg
+from pathlib import Path
+
+defs = dg.load_from_defs_folder(project_root=Path(__file__).parent)
+```
+
+---
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for how to add new components.
+
+## License
+
+MIT License

dagster_community_components-0.1.0/README.md

@@ -0,0 +1,269 @@
+# Dagster Component Templates
+
+A community library of 195+ reusable [Dagster component](https://docs.dagster.io/guides/components) templates covering data ingestion, AI/LLM enrichment, orchestration, infrastructure provisioning, reverse ETL, observability, sensors, and enterprise tool integrations — all configurable via YAML with no Python required.
+
+## What are Dagster Components?
+
+Components are reusable, YAML-configurable building blocks that package common data engineering patterns. Drop one into your project's `defs/` folder and configure it in YAML — no boilerplate Python needed.
+
+```yaml
+# defs/components/sqs_ingest.yaml
+type: dagster_component_templates.SQSToDatabaseAssetComponent
+attributes:
+  asset_name: raw_events
+  queue_url_env_var: SQS_QUEUE_URL
+  database_url_env_var: DATABASE_URL
+  table_name: raw_events
+  partition_type: daily
+```
+
+## Component Library
+
+### Assets (143)
+
+**Ingestion — cloud storage**
+`s3_to_database_asset` · `gcs_to_database_asset` · `adls_to_database_asset`
+
+**Ingestion — messaging & streaming**
+`kafka_to_database_asset` · `sqs_to_database_asset` · `kinesis_to_database_asset` · `eventhubs_to_database_asset` · `servicebus_to_database_asset` · `rabbitmq_to_database_asset` · `pubsub_to_database_asset` · `redis_streams_to_database_asset` · `nats_to_database_asset` · `pulsar_to_database_asset` · `mqtt_to_database_asset`
+
+**Ingestion — files & databases**
+`sftp_to_database_asset` · `sql_to_database_asset` · `csv_file_ingestion` · `rest_api_fetcher` · `openapi_asset` · `graphql_asset`
+
+**AI / LLM enrichment**
+`litellm_inference_asset` · `ollama_inference_asset` · `langchain_chain_asset` · `llm_prompt_executor` · `llm_chain_executor` · `document_summarizer` · `entity_extractor` · `embeddings_generator` · `moderation_scorer` · `anthropic_llm` · `conversation_memory` · `snowflake_cortex_asset`
+
+**dbt**
+`dbt_docs_enriched_project` — extends `DbtProjectComponent` with exposures, metrics, semantic models, contracts, source freshness, and clickable dbt docs links on every asset
+
+**Enterprise orchestration**
+`coalesce_run_asset` · `abinitio_run_asset` · `matillion_run_asset` · `rivery_run_asset` · `precisely_run_asset` · `step_functions_asset` · `dataiku_asset` · `autosys_asset`
+
+**Infrastructure as Code** *(provision resources before pipeline runs)*
+`terraform_asset` · `terraform_cloud_asset` · `cloudformation_asset` · `ansible_asset` · `pulumi_asset` · `helm_deploy` · `aws_cdk_asset`
+
+**Secrets & remote execution**
+`ssh_asset` · `hashicorp_vault`
+
+**Notebooks & ML compute**
+`jupyter_notebook_asset` · `modal_asset`
+
+**Vector stores**
+`pinecone_asset` · `pgvector_asset` · `chromadb_asset` · `elasticsearch_asset`
+
+**Feature stores**
+`feast_asset` · `tecton_asset`
+
+**ML experiment tracking**
+`wandb_asset`
+
+**Data versioning**
+`lakefs_asset`
+
+**Reverse ETL**
+`polytomic_asset`
+
+**Schema discovery**
+`warehouse_schema_assets` — introspects a warehouse at prepare time, creates one external AssetSpec per table with full column metadata
+
+**Analytics & ML**
+`anomaly_detection` · `customer_segmentation` · `ltv_prediction` · `lead_scoring` · `propensity_scoring` · `customer_health_score` · `cohort_analysis` · `funnel_analysis` · `ab_test_analysis` · `campaign_performance` · `multi_touch_attribution` · `product_recommendations` · and more
+
+---
+
+### Sensors (30)
+
+**Cloud storage**
+`s3_monitor` · `gcs_monitor` · `adls_monitor`
+
+**Messaging & streaming**
+`kafka_monitor` · `sqs_monitor` · `kinesis_monitor` · `eventhubs_monitor` · `servicebus_monitor` · `rabbitmq_monitor` · `pubsub_monitor` · `redis_streams_monitor` · `nats_monitor` · `pulsar_monitor` · `mqtt_monitor`
+
+**Files**
+`sftp_monitor` · `sql_monitor`
+
+**Enterprise tools**
+`coalesce_job_sensor` · `abinitio_job_sensor` · `matillion_job_sensor` · `rivery_job_sensor` · `precisely_job_sensor`
+
+**Notifications**
+`slack_notification` · `pagerduty_alert` · `teams_notification` · `opsgenie_alert` · `twilio_notification`
+
+**ML triggers**
+`mlflow_model_sensor`
+
+---
+
+### Asset Checks (7)
+
+`dq_check` · `great_expectations_check` · `soda_check` · `monte_carlo_check` · `sifflet_check` · `acceldata_check` · `freshness_check`
+
+---
+
+### Observations (20)
+
+`clickhouse_table_observation_sensor` · `snowflake_table_observation` · `bigquery_table_observation` · `postgres_table_observation` · `redshift_table_observation` and more
+
+---
+
+### External Assets (21)
+
+`external_clickhouse_table` · `external_snowflake_table` · `external_bigquery_table` · `external_postgres_table` · `external_s3_object` · `external_kafka_topic` and more
+
+---
+
+### Integrations (18)
+
+`aws_glue` · `aws_dms` · `aws_kinesis` · `aws_redshift` · `aws_sagemaker` · `azure_data_factory` · `azure_stream_analytics` · `azure_synapse` · `databricks_asset_bundle` · `databricks_workspace` · `google_bigquery` · `google_cloud_functions` · `google_cloud_run_jobs` · `google_dataflow` · `google_datastream` · `google_pubsub` · `google_vertex_ai` · `snowflake_workspace`
+
+---
+
+## Component Structure
+
+Every component follows the same layout:
+
+```
+component_name/
+├── component.py       # Dagster component class
+├── example.yaml       # Working YAML configuration example
+├── README.md          # Documentation and field reference
+├── requirements.txt   # pip dependencies
+└── schema.json        # Component registry metadata
+```
+
+---
+
+## StateBackedComponent
+
+Several components that discover resources from external APIs use Dagster's `StateBackedComponent` pattern. The API call happens **once at prepare time** and is cached to disk — code-server reloads are instant with zero network calls.
+
+Components using this pattern: `coalesce_run_asset`, `azure_data_factory`, `aws_glue`, `databricks_workspace`, `openapi_asset`, `warehouse_schema_assets`, `step_functions_asset`, `dataiku_asset`, `polytomic_asset`, `autosys_asset`, `terraform_cloud_asset`
+
+To refresh the cached state after adding pipelines/jobs in the external system:
+
+```bash
+dg utils refresh-defs-state
+# or simply restart: dagster dev
+```
+
+---
+
+## Asset Dependencies & Lineage
+
+Every asset component supports a `deps` field for declaring upstream dependencies in the asset graph:
+
+```yaml
+type: dagster_component_templates.LiteLLMInferenceAssetComponent
+attributes:
+  asset_name: enriched_tickets
+  upstream_asset_key: raw_tickets   # loads data + draws lineage edge
+  deps:                              # additional lineage-only edges
+    - support_schema/tickets_raw
+    - raw/other_table
+  model: claude-3-5-sonnet-20241022
+  prompt_template: "Classify: {body}"
+  database_url_env_var: DATABASE_URL
+  table_name: enriched_tickets
+```
+
+**`upstream_asset_key`** — for components that *load* upstream data (LiteLLM, Ollama, LangChain, SQL): draws a lineage edge **and** loads the asset value at runtime.
+
+**`deps`** — for all components: draws additional lineage-only edges without loading data. Use this to express that an asset *depends on* another without consuming it directly.
+
+Dependencies can also be wired externally via `map_resolved_asset_specs()` in `definitions.py` — the same approach used by [Dagster Designer](https://github.com/eric-thomas-dagster/dagster_designer).
+
+---
+
+## Partitioning
+
+All ingestion assets support time-based partitioning out of the box:
+
+```yaml
+attributes:
+  partition_type: daily          # none | daily | weekly | monthly
+  partition_start_date: "2024-01-01"
+  table_name: events_{partition_key}   # {partition_key} is substituted at runtime
+```
+
+---
+
+## Sensor → Asset Pairing
+
+Most sensors are designed to trigger a companion ingestion asset. The sensor detects new data and fires a `RunRequest` with source info in `run_config`; the asset reads and ingests it.
+
+| Sensor | Companion Asset |
+|--------|----------------|
+| `s3_monitor` | `s3_to_database_asset` |
+| `kafka_monitor` | `kafka_to_database_asset` |
+| `sqs_monitor` | `sqs_to_database_asset` |
+| `kinesis_monitor` | `kinesis_to_database_asset` |
+| `eventhubs_monitor` | `eventhubs_to_database_asset` |
+| `rabbitmq_monitor` | `rabbitmq_to_database_asset` |
+| `sftp_monitor` | `sftp_to_database_asset` |
+| … | … (all 15 pairs complete) |
+
+---
+
+## dbt Docs Enrichment
+
+The `dbt_docs_enriched_project` component is a drop-in replacement for `DbtProjectComponent` that adds rich metadata from the dbt manifest to every asset in the Dagster UI:
+
+```yaml
+type: dagster_component_templates.DbtDocsEnrichedProjectComponent
+attributes:
+  project: "{{ project_root }}/dbt_project"
+  dbt_docs_url: "https://dbt-docs.internal.mycompany.com"
+  include_exposures: true
+  include_metrics: true
+  include_semantic_models: true
+  include_contracts: true
+  include_source_freshness: true
+```
+
+Each dbt model asset then shows: a clickable link to the dbt docs page, downstream BI exposures, metrics, semantic models, contract status, and source freshness SLAs — all visible in the Dagster Asset Catalog. All `include_*` flags default to `false` — opt in to only what you need.
+
+---
+
+## Quick Start
+
+### 1. Install dagster
+
+```bash
+pip install dagster
+```
+
+### 2. Copy a component into your project
+
+```bash
+cp -r assets/s3_to_database_asset/ my_project/defs/components/
+```
+
+### 3. Configure in YAML
+
+```yaml
+# defs/components/my_s3_ingest.yaml
+type: dagster_component_templates.S3ToDatabaseAssetComponent
+attributes:
+  asset_name: raw_orders
+  bucket_env_var: DATA_BUCKET
+  database_url_env_var: DATABASE_URL
+  table_name: raw_orders
+```
+
+### 4. Load in definitions.py
+
+```python
+import dagster as dg
+from pathlib import Path
+
+defs = dg.load_from_defs_folder(project_root=Path(__file__).parent)
+```
+
+---
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for how to add new components.
+
+## License
+
+MIT License

dagster_community_components-0.1.0/asset_checks/acceldata_check/README.md

@@ -0,0 +1,52 @@
+# Acceldata Check
+
+Triggers an Acceldata data quality rule execution on demand and surfaces the result as a Dagster asset check.
+
+Acceldata owns the rule logic — Dagster triggers execution and surfaces pass/fail/warn, exactly like the Soda, Great Expectations, Monte Carlo, and Sifflet integrations.
+
+## How It Works
+
+1. `POST /api/v1/rules/{rule_id}/execute` — triggers the rule run, returns an `executionId`
+2. Polls `GET /api/v1/rules/{rule_id}/executions/{executionId}` until `status` is terminal
+3. Returns `AssetCheckResult(passed=True/False, metadata={...})`
+
+## Configuration
+
+| Field | Required | Description |
+|-------|----------|-------------|
+| `asset_key` | Yes | Dagster asset key to attach this check to (e.g. `warehouse/orders`) |
+| `api_url_env_var` | Yes | Env var with Acceldata API base URL (e.g. `https://mycompany.acceldata.io`) |
+| `api_token_env_var` | Yes | Env var with Acceldata API token |
+| `rule_id` | Yes | ID of the Acceldata DQ rule to execute |
+| `poll_interval_seconds` | No | Seconds between status polls (default: 5.0) |
+| `timeout_seconds` | No | Max seconds to wait for execution (default: 300) |
+| `severity` | No | `ERROR` or `WARN` (default: `ERROR`) |
+
+## Finding Your Rule ID
+
+In the Acceldata UI: **Rules → Select Rule → Rule Details → ID**
+
+## Example
+
+```yaml
+type: dagster_component_templates.AcceldataCheckComponent
+attributes:
+  asset_key: warehouse/orders
+  api_url_env_var: ACCELDATA_API_URL
+  api_token_env_var: ACCELDATA_API_TOKEN
+  rule_id: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
+  severity: ERROR
+```
+
+## Environment Variables
+
+```bash
+export ACCELDATA_API_URL=https://mycompany.acceldata.io
+export ACCELDATA_API_TOKEN=your-api-token
+```
+
+## Dependencies
+
+```
+requests>=2.28.0
+```