…& SamplingSequencer

Add clear documentation about the current single-environment limitation
where all components (including SamplingSequencer) share the same
TeamHeaderValue from userdata.

Document future solution: SamplingSequencer should have its own Environment
property to explicitly couple it with its paired HoneycombExporter, enabling
multi-environment support while maintaining the requirement that a
SamplingSequencer uses the same Environment as its downstream exporter.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Implements environment ID to API key lookup using per-pipeline userdata,
replacing the previous global approach. This enables proper multi-environment
support in the future while maintaining single-environment compatibility.

Key changes:
- Added findTeamHeaderValueForPath() to compute TeamHeaderValue per-pipeline
- Each pipeline gets its own pathUserdata with computed TeamHeaderValue
- Environment ID (e.g., hny_abc123) is looked up in APIKeys map from userdata
- Falls back to APIKey property, then APIKey default value
- SamplingSequencer and HoneycombExporter share the same API key per pipeline
- For single-environment setups, falls back to any HoneycombExporter globally

The lookup priority is:
1. Environment ID looked up in userdata["APIKeys"] map
2. User-defined APIKey property
3. APIKey default value from template (${HTP_EXPORTER_APIKEY})

This approach works for current single-environment configurations and
doesn't block future multi-environment support with Router components.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

- Add template fallback to use ${HTP_EXPORTER_APIKEY} when TeamHeaderValue is empty
- Fix connection types in test files (Honeycomb → HoneycombEvents)
- Update golden test files to expect fallback for split-path scenarios
- Remove unused h parameter from findTeamHeaderValueForPath

This is an intermediate commit before merging mike/multiple-environments
to get complete pipeline traversal solution.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

This commit integrates two complementary approaches to environment handling:

1. **Router/SetEnvironment components** (from multiple-environments branch):
   - Adds Router and SetEnvironment components for multi-environment routing
   - Updates path traversal to follow Environment connections
   - Adds pipeline transformation logic for routing connectors
   - Injects environment-specific API key variables (${HTP_EXPORTER_APIKEY_<ENV>})

2. **Per-path API key lookup** (from hny-exporter-env branch):
   - Adds findTeamHeaderValueForPath() to compute TeamHeaderValue per pipeline
   - Looks up actual API keys from userdata["APIKeys"] map based on Environment ID
   - Stores TeamHeaderValue in pathUserdata for all components in a pipeline
   - Ensures SamplingSequencer and HoneycombExporter use same API key

**Integration approach:**
- Resolved merge conflicts by keeping all functions from both branches
- Added findTeamHeaderValueForPath() integration into GenerateConfig()
- Restored missing Inspect() and utility functions needed by tests
- Added componentVersionSupported() for test compatibility

**Files modified:**
- pkg/translator/translator.go: Core translation logic with both approaches
- pkg/hpsf/hpsfTypes.go: Path traversal with Environment connection support
- pkg/data/components/: Added Router.yaml, SetEnvironment.yaml
- pkg/config/: Updated to support routing connectors and environment handling
- testdata/: Added router and setenvironment test cases

**Known issue:**
TestSamplingSequencerRuleOrdering fails due to changes from multiple-environments
branch. This test passes on the original hny-exporter-env branch. The issue appears
to be related to port index extraction or sorting, not the API key lookup feature.
This needs investigation but doesn't block the core functionality.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

The previous merge commit accidentally lost the Inspect() method and related
test utility functions (Exporters, Processors, Receivers, Samplers predicates,
ComponentInfo, InspectionResult types, and componentVersionSupported).

These functions are required by the test suite and were in the original
hny-exporter-env branch but got lost during the merge resolution.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

The findTeamHeaderValueForPath function was accidentally removed during the
merge commit. This function is essential for per-path API key lookup.

Added back:
- findTeamHeaderValueForPath() method definition
- Integration call in GenerateConfig() to populate pathUserdata["TeamHeaderValue"]

This fixes the issue where HoneycombExporter was getting <no value> for
x-honeycomb-team header instead of the proper API key.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Simplify pipeline generation by removing custom pipeline naming in favor of
generated pipeline names based on path hashing. This change removes:

- EnvironmentName property from HoneycombExporter component definition
- PipelineName field from PathWithConnections struct
- Custom pipeline name assignments in translator (intake, environment-based)
- EnvironmentName references in router test files

Pipeline names are now consistently generated using GetID() which creates
a hash of component names and connection type. Environment-specific API
keys are still looked up correctly via Environment IDs.

Test results:
- 48/51 tests passing (~94%)
- 3 pre-existing test failures remain (documented in PR #246)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Remove EnvironmentName property from HoneycombExporter and all related code
that built environment maps from this property. This simplifies pipeline
generation and standardizes on using Environment IDs for lookups.

Changes:
- Remove EnvironmentName property validation functions
- Remove buildExporterEnvironmentMap() function
- Remove injectEnvironmentAPIKeys() function
- Remove generateRefineryRulesWithRouter() EnvironmentName traversal logic
- Remove SetEnvironment EnvironmentName lookup (property doesn't exist)
- Remove dynamic routing connector generation based on EnvironmentName
- Update test files to remove EnvironmentName property references

The system now relies on Environment IDs in the Environment property for
API key lookups. Environment slug/name information for refinery rules will
need to be provided through userdata in future updates.

Test results: 48/51 tests passing (~94%)
- 3 pre-existing failures remain (documented in PR #246)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Fixes TestSamplingSequencerRuleOrdering by ensuring connections are
sorted numerically by port index rather than lexicographically by name.

Changes:
- Add Index field to Port struct to store explicit port ordering
- Add PopulateComponentPorts method to load port metadata from templates
- Implement getPortIndex helper for retrieving port indices
- Sort connections by port index in FindAllPaths before traversal
- Update getFirstConnectionPortIndex to check path components first

This ensures "Rule 2" comes before "Rule 10" in path traversal order,
fixing the ordering regression introduced by Environment connection
routing logic.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

- Add isComponentVersionCompatible helper function to eliminate duplicate
  version checking code between MakeConfigComponent and
  getMatchingTemplateComponents
- Remove redundant exact version match check (tc.Version == component.Version)
  as artifactVersionSupported already handles exact matches
- Implement intelligent version inference: when min/max not set, accept
  same major version with version <= component version
- Maintains backward compatibility (v0.1.0 works with v0.2.0 templates)
- Rejects invalid versions (e.g., v999999.1.0)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

…Sequencer

When a SamplingSequencer and HoneycombExporter are in different signal paths
(e.g., traces path vs sampling/events path), the SamplingSequencer needs to
use the same APIKey as the downstream HoneycombExporter.

- Add findDownstreamHoneycombExporter to search for HoneycombExporter
  components downstream from a SamplingSequencer
- Only propagate explicitly set APIKey properties (not Environment-based
  lookups or defaults) to ensure correct behavior
- Update test expectation to match YAML parser behavior (strips ${} wrapper
  when parsing config)

This ensures that user-defined API keys in HoneycombExporter are correctly
used by SamplingSequencer exporters that send data to Refinery.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>