Fix panic in analyze command if cluster is not found #1697
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: #1693
Thanks @masih for reporting
Type of change
Please select one of the options below.
Discussion
Testing
Did a local test with the fix:
$ ./dist/kubectl-fdb_darwin_arm64/kubectl-fdb analyze tabaluga Error: could not fetch cluster information for: default/tabaluga, error: foundationdbclusters.apps.foundationdb.org "tabaluga" not found
Documentation
Follow-up