Skip to content

[Explorer] Collector Pipeline #25

@jaydeluca

Description

@jaydeluca

See parent issue #23 for more information / context.

Notes

Collector components have different schema than Java Agent (no target_versions,
different status structure, distribution/type taxonomy).

Collector has multi-dimensional classification:

  • Distributions: core, contrib, third-party
  • Component Types: receiver, processor, exporter, extension, connector

Requirements

  • Implement Collector registry reader
    • Read from ecosystem-registry/collector/{version}/
    • Parse metadata.yaml format from each component type directory
    • Handle receivers/, processors/, exporters/, extensions/, connectors/
    • Extract README/markdown content from component directories
    • Extract distribution and type information
  • Implement Collector transformation logic
    • Map registry data to output schema
    • Include distribution and type metadata in each component
  • Implement Collector output writer
    • Create collector/ directory structure
    • Write content-addressed component files
    • Write content-addressed markdown files
    • Generate version manifests with optional markdown references
    • Generate index.json with taxonomy summary
    • Generate versions.json

Ensure all component types are handled

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions