Preserve config name when updating existing snapshot#44
Merged
fullstackjam merged 1 commit intomainfrom Apr 22, 2026
Merged
Conversation
…ired" When publishing updates to an existing config, the CLI skipped the name/description prompt and sent an empty name in the PUT body. The API requires name for both POST and PUT, so it rejected the request with status 400. Now we fetch the existing config's name from the API before the PUT and fall back to the slug if the fetch fails. https://claude.ai/code/session_01J6FVyNhP1uSiqHbMUYHo1i
|
👋 Thanks for opening this pull request! Before merging:
@fullstackjam will review this soon. Thanks for contributing! 🚀 |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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
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.
What does this PR do?
When publishing a snapshot to update an existing config, fetch the remote config to preserve its name before sending the PUT request.
Why?
The PUT endpoint requires a
namefield. When updating an existing config (rather than creating a new one), we need to preserve the existing config's name. This change fetches the remote config to get the current name, falling back to the target slug if the fetch fails or returns an empty name.Testing
go vet ./...passes./openboot --dry-runwhen updating an existing configNotes for reviewer
The change gracefully handles fetch failures by falling back to using the target slug as the config name, ensuring the update can proceed even if the remote config fetch fails.
https://claude.ai/code/session_01J6FVyNhP1uSiqHbMUYHo1i