We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What happened: When running the plan status command via the CLI, the output isn't sorted in any way and can change each time it's run.
plan status
What you expected to happen: Consistent output for this command.
The ordering isn't necessarily important (although it would make sense if the deploy plan was always first), but I think it needs to be consistent.
deploy
How to reproduce it (as minimally and precisely as possible):
Run kubectl kudo plan status --instance my-instance a couple of times, the order of the plans as they're displayed changes.
kubectl kudo plan status --instance my-instance
The text was updated successfully, but these errors were encountered:
yankcrime
Successfully merging a pull request may close this issue.
What happened:
When running the
plan status
command via the CLI, the output isn't sorted in any way and can change each time it's run.What you expected to happen:
Consistent output for this command.
The ordering isn't necessarily important (although it would make sense if the
deploy
plan was always first), but I think it needs to be consistent.How to reproduce it (as minimally and precisely as possible):
Run
kubectl kudo plan status --instance my-instance
a couple of times, the order of the plans as they're displayed changes.The text was updated successfully, but these errors were encountered: