Skip to content

docs: Add env field to deployment manifest documentation#566

Open
promptless[bot] wants to merge 1 commit intomainfrom
promptless/flash-env-vars-in-manifest
Open

docs: Add env field to deployment manifest documentation#566
promptless[bot] wants to merge 1 commit intomainfrom
promptless/flash-env-vars-in-manifest

Conversation

@promptless
Copy link
Contributor

@promptless promptless bot commented Mar 23, 2026

Open this suggestion in Promptless to view citations and reasoning process

Updates the flash_manifest.json example in the deployment docs to show that environment variables defined on endpoints are persisted in the manifest. This clarifies how the env parameter is stored and deployed with your Flash application.

Trigger Events

runpod/flash PR #226: Fix: AE-2266: persist env vars in manifest and deployed endpoints

Promptless Research (6 files, 1 GitHub PR)

  • Reviewed runpod/flash#226
  • Viewed .long_term_context/product_knowledge/product_overview.md
  • Viewed .long_term_context/doc_workflow/client_instructions.md
  • Viewed .long_term_context/style/client_style_guide.md
  • Viewed flash/cli/env.mdx
  • Viewed flash/configuration/parameters.mdx
  • Viewed flash/apps/deploy-apps.mdx

Agent Response

I've reviewed PR #226 and created a documentation update.

Summary

PR #226 fixes a bug where environment variables defined on Flash endpoints weren't being persisted in the deployment manifest. Previously, when building the resource manifest, env variables were not being saved, which meant they weren't being passed to deployed endpoints.

Documentation Impact

The existing documentation in flash/configuration/parameters.mdx already correctly describes how the env parameter works. However, the example flash_manifest.json in the deployment docs didn't show the env field, which could confuse users trying to understand how their environment variables are stored and deployed.

Changes Made

I updated flash/apps/deploy-apps.mdx to:

  1. Added env to the manifest example - Shows how environment variables appear in the deployment manifest
  2. Updated the manifest description - Added "Environment variables for workers" to the list of what the manifest contains

This helps users understand that their endpoint environment variables are persisted in the deployment manifest and will be available to their workers after deployment.

Suggestion URL: https://app.gopromptless.ai/suggestions/a3c3fada-d737-4486-a282-b62c26b508e8


Tip: Leave inline comments with @Promptless on suggestion diffs in the Promptless dashboard for targeted refinements 💬

"imageName": "runpod/flash:latest",
"gpuIds": "AMPERE_16",
"workersMax": 3,
"env": {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Citation: PR #226 fixes env var persistence in the manifest. Changes in manifest.py show that the env dict is now extracted and included in the deployment config (excluding RUNPOD_API_KEY for security).
View source

@muhsinking muhsinking requested a review from deanq March 23, 2026 15:10
@mintlify
Copy link

mintlify bot commented Mar 23, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
runpod-docs 🟢 Ready View Preview Mar 23, 2026, 3:11 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants