Feature Description

Currently when configuring a related resource, the agent assumes that the reference always needs to exist in an object (i.e. if the configured path is not resolvable, an error is raised).

However there can be cases where the related resource is entirely optional. This currently cannot be expressed with a PublishedResource.

Proposed Solution

I propose that we add a new optional: <bool> field to each related resource in a PublishedResource.

Alternative Solutions

No response

Want to contribute?

• I would like to work on this issue.

Additional Context

No response