terraform-provider-mezmo
by
mezmo

Description: The Mezmo Terraform Provider allows organizations to manage Pipelines (sources, processors and destinations) programmatically via Terraform.

View on GitHub ↗

Summary Information

Updated 2 hours ago
Added to GitGenius on February 7th, 2025
Created on June 7th, 2023
Open Issues & Pull Requests: 6 (+0)
Number of forks: 2
Total Stargazers: 4 (+0)
Total Subscribers: 8 (+0)

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Repository Insights (GitGenius)

Median issue/PR response: 19.4 hours
Mean response time: 19.4 hours
90th percentile: 19.4 hours
Tracked items: 1

Most active contributors

Detailed Description

The Mezmo Terraform Provider is a Go-based infrastructure-as-code tool that enables organizations to programmatically manage Mezmo Pipelines through Terraform. The provider allows users to define and deploy sources, processors, and destinations as code, integrating Mezmo's telemetry pipeline capabilities into standard Terraform workflows. The project is available both as a downloadable repository for local development and through the HashiCorp Terraform Registry for production use.

The provider requires Terraform version 1.0 or later and Go version 1.20 or higher. Users can build the provider locally by running go install, which compiles the binary and places it in the $GOPATH/bin directory. For local development workflows, the provider supports dev_overrides through a .terraformrc configuration file, allowing developers to test local builds before publishing. The documentation notes that users must clear the .terraform directory when switching between remote registry versions and local development overrides to ensure the correct provider version is used.

Documentation generation is a built-in part of the development process. When developers modify component schemas, descriptions, or types, they must run go generate to automatically regenerate the documentation. This ensures that schema changes are consistently reflected in the provider's documentation without manual updates.

The testing infrastructure supports both full integration test suites and granular unit testing. The full test suite can be executed with Docker containers for required services, allowing comprehensive validation of provider functionality. For more targeted testing, developers can run individual tests or groups of tests using regex patterns against running Docker services. The testing framework includes specialized environment variables for debugging, such as DEBUG_ATTRIBUTES for displaying loaded state attributes and TF_LOG_PROVIDER_MEZMO for trace logging of API requests and responses. The trace logging capability is particularly useful for debugging provider execution and integration tests, though it may expose sensitive information and should only be used in local development environments.

According to GitGenius activity tracking, the repository shows median issue and pull request response latency of 19.4 hours across tracked items. The most active contributor tracked by GitGenius is martinohansen, who has logged 3 events in the repository. The project is classified across multiple infrastructure and DevOps categories including infrastructure as code, cloud resource provisioning, API connectivity, infrastructure orchestration, and Terraform provider development.

The provider integrates with Mezmo's telemetry pipeline platform, enabling users to manage complex data processing pipelines through declarative Terraform configurations. This approach allows infrastructure teams to version control their pipeline configurations, apply standard GitOps practices, and automate pipeline deployments across environments. The combination of local development support, comprehensive testing infrastructure, and integration with the HashiCorp registry makes the Mezmo Terraform Provider suitable for both individual developers and enterprise deployments requiring programmatic pipeline management.

terraform-provider-mezmo
by
mezmomezmo/terraform-provider-mezmo

Repository Details

Fetching additional details & charts...