You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: