---
title: "2026-08-07 argo workflow environment injection check"
description: "Checked infra_k8s Argo templates for automatic workflow ID environment injection."
image: "https://docs.virdx.dev/img/virdx-social-card.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.virdx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-08-07 argo workflow environment injection check

## Work Done

Inspected `virdx/infra_k8s` and its `current/argo-workflows/templates` manifests. The templates use `{{workflow.name}}` in output paths and shell text, but no workflow ID/name environment variable is declared. `run-image` only imports credential secrets and exports unrelated runtime configuration.

## Lessons Learned: Pitfalls

The Argo workflow name is available for template substitution, which is different from automatic environment injection. The repository contains no `workflow.uid`, `ARGO_WORKFLOW_*`, or workflow-ID env references.

## Lessons Learned: Improvements

When job code needs an identifier, explicitly add an env entry such as `name: ARGO_WORKFLOW_NAME` with `value: "{{workflow.name}}"`; use `{{workflow.uid}}` if the immutable workflow UID is required.

Source: https://docs.virdx.dev/knowledge/inbox/2026-08-07-infrastructure-argo-workflow-env-injection-check/index.mdx