Switch 'kubectl cost predict' to use /prediction/speccost #143
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.
DO NOT RELEASE UNTIL v1.101 IS RELEASED
What does this PR change?
See release note.
I apologize to reviewers for the intense refactoring. Display options are now substantially clearer as a nice side effect, e.g. Allocation options no longer pollute Asset commands.
How does this PR impact users? (This is the kind of thing that goes in release notes!)
kubectl cost predictto use the new/prediction/speccostAPI introduced in https://github.com/kubecost/kubecost-cost-model/pull/1226 and https://github.com/kubecost/kubecost-cost-model/pull/1229. This changes the output format a bit. Diffs now include usage information (if available) by default. See updatedkubectl cost predict --helpfor more information.How was this PR tested?
Have you made an update to documentation?