Revert "feat: Update openapi contracts to include onConflict parameter for restore (#655)" - #656
Open
devanbenz wants to merge 1 commit into
Open
Revert "feat: Update openapi contracts to include onConflict parameter for restore (#655)"#656devanbenz wants to merge 1 commit into
devanbenz wants to merge 1 commit into
Conversation
…r for restore (#655)" This reverts commit d90ba20. Bucket conflict handling for `influx restore --on-conflict` is now implemented entirely client-side in the CLI (influxdata/influx-cli#583), so the server never receives an onConflict parameter and the spec change is no longer needed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Reverts #655.
Bucket conflict handling for
influx restore --on-conflictis now implemented entirely client-side in the CLI (see influxdata/influx-cli#583): the CLI checks bucket existence itself and resolveserror/skip/replacewithout any server involvement. The server never receives anonConflictparameter, so this spec addition is unused and can be removed.