fix API related CMDS crash on wrong apikey #486
Merged
Conversation
This file contains 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
Co-authored-by: Harsh Thakur <[email protected]>
RealHarshThakur
approved these changes
Dec 23, 2024
fernando-villalba
approved these changes
Dec 23, 2024
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.
fixes: #464
Previously, the loadConfig function always attempted to fetch
regionsToFeature(which calls the GET regions API) , even for commands that didn’t need this data (e.g.,civo apikey remove).If the saved API key was invalid, this API call would fail, causing the entire command to break.
By introducing the
SkipAPIInitializationflag, commands can signal that API-dependent logic should be skipped, avoiding unnecessary API interactions for the cmds that dont require interaction with API