docs: Document rolling releases for code-only deploys#628
docs: Document rolling releases for code-only deploys#628promptless[bot] wants to merge 19 commits intomainfrom
Conversation
Add documentation explaining that code-only changes now trigger rolling releases via source fingerprinting. Updated: - flash/cli/deploy.mdx: New section on rolling releases - flash/cli/build.mdx: Source fingerprinting step in build process - flash/apps/deploy-apps.mdx: Brief note on code change detection
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
There was a problem hiding this comment.
(Line 72)
Added section documenting rolling releases for code-only deploys based on PR #320, which implements source fingerprinting in cli/commands/build.py to detect code changes between deployments.
Source: runpod/flash#320
There was a problem hiding this comment.
(Line 52)
Added source fingerprinting step based on PR #320, which adds compute_source_fingerprint() function in cli/commands/build.py.
Source: runpod/flash#320
| 3. **Provision**: Creates or updates Serverless endpoints. | ||
| 4. **Configure**: Sets up environment variables and service discovery. | ||
|
|
||
| When you deploy updates to an existing application, Flash automatically triggers a rolling release if your source code has changed. Flash computes a fingerprint of your source files during build, so code-only changes (without resource configuration changes) still result in updated endpoints. |
There was a problem hiding this comment.
Added note about code change detection based on PR #320, which injects _FLASH_SOURCE_FINGERPRINT into resource env in cli/utils/deployment.py to trigger updates on code changes.
Source: runpod/flash#320
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
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.) |
1 participant
Open this suggestion in Promptless to view citations and reasoning process
Adds documentation explaining that Flash now automatically triggers rolling releases when source code changes, even without resource configuration changes. The build phase computes a source fingerprint to detect code changes between deployments.
Trigger Events
Tip: Set up a GitHub Issues trigger in Projects to enable @Promptless mentions in issues 🐙