Skip API token checks for configure commands #612
Merged
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.
Description
Fixes #611
The recent migration from Cobra to Kong introduced a regression where configuration validation was added to the
configurecommand itself, causing a chicken and egg scenario.Changes
Instead of adding the specific
configurecommands toCommandsNotRequiringToken, usedstrings.HasPrefix()to apply exemption to allconfigurecommands.Testing
go test ./...)go fmt ./...)Built local binary and successfully tested changes with previously failing
bk configure --org <org-slug> --token <token>command.Disclosures / Credits
Used Claude Code to validate the issue, identify the bug (and how it was introduced) and implement a guided fix.