We’re running the genesys-cloud cxascode export command to pull our Architect flow definitions into version control, but the output JSON is stripping out the custom attributes we use for distributed tracing. We’ve injected a unique span ID into the flow’s attributes object via a Data Action before the export trigger, expecting to see that payload in the generated .json file. Instead, the CLI seems to sanitize or ignore any non-standard keys in the attributes map. The goal is to have the exported JSON contain the exact trace context so we can correlate deployment changes with specific OTel spans in Jaeger. Here’s the relevant snippet from the exported flow file:
{
"id": "flow-12345",
"name": "Customer Support Route",
"attributes": {
"version": "1.2",
"description": "Main inbound flow"
}
}
Notice how traceparent and our custom otel.span.id are missing. We’ve tried using the --include-attributes flag, but the documentation is vague on whether this applies to custom keys or just the built-in metadata. Is there a specific flag or configuration file we need to tweak to force the CLI to dump the raw attribute map? We need this for audit trails. If the CLI can’t do it, we’re looking at hitting the /api/v2/architect/flows endpoint directly, but that feels like a step backward since we want to use the CX as Code tooling for consistency. Anyone else hit this wall when trying to keep trace context in their IaC exports?