The parser could enforce a EDF schema where only known keys are accepted inside [annotations], [env], etc. Then misplaced top-level keys would fail fast instead of silently being ignored or interpreted under the wrong table.
Example error:
[annotations]
mounts = ["/capstor/.../workdir:/workdir"]
Parser then does not interpret mount to be top-level but rather an annotation
Instead, we should fail early or provide a warning when reserved top-level keys such as mounts, image, or other top level entry appear inside a table like [annotations] or [env].
The parser could enforce a EDF schema where only known keys are accepted inside [annotations], [env], etc. Then misplaced top-level keys would fail fast instead of silently being ignored or interpreted under the wrong table.
Example error:
[annotations]
mounts = ["/capstor/.../workdir:/workdir"]
Parser then does not interpret mount to be top-level but rather an annotation
Instead, we should fail early or provide a warning when reserved top-level keys such as mounts, image, or other top level entry appear inside a table like [annotations] or [env].