Skip to content

Error when not discovering resources of a type when none exist. #1688

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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
zipkid opened this issue May 14, 2025 · 0 comments
Open

Error when not discovering resources of a type when none exist. #1688

zipkid opened this issue May 14, 2025 · 0 comments

Comments

@zipkid
Copy link
Contributor

zipkid commented May 14, 2025

These error appear when no resources were discovered, even when no resources of the specified type exist in the account.
{"time":"2025-05-14T11:29:59.478375188Z","level":"ERROR","source":"discovery.go:52","msg":"No tagged resources made it through filtering","version":"custom-build","job_type":"AWS/ElastiCache","region":"eu-west-1","arn":"arn:aws:iam:::role/Yace","account":"","err":"expected to discover resources but none were found"}

If no resources exist, maybe an Info log may be useful, but not an Error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant