Skip to content

docs: Rename flash run to flash dev and document implicit endpoint resolution#619

Open
promptless[bot] wants to merge 3 commits intomainfrom
promptless/flash-cli-dev-rename-endpoint-resolution
Open

docs: Rename flash run to flash dev and document implicit endpoint resolution#619
promptless[bot] wants to merge 3 commits intomainfrom
promptless/flash-cli-dev-rename-endpoint-resolution

Conversation

@promptless
Copy link
Copy Markdown
Contributor

@promptless promptless Bot commented Apr 24, 2026

Open this suggestion in Promptless to view citations and reasoning process

Updates Flash CLI documentation to reflect the flash run to flash dev rename, and documents the new implicit endpoint resolution feature that allows calling deployed endpoints from scripts using FLASH_APP and FLASH_ENV environment variables.

Trigger Events


Tip: Worried about broken links? Ask Promptless to find and fix them automatically 🔗

- Rename flash/cli/run.mdx to flash/cli/dev.mdx
- Update all references from flash run to flash dev across docs
- Document new implicit endpoint resolution feature with FLASH_APP and FLASH_ENV environment variables
- Add note that flash run is a hidden alias for backward compatibility
Comment thread flash/cli/dev.mdx
@@ -1,32 +1,36 @@
---
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

PR #324 renamed flash run to flash dev with flash run as a hidden alias for backward compatibility. The CLI registration in main.py:42-43 shows both commands pointing to the same handler.

Source: runpod/flash#324

return {"classification": result}
```

## Call deployed endpoints from scripts
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

PR #324 introduced implicit endpoint resolution via FLASH_APP and FLASH_ENV environment variables. The flash_context.py:17-37 module reads these env vars, and client.py:236-275 uses them in the @remote wrapper decision tree to route calls through the Flash sentinel service.

Source: runpod/flash#324

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

these environment variables should only be used to override (e.g. running the script in a different cwd and need to target the same app as before)

@mintlify
Copy link
Copy Markdown

mintlify Bot commented Apr 24, 2026

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

Project Status Preview Updated (UTC)
runpod-docs 🟢 Ready View Preview Apr 24, 2026, 10:48 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@promptless
Copy link
Copy Markdown
Contributor Author

promptless Bot commented Apr 26, 2026

Just a reminder: If you'd like me to act on any feedback you have via Github comments, just type @Promptless in your suggestion and I'll get right on it! (I won't show up in the user dropdown, but I'll process any request that has @Promptless in the comment body.)

Copy link
Copy Markdown
Contributor

@KAJdev KAJdev left a comment

Choose a reason for hiding this comment

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

some clarifications needed

@KAJdev
Copy link
Copy Markdown
Contributor

KAJdev commented Apr 26, 2026

@Promptless the environment variables should only be used when they need to be overridden. for example, if you moved the script to a different directory the resolved app name would be different. if you still want to target the original app you need to set FLASH_APP.

Updates the "Call deployed endpoints from scripts" section to explain that
Flash automatically resolves app context from project structure. FLASH_APP
and FLASH_ENV are now documented as override mechanisms for special cases,
such as when a script is moved to a different directory.

Addresses reviewer feedback from PR #619.
@promptless
Copy link
Copy Markdown
Contributor Author

promptless Bot commented Apr 26, 2026

Thanks for the feedback @KAJdev! I've updated the documentation to clarify that:

  1. Flash automatically resolves app context from the project structure — users don't need to set environment variables in most cases
  2. FLASH_APP and FLASH_ENV are documented as override mechanisms for special cases (e.g., when a script is moved to a different directory and you want to continue targeting the original app)

The "Set the environment context" section has been replaced with an "Override the resolved context" section that explains when and why you'd use these environment variables.

@KAJdev
Copy link
Copy Markdown
Contributor

KAJdev commented Apr 26, 2026

@Promptless also, the example should probably be calling within the same script and then that you can also import in another script

Show calling the endpoint within the same script first, then importing
from another script as an alternative pattern.
@promptless
Copy link
Copy Markdown
Contributor Author

promptless Bot commented Apr 26, 2026

Thanks for the feedback @KAJdev! I've updated the example section to show:

  1. Calling within the same script — the endpoint definition with asyncio.run() at the bottom of the same file
  2. Importing from another script — as an alternative pattern for separate files

The changes have been pushed to this PR.

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.

1 participant