►
From YouTube: WG API Expression Bi-Weekly Meeting for 20210803
Description
WG API Expression Bi-Weekly Meeting for 20210803
A
A
B
Okay,
so
just
to
give
a
brief
background
about
open
api
v3,
so
why,
first
of
all,
why
do
we
need
v3?
First
of
all,
custom
resource
definitions
crds
they
by
default?
They
have
vt
validation,
schemas
and
some
of
these
fields
are
not
v3.
Fields
are
not
supported
when
we
we
end
up
printing
them
and
when
we
publish
v2,
so
some
of
those
information
gets
lost
and
when
it
gets
passed
to
things
like
service,
I
apply
cube
cuddle.
B
Some
we
lose
some
critical
information
that
will
be
valuable
to
keep,
so
some
of
these
fields
include
mostly
value
validations
like
any
of
one
of
inter
strings.
I
know
there
have
been
a
couple
bugs
around
that
I've
seen
in
open
source,
I'm
also
nullable,
so
I
just
want
to
give
a
quick
demo
in
terms
of
what
we
have
so
far
with
open
api
v3.
B
So
what
we
decided
for
now
was
to
just
split
by
group
which
means
that
right
now,
so
let
me
just
show
the
open
ipiv2,
so
the
original
endpoint
was
open
at
v2,
our
training
endpoint
for
open,
ipi
v3,
and
this
endpoint
right
now
it
serves
a
list
of
groups
that
we
have
for
the
other
api.
So
essentially
now
we
don't
need
to,
but
we're
not
really
sure
how
we
want
to
handle
aggravating
the
entire
spec.
B
But
right
now
we're
able
we're
like
our
goal
is
to
be
able
to
access
each
individual
group
separately
and
get
only
the
resources
schemas
specifically
for
the
group,
rather
than
getting
it
for
all
the
groups
together.
So,
for
example,
we
have
we
can
even
access
something
like
the
version
and
you'll
get
the
opening
pass
back.
Just
for
that
one
particular
path.
B
B
B
A
B
B
A
B
B
A
A
I
moved
the
remaining
stuff
from
our
ssa
g8
document
into
our
work
items
again
and
put
our
notes
into
j
doc,
because
we
are
past
code
freeze
and
seems
like
we
made
it
this
time,
but
we
still
have
some
leftover
stuff.
We
in
our
document-
and
I
wanted
to
go
over
what
of
that.
We
want
to
work
on
and
oh.
B
B
B
A
D
A
A
B
A
D
Yeah
this
was
from
a
while
ago.
I
had
put
together
a
small
document
that
I
don't
know
I
can
link
to
there,
but
there's
probably
not
a
whole
lot
of
work
to
be
done
on
that
front.
Let
me
sorry,
I'm
just
looking
for
this
document
here,
but
yeah
I'll,
just
add
a
doc
to
that
one
and
we
can
probably
cross
it
off.
D
No,
I
think
I
think
that
I
don't
know.
I
think
I
think
that
we
can't
really.
We
don't
really
want
to
write
a
ton
of
documentation
without
the
cube
builder
clients
to
come
in.
So
I
think
it's
more.
That's
not
really.
I
guess
related
to
this
stuff
as
much
as
it
is
just
like
add
something
to
the
cube
builder
book
once
once
the
the
clients,
once
the
the
apply
clients
get
merged
into
like
cube,
cube
controller
tools
and.