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
When running a check against a CloudWatch Log Group, I receive the error:
RuntimeError:
Found multiple CloudWatch Log Groups.
The log group I'm trying to check is named similarly to /my-environment/my-app. Not able to post the actual log group names due to confidentiality concerns.
The error reports that it finds the log group I want to check, but ALSO a log group named /my-environment/my-app-deploy.
I have been able to duplicate this error with other environments that have similar names.
I realize that this is the default behavior of the describe_log_groups api call, since it's actually doing a prefix lookup. But, since this is a singular resource, rather than a plural one, I would expect it to only return a match on the specific name.
Possible Solution
Add limit: 1 to the call doing the lookup by default to only return the first match.
The text was updated successfully, but these errors were encountered:
Describe the problem
When running a check against a CloudWatch Log Group, I receive the error:
RuntimeError:
Found multiple CloudWatch Log Groups.
The log group I'm trying to check is named similarly to
/my-environment/my-app
. Not able to post the actual log group names due to confidentiality concerns.The error reports that it finds the log group I want to check, but ALSO a log group named
/my-environment/my-app-deploy
.I have been able to duplicate this error with other environments that have similar names.
I realize that this is the default behavior of the
describe_log_groups
api call, since it's actually doing a prefix lookup. But, since this is a singular resource, rather than a plural one, I would expect it to only return a match on the specific name.Possible Solution
Add
limit: 1
to the call doing the lookup by default to only return the first match.The text was updated successfully, but these errors were encountered: