Skip to content
New issue

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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tool should not fail on a discovered cluster that does not exist #113

Closed
mikouaj opened this issue Aug 3, 2022 · 0 comments 路 Fixed by #117
Closed

Tool should not fail on a discovered cluster that does not exist #113

mikouaj opened this issue Aug 3, 2022 · 0 comments 路 Fixed by #117
Assignees
Labels
bug Something isn't working

Comments

@mikouaj
Copy link
Member

mikouaj commented Aug 3, 2022

Community Note

  • Please vote on this issue by adding a 馃憤 reaction
    to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do
    not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Debug Output

N/A

Panic Output

N/A

Steps to Reproduce

  1. Create new GKE cluster
  2. Wait and ensure that GKE Cluster is visible in Assent Inventory
  3. Delete GKE cluster
  4. Run the tool

Expected Behavior

The tool produces warning.
If there is more than one cluster to process, the remaining clusters are checked.

Actual Behavior

The tool produces an error and exists with system code 1.
If there are multiple clusters to check, there is a high chance that not all of them will be processed.

References

N/A

@mikouaj mikouaj added the bug Something isn't working label Aug 3, 2022
@mikouaj mikouaj self-assigned this Aug 8, 2022
@mikouaj mikouaj linked a pull request Aug 8, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant