fix: enrichment redeploy loop and lowercase env name

[TerrifiedBug]

Summary

• Fix infinite redeploy loop: pipeline.get was comparing YAML without enrichment transforms against deployed YAML that had them baked in — they could never match, so "pending deploy" always showed after any enrichment-enabled deploy.
• Fix missing "pending deploy" on enrichment toggle: When toggling enrichMetadata ON, the editor didn't detect a configuration change because both comparison sides lacked enrichment.
• Lowercase environment name in enrichment metadata (e.g. "production" instead of "Production").

Root cause

pipeline.get (editor/detail view) was missing the enrichment parameter in its call to generateVectorYaml(). The pipeline.list endpoint already had this fix, but pipeline.get was missed.

Changes

• src/server/routers/pipeline.ts: Add name to environment select, version to latestVersion select, and pass enrichment to generateVectorYaml() in pipeline.get
• src/lib/config-generator/yaml-generator.ts: Lowercase environment name in VRL enrichment source

Test plan

• Enable enrichment on a deployed pipeline → editor shows "pending deploy"
• Deploy with enrichment → editor no longer shows "pending deploy"
• Verify enrichment metadata has lowercase environment name
• Toggle enrichment OFF on deployed pipeline → editor shows "pending deploy"

[greptile-apps]

Greptile Summary

This PR fixes two related bugs in the pipeline editor's "pending deploy" detection and corrects the casing of environment names in enrichment metadata.

• Root cause fixed: pipeline.get was calling generateVectorYaml() without the enrichment parameter, so the YAML it generated for comparison never matched the deployed YAML (which had enrichment transforms baked in), causing a perpetual "pending deploy" state. The fix mirrors the already-correct pipeline.list implementation: select environment.name and latestVersion.version from the DB, construct an enrichment object when pipeline.enrichMetadata is true, and pass it through to generateVectorYaml().
• Toggle detection fixed: Because pipeline.get now correctly reflects enrichMetadata state, toggling enrichment ON on a previously non-enriched pipeline is now detectable (the generated YAML diverges from the stored YAML).
• Lowercase environment name: .toLowerCase() is applied inside generateVectorYaml() before the environment name is embedded in the VRL source. Pipelines that were deployed with an uppercase environment name will now show "pending deploy" until re-deployed with the corrected casing — this is the expected and documented behaviour.

Confidence Score: 5/5

• Safe to merge — targeted bug fix with no logic regressions or security concerns.
• The changes are minimal and tightly scoped. The new pipeline.get enrichment logic is a direct copy of the already-shipped pipeline.list pattern, making the two code paths consistent. The .toLowerCase() change is a one-liner with a clear, intentional side-effect (existing deployments with uppercase names will surface as needing a redeploy). No security-sensitive paths, no new data exposure, no missing middleware.
• No files require special attention.

Important Files Changed

Filename	Overview
src/server/routers/pipeline.ts	Adds name to environment select and version to latestVersion select in pipeline.get, then constructs and passes an enrichment object to generateVectorYaml() — mirroring the already-correct pipeline.list implementation. Fixes the infinite "pending deploy" loop and the missed change detection on enrichment toggle.
src/lib/config-generator/yaml-generator.ts	One-line change: applies .toLowerCase() to enrichment.environmentName before embedding it in the VRL source. Ensures the environment name is stored in lowercase (e.g. "production" vs "Production") in enrichment metadata. Pipelines previously deployed with an uppercase name will correctly show "pending deploy" until re-deployed.

Sequence Diagram

sequenceDiagram
    participant Client
    participant pipeline.get
    participant DB (Prisma)
    participant generateVectorYaml

    Client->>pipeline.get: query({ id })
    pipeline.get->>DB (Prisma): findUnique(pipeline)<br/>include environment { name } + nodes + edges
    DB (Prisma)-->>pipeline.get: pipeline (with environment.name)
    pipeline.get->>DB (Prisma): findFirst(latestVersion)<br/>select { configYaml, logLevel, version }
    DB (Prisma)-->>pipeline.get: latestVersion (with .version)

    alt enrichMetadata = true
        pipeline.get->>pipeline.get: enrichment = { environmentName, pipelineVersion }
    else enrichMetadata = false
        pipeline.get->>pipeline.get: enrichment = null
    end

    pipeline.get->>generateVectorYaml: (nodes, edges, globalConfig, enrichment)
    note over generateVectorYaml: if enrichment: inject remap transform<br/>with environmentName.toLowerCase()
    generateVectorYaml-->>pipeline.get: currentYaml

    pipeline.get->>pipeline.get: hasConfigChanges = (currentYaml !== latestVersion.configYaml)
    pipeline.get-->>Client: { ...pipeline, hasConfigChanges }

Loading

_{Last reviewed commit: d8af578}