feat: expose DUA Agentex credentials to Redash

[yianni]

Summary

Exposes the two Agentex credentials required by DUA and bumps the chart from 3.0.12 to 3.0.13.

Changes

• Maps duaAgentexAPIKey to DUA_AGENTEX_API_KEY.
• Maps duaAgentexAccountId to DUA_AGENTEX_ACCOUNT_ID.
• Supports both chart-managed and existing Redash secrets.

This is additive, but releases using an existing secret must add both keys before upgrading to 3.0.13.

Related

• Application: scaleapi/redash#128
• Deployment: scaleapi/Terracode-Infra#8398
• Tracking: PLA4-40261

Greptile Summary

This PR adds two new Agentex credentials (DUA_AGENTEX_API_KEY, DUA_AGENTEX_ACCOUNT_ID) to the Redash Helm chart and bumps the version to 3.0.13. The implementation follows the exact same pattern as the existing EGP credentials — values stored in the chart-managed Secret when no existingSecret is configured, and env vars injected conditionally using the or <value> .Values.redash.existingSecret guard.

• New duaAgentexAPIKey and duaAgentexAccountId fields added to values.yaml with empty defaults; corresponding keys written to templates/secrets.yaml when the chart manages the Secret.
• Two new env-var blocks in templates/_helpers.tpl expose the credentials to the Redash container, consistent with the existing EGP credential pattern.
• As documented in the PR description, deployments using an existingSecret must add both new keys to that secret before upgrading to 3.0.13.

Confidence Score: 5/5

Additive chart change that mirrors an already-proven credential pattern; no existing behavior is altered.

All four files are updated consistently. The new keys follow the identical guard pattern used for the EGP credentials, the chart-managed Secret template correctly includes the new keys, and the env-var blocks in _helpers.tpl are properly conditioned. No logic is changed for existing deployments that don't set the new values.

No files require special attention.

Important Files Changed

Filename	Overview
Chart.yaml	Chart version bumped from 3.0.12 to 3.0.13 to reflect the new credentials addition.
values.yaml	Two new optional values added (duaAgentexAPIKey, duaAgentexAccountId) with empty-string defaults; follows existing EGP key conventions.
templates/secrets.yaml	New keys added to chart-managed Secret; correctly guarded by not .Values.redash.existingSecret via the template's outer conditional.
templates/_helpers.tpl	Two new env-var blocks injected following the identical or .Values.redash.duaAgentex* .Values.redash.existingSecret guard pattern used by existing EGP keys.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Helm Install / Upgrade] --> B{existingSecret set?}
    B -- No --> C[secrets.yaml creates\nmanaged Secret\nwith duaAgentexAPIKey\n& duaAgentexAccountId]
    B -- Yes --> D[Operator-managed\nexternal Secret\nmust already contain\nboth keys]
    C --> E[_helpers.tpl injects\nDUA_AGENTEX_API_KEY\nif value OR existingSecret]
    D --> E
    E --> F[_helpers.tpl injects\nDUA_AGENTEX_ACCOUNT_ID\nif value OR existingSecret]
    F --> G[Redash Pod\nreads env vars\nDUA_AGENTEX_API_KEY\nDUA_AGENTEX_ACCOUNT_ID]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Helm Install / Upgrade] --> B{existingSecret set?}
    B -- No --> C[secrets.yaml creates\nmanaged Secret\nwith duaAgentexAPIKey\n& duaAgentexAccountId]
    B -- Yes --> D[Operator-managed\nexternal Secret\nmust already contain\nboth keys]
    C --> E[_helpers.tpl injects\nDUA_AGENTEX_API_KEY\nif value OR existingSecret]
    D --> E
    E --> F[_helpers.tpl injects\nDUA_AGENTEX_ACCOUNT_ID\nif value OR existingSecret]
    F --> G[Redash Pod\nreads env vars\nDUA_AGENTEX_API_KEY\nDUA_AGENTEX_ACCOUNT_ID]

Loading

_{Reviews (1): Last reviewed commit: "feat: DUA agentex secret env mappings (D..." | Re-trigger Greptile}