Validate resulting YAML/JSON against JSONschema
Describe the bug Some workflows generated by the library are not valid. E.g. workflows with name over 63 characters in length. To Reproduce Create a workflow with a name 64 characters long. Expected behaviour Receive an error when setting name so be longer than 63 characters.
Screenshots
This workflow was submitted via the DSL and failed only when run.
Is this a requirement imposed by Kubernetes, rather than Argo? Perhaps it's a limitation of RFC1123? There is some K8S documentation on this but it has to do with labels/selectors.
Regardless of where this limitation comes from, this workflow shouldn't have been accepted in a submit call. I hope these things are covered in the official JSONschema...