You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i'm one of the authors of tools found here: https://k14s.io. ytt -f . | kbld -f - | kapp -y deploy -a app1 -f - is my most common combination of these tools. that pipeline templates configuration, builds images, and deploys to k8s.
i am interested in allowing folks to validate their resources seamlessly as part of command pipeline so that it looks something like this: ytt -f . | VALIDATOR -f- | kbld -f - | kapp -y deploy -a app1 -f - where VALIDATOR is a standalone tool that validates k8s YAML. for the pipeline to work nicely; however, such tool needs to:
(1) support dealing with YAML stream (multi doc)
(2) support propagating input as output (print YAML back for next steps)
what do you think about changing yamlvalidate to allow above use case? both points i believe would be easy to implement and do not go against spirit of this project.
The text was updated successfully, but these errors were encountered:
cppforlife
changed the title
multi-doc output after successful validation
integration with k14s's ytt, kapp
Sep 20, 2019
i'm one of the authors of tools found here: https://k14s.io.
ytt -f . | kbld -f - | kapp -y deploy -a app1 -f -
is my most common combination of these tools. that pipeline templates configuration, builds images, and deploys to k8s.i am interested in allowing folks to validate their resources seamlessly as part of command pipeline so that it looks something like this:
ytt -f . | VALIDATOR -f- | kbld -f - | kapp -y deploy -a app1 -f -
where VALIDATOR is a standalone tool that validates k8s YAML. for the pipeline to work nicely; however, such tool needs to:(1) support dealing with YAML stream (multi doc)
(2) support propagating input as output (print YAML back for next steps)
what do you think about changing yamlvalidate to allow above use case? both points i believe would be easy to implement and do not go against spirit of this project.
The text was updated successfully, but these errors were encountered: