feat!: flash deploy auto builds, automatic app & env management#178
Merged
feat!: flash deploy auto builds, automatic app & env management#178
Conversation
DeJayDev
approved these changes
Feb 5, 2026
Member
DeJayDev
left a comment
There was a problem hiding this comment.
fantastic, thank you - just these but not a hard blocker
Co-authored-by: Dj Isaac <contact@dejaydev.com>
Co-authored-by: Dj Isaac <contact@dejaydev.com>
jhcipar
approved these changes
Feb 5, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR introduces a streamlined deployment workflow by consolidating the build and deploy steps into a single flash deploy command, while also reorganizing environment management commands under a new flash env namespace. The changes eliminate manual app and environment creation by automatically handling these resources based on flags and discovery.
Changes:
- Unified build and deployment into
flash deploycommand with automatic app/environment creation - Moved environment management from
flash deploy <subcommand>toflash env <subcommand> - Refactored flag naming from
--app-nameto--appfor consistency
Reviewed changes
Copilot reviewed 10 out of 11 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| tests/unit/cli/test_env.py | New test suite covering environment management commands (list, create, info, delete) |
| tests/unit/cli/test_deploy.py | Updated tests for new unified deploy command with automatic environment resolution |
| tests/unit/cli/test_apps.py | Updated flag names from --app-name to --app |
| src/runpod_flash/cli/utils/skeleton_template/README.md | Updated deployment examples to reflect new single-command workflow |
| src/runpod_flash/cli/utils/deployment.py | Updated error message to reference flash deploy instead of flash build |
| src/runpod_flash/cli/main.py | Restructured command registration: added flash deploy as direct command and flash env as subcommand group |
| src/runpod_flash/cli/commands/env.py | New environment management module with list, create, info, delete commands |
| src/runpod_flash/cli/commands/deploy.py | Completely rewritten to handle build + deploy workflow with automatic environment resolution |
| src/runpod_flash/cli/commands/build.py | Refactored to extract core build logic into run_build() for reuse by deploy command |
| src/runpod_flash/cli/commands/apps.py | Updated flag name from --app-name to --app |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
deanq
approved these changes
Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
currently, you have to do a multi-step process of creating a build archive and
flash deploy sendto send it to an environment. this is mostly just busywork.This PR focused on removing all that friction and presenting with a simple monolithic
flash deploycommand that will:we default to the current directory name for the app name. If the app has a single environment, it will just be automatically used to deploy. If no environments exist, a
productionenvironment will be created. If multiple exist, you are asked to specify one. specifying an environment or app with--envor--appthat doesnt exist will automatically create it.flash deployalso had a bunch of environment management sub-commands, these have been moved toflash env. (flash deploy newhas been moved toflash env createto be more in line with other commands).