Context
In the launchdarkly schema, various tables such as feature_flag_environment_rule, feature_flag_environment, and feature_flag_environment_rule_clause reference variation values by index (e.g., 0, 1, 2), but do not provide any way to resolve these indices to their actual values (e.g., "true", "off", "limit_50").

The table "feature_flag_variation" has the id and values column but missing the index column.

Request
Please add a table or column in the LaunchDarkly connector export that maps variation indices to their actual values and ids.

Why This Matters
Without this mapping:

• The variation indices (e.g., 0, 1, 2) are not human-readable or actionable

• It is impossible to join environment rules or fallthroughs with their actual served values

• Organizations cannot fully trust or automate analysis based on this data

This limits the usefulness of an otherwise powerful integration and forces teams to fall back on manual inspection or LaunchDarkly API calls - defeating the purpose of the connector.

Please let know if you need any additional information.

Thanks