Uh oh!
There was an error while loading. Please reload this page.
Set app description correctly on create only - #182
Merged
Conversation
…vements - Change towerfile desc. to Option<String> to distinguish absence and explicit empty - Add ApiCreateError for more accurate error reporting on app createion - Add UnexpectedApiResponse error to prevent silent description synchronization skip - Simplify error conversion in `ensure_app_exists`
Change from diff-checking approach to "latest wins" semantics; - Always update description on deploy when present (no comparison) - Skip update for empty/None (preserves server state) - Remove spinner and entity validation (simpler, more resilient)
bradhe
approved these changes
Jan 23, 2026
bradhe
left a comment
Contributor
There was a problem hiding this comment.
This is really great, thanks for taking care of this @burakdede! I'll leave this open in case there's any modifications you want to make, but will merge it over the weekend!
Uh oh!
There was an error while loading. Please reload this page.
bradhe added a commit
that referenced
this pull request
Aug 14, 2026
* Revert "fix(schedules): restore direct update semantics and strengthen parsing tests (#205)" This reverts commit 58456c5. * Revert "Set app description correctly on create only (#182)" This reverts commit a3307b0. * Revert "Add new `--follow` mode for `tower apps logs` with resilient streaming and tests (#171)" This reverts commit fd79baf. * Revert "fix(cli-help): clarify usage/examples for apps, schedules, secrets (#169)" This reverts commit 7f6d0a7. * Revert "Fix: better handling of non-iterable dbt result objects and selectable dbt commands (#143)" This reverts commit 6239423. * Add --follow mode to tower apps logs * Add positional schedule id handling * Make app description create-only * Improve subcommand help text * Handle non-iterable dbt results and selector targeting * Add integration coverage for run cancel, follow mode, and app descriptions * Apply black formatting * Fix warning handling in follow mode and stream error formatting
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This fixes the description issue reported #166.
As evident from the commits I changed my mind quite a bit about where, when
descriptionmetadata should be applied eventually settled to scope it to only create flows and applied optional semantics of the field. (deployseemed too critical and applied too frequent to constantly sync this)High level changes;
descriptionto the API’sshort_descriptionon create (including deploy --create), and deploy no longer updates description for existing apps.