Skip to content

Add error logging to extractor #427

Description

@teabot

What problem are you facing?

When selectors fail to resolve values correctly (see crossplane-contrib/provider-upjet-aws#118), it is hard to diagnose the probable issue.

How could Upjet help solve your problem?

It would be beneficial to add some additional logging in extractor.go to log errors, which are currently swallowed silently:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions