Open flynntsang opened 3 days ago
I had tried to do this a while back, but ended up with the spec being very poluted regardless of type (you can actually see this bleeding between machine / agent / agent-template-types already).
This might be due to extra fields being allowed on resources. Need to experiment to see if this solves the problem. Otherwise, we could work around this by breaking out the schema matching rules.
ie foo.reference.eidolon.yaml
vs foo.agent.eidolon.yaml
vs foo.machine.eidolon.yaml
To do:
kind: Reference
spec: > value: