Skip to content

Handle relation resolution when the same kind from different groups is referenced #11

@vertex451

Description

@vertex451
How would you solve the multiple kinds for different group errors? E.g. imagine a resource that has a ThingRef but Thing is provied via group A and group B - how would you know which would be the right kind to use for the relation?

P.S. I kubectl-style approach is partially implemented, but we need to verify if it works.

Hints:
openmfp/kubernetes-graphql-gateway#303

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions