►
From YouTube: Carvel ytt Validations Intro with John Ryan
Description
We are looking for feedback on the ytt validations proposal! John Ryan, maintainer of Carvel, goes over the need for validations then walks through the two key sections of the proposal to focus on, gives prompts to make clear what would instantly valuable feedback, and mechanisms to give us feedback.
A
A
Our
goal
is
to
solve
the
right
problem
in
the
right
way
being
able
to
get
and
fold
in
your
perspective
into
our
efforts,
increases
our
chances
of
doing
just
that.
So,
thank
you
so
in
this
recording
I'm
going
to
give
you
the
background
that
you
need
to
quickly
jump
into
digesting
and
critiquing
this
proposal,
so
we'll
start
by
validating
the
need
for
validations
or
motivating
it
by
working
through
an
example.
A
A
It's
rather
detailed,
so
you
don't
want
to
have
to
read
it
all
in
order
to
provide
useful
feedback,
and
you
won't
have
to
so
I'll
point
you
to
the
two
key
sections
in
the
proposal
that
you
should
focus
on.
First
I'll
give
you
some
prompts
to
make
clear
what
would
be
instantly
valuable
feedback
and
finally
I'll
share
with
you
two
key
mechanisms
you
can
use
to
give
us
feedback.
A
A
So
I
know
it's
a
little
contrived
here,
but
we're
just
trying
to
illustrate
a
point.
This
won't
work
if
we
attempt
to
apply
this
to
a
cluster,
so
it's
valuable
to
know
that
my
input
is
of
the
right
type.
That
is,
that
it's
well
formed.
So
in
ytt
this
is
really
easy.
So,
instead
of
just
naming
a
data
value,
we
declare
a
variable
of
a
specific
type.
A
A
Nice,
okay,
so
now
imagine
further
that
in
your
system
you
know
that
if
the
user
configures
more
than
four
instances
of
this
deployment,
it's
actually
going
to
lead
to
performance
problems.
Now
it's
a
rough
way
to
learn
to
deploy
a
with
a
larger
value
and
discover
that
it's
a
problem.
So
what
if?
Instead
you
could
put
bumpers
on
those
values
and
that's
the
point
of
a
validation
to
ensure
that
the
inputs
are
not
just
well-formed
but
they're,
also
within
tolerances.
A
A
A
A
A
A
A
Now
we
haven't
implemented
it,
so
these
annotations
won't
be
interpreted,
but
this
illustrates
all
of
what
ytt
would
do.
What
will
the
validation
features
do?
Well,
there's
two
sections
that
you
should
read
the
others
are
good
detail,
but
these
are
the
two
most
important
ones:
they
define
the
problem
we're
solving.
A
A
There's
a
list
here
of
scenarios.
We're
designing
the
feature
around
great
feedback
here
would
include
identifying
any
use
cases
you'd
expect
to
see,
but
are
not
listed
here.
Also,
you
can
pick
a
use
case
that
piques
your
interest
and
ask
yourself
in
what
ways
is
the
proposed
solution
seem
awkward
or
how
about
the
solution
be
better?
A
A
This
is
exactly
the
annotation
we
added
in
our
example
to
declare
our
validation.
What
the
proposal
is
trying
to
say
is
that
this
annotation
schema
validation
is
a
way
to
record
the
need
for
the
resulting
data
value
to
have
the
actual
validation
attached
to
it,
and
that
is
it's
annotated
with
an
assert
validate.
A
A
This
view
of
the
proposal
is
really
useful
because
it's
rendered
and
it's
easy
to
navigate
around
using
the
links
if
you're
not
familiar
github's
markdown
viewer
includes
a
navigation
drop-down
here,
and
the
selection
is
automatically
set
to
wherever
you're
at
in
the
document.
Right
now.
The
best
way
to
leave
feedback
is
actually
in
the
pr
itself.