Skip to content

Suppress logging when URI for a relation cannot be constructed #14

Closed
@iainelder

Description

In my first run of Inspector (#11) I saw this warning about billing alarm.

[2021-03-20 14:23:25,481] {resource.py:65} WARNING - Missing target for relation arn:aws:cloudwatch:us-east-1:01234567890:alarm:BillingAlert fires-on [metrics/us-east-1/None/None/] (1)

It turns out that it's not actually a problem with the alarm configuration but a limitation of introspector when deriving relations from the resources.

@gsoltis commented:

For some of the calculated relations, as you can see from the None token, we don't know the correct thing to relate them to (or it might not exist). These shouldn't actually be warnings at this point. If we can't construct the URI for a relation, we should not then be logging that we can't find the target...

(Please correct me if I have mixed this one up. It seems to be about an implementation detail that I don't understand yet.)

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions