►
From YouTube: WebAssembly Filters Meeting (Aug 9th, 2021)
Description
WebAssembly Filters Meeting - Aug 9th, 2021
Join the community at https://layer5.io/community
Find Layer5 on:
GitHub: https://github.com/layer5io
Twitter: https://twitter.com/layer5
LinkedIn: https://www.linkedin.com/company/layer5
Docker Hub: https://hub.docker.com/u/layer5/
A
A
We
all
of
you
are
familiar
face
at
this
point,
so
you're
aware
that
we
record
the
meetings
and
post
them
on
youtube
and
with
that
we've
got
a
few
things
to
go
over
in
context
of
webassembly
filters,
a
little
less
today
on
webassembly
as
a
technology
and
envoy
as
part
of
that
focus,
but
a
little
more
today,
probably
on
how
measury
is
managing
filters
and
then
some
related
concepts.
A
A
A
A
Okay,
good
well,
the
first
topic
was
pretty
quick
by
the
way.
So,
as
we
get
kicked
off
here,
we
run
this
call
just
like
we
run
all
the
other
community
calls,
and
so
we
take
a
moment
to
introduce
anyone
who's
new
on
the
call-
and
it
looks
like
my
measure-
is
coming
up.
So
it's
refreshing
on
me,
but
now's
your
chance.
If
this
is
your
first
time
on
this
particular
call,
please
take
a
moment
to
say:
hi
introduce
yourself.
A
We
can
almost
hear
you
say
it
again.
A
Very
good
good,
I
think
your
voice
cut
out
a
little
bit,
but
we
did
get
the.
I
think
this
one
like
this.
D
A
D
A
Nice
beautiful
welcome,
I'm
very,
very
nice
to
have
you
wait,
say
your
first
name
one
more
time
is
it.
A
Nice,
so
I
didn't
get
that,
oh,
you
know
what
attend.
There's
it's
great
to
have
you
there's
a
couple
of
other
meetings
that
might
interest
you
as
well,
and
so
we
just
had
a
websites
meeting
actually
that
that
might
be
of
interest
as
well.
So,
no
doubt
some
of
the
folks
on
the
call
will
tell
you
about
those
so
good
thanks
for
thanks
for
joining
yeah.
Thank
you,
nice
all
right.
So
we've
got
a
couple
of
topics
up
so
well
gosh.
A
If
I
recall,
I
think
we
were
having
more
of
a
discussion
about
various
items
to
configure
of
filters,
and
I
think
in
the
time
that
we
last
met
somewhere
in
between
there,
we
ended
up
with
a
couple
of
new
components
potentially,
and
so
those
components
bear
weight
on
some
of
the
work
that
abi
kumar
is
working
on
in
terms
of
the
user
experience
for
so
when
someone
goes
to
try
to
you
know,
deploy
a
filter
from
measure
ui.
E
Okay,
I'm
not
sure
I,
like
I
understood
the
first
part,
that
is,
there
were
some
proposals
of
adding
up
a
few
more
attributes
that
we
stored
about
filters
and
I
couldn't
quite
get
the
part
of
basically
the
relation
with
the
mystery
one.
A
Yeah
yeah
there,
okay,
so
a
couple
of
the
items
that
we
spoke
about
last
time
in
terms
of
capturing
had
to
deal
well,
not
just
specifically
with
filters,
but
also
ended
up
applying
to
patterns
and
applications
as
well,
to
the
extent
that
people
have
uploaded
a
file
to
mesheri
it.
It's
nice
to
be
able
to
show
back
the
you
know
the
some
display
name,
but
also
the
file
name
of
the
pattern
of
the
application
of
the
filter
for
pattern
and
application.
A
There
might
not
be
a
file
name
based
on
because
maybe
they
they
loaded
it
in
a
different
way,
but
anyway,
those
were
attributes
kind
of
common
attributes.
I
think
we
want
to
expose
across
patterns
applications
and
filters,
so
abi
and
megana
as
you.
Hopefully,
your
ears
are
picking
up
as
we're
talking
about
this
I
mean
crush.
I
you
know
the
for
filters.
Specifically,
there
were
a
number
of
other.
A
E
Okay,
yeah
yeah
right
now,
I
remember
so
yeah,
but
there
were
a
few
if
we
talked
about
only
filters
for
now.
E
So
there
were
a
few
things
that
that
I
was
proposing
that
we
can
and
probably
should
track
when
we
actually
store
filters
in
in
the
pro
in
the
databases,
and
those
fields
were
like
where,
where
the
filter
should
land
in
the
in
filter
chain,
that
is
what
position
should
it
be
dropped
into
and
if
it's
supposed
to
be
dropped
into
sidecar
or
should
it
be
dropped
into
a
gateway
and
those
kind
of
stuff
that
that
configuration?
E
The
reason
you
may
want
to
capture
this
is
first
definitely
it
makes
it
more
configurable
and
the
second
reason
I
was
proposing
this
was
because
we
have
a
few
filters
which
are
which
are
like
special
to
measuring,
like
rate
limiting
and
all
in
those
cases.
We
do
not
actually
require
the
user
to
input
those
kind
of
things
and
we
can
still
save
them
on.
So
basically,
it
would
be
a
more
generic
approach.
That
is,
these
are
the
special
filters.
E
We
have
the
configuration
for
them
and
just
apply
it,
and
we
will
drop
it
in
the
right
position.
Just
let
us
know
where
to
drop
it.
That
is
what
we're
going
to
actually
say
so.
The
two
or
three
fields
that
I
was
proposing
first,
was
basically
the
position
and
filter
change.
Second,
was
which
workload
to
select,
and
third
is
what
component
you
say
that
is
is
it's
a
cycle
proxy
is
basically
cycle
bound
is
what
I
guess
they
call
it
or
basically
gateway
in
inbound
traffic
or
outbound
traffic.
E
Those
kind
of
configuration
that
is,
that
is
what
I
was
basically
proposing,
and
the
generic
fields
that
I
was
that
we
were
talking
about
was
basically
separating
out
the
patents
name.
So
patents,
patents
in
themselves
have
actually
a
name
field
in
them,
but
we
can
allow,
which
in
some
cases
actually
happens
also
so
mitch
mark
is
the
example.
Mesh
map
actually
keeps
pattern
names
separate
in
the
file
like
the
display
name
separate,
so
that's
a
thing
that
we
can
maybe
make
more
common
among
patents,
application.
E
E
Yeah
yeah,
I
think
so.
Okay,
although
in
terms
of
patterns,
probably
file
name,
would
always
be
present.
So
if
you're
loading
it
from
a
repository,
it's
still
being
getting
fetched
from
a
file,
there
is
a
file
and
if
you're
loading
it
from
memory
ctl,
there
is
still
a
file.
So
most
of
the
time
at
least
for
now
you
would
have
a
file
name,
but
probably
if
we
support
streams
or
input
streams
or
something
in
future,
then
in
that
case,
definitely
there
won't
be
a
file
name.
A
Okay,
what
about
the
case
of
designing
from
scratch
in
mesh
map.
E
Yeah,
actually,
that's
something
actually
that's
handed
by
mishma.
The
mesh
map
assigns
a
name
automatically
to
the
file,
and
that
is
the
display.
The
pattern
name
is
this
is
what
mishma
does
differently
than
what
is
being
happening
in
ministry
ui?
What
mesh
map
does
is
it's
actually
even
today
separates
out
the
display
name
from
the
name
of
the
patent.
Display
name
is
something
that
the
user
says.
The
pattern
name
is
something
that
the
server
is
setting
and
that
is
messy
generated
pattern.
That's
common
among
everything.
E
Every
pattern
that's
being
generated
when
you
design
using
meshmark
a
while
the
display
name,
is
something
that
the
user
can
set
to
anything
they
want
to.
Like
I
recently
created,
I
was
trying
bokeh
info
deploying
book
info
from
mishma,
and
I
called
the
display
name
to
be
booking
for
new
to
something,
but
the
battery
name
was
the
mystery
generation
part.
So
that's
something
mesh
map
is
already
doing,
but
we
should
probably
be
doing
the
same
thing
in
mystery.
Ui
also,
that
is
separating
out
the
display
name
with
the
pattern
name.
A
Okay,
so
I
guess
to
just
to
be
concise
the
when
someone
designs
a
new
pattern
in
mesh
map.
We
are
meshmap
as
a
plugin
is
not
only
providing
a
display
name,
but
is
also
responsible
for
providing
a
file
name.
E
So
right
now
patterns
do
not
have
a
different
thing
called
file
name.
They
have
two
attributes
the
display
name
and
the
name
that
is
present
in
the
pattern
mesh
map.
What
it's
doing
is
it
allows
you
to
configure
the
display
name
while
the
pattern
name
is
something
that
the
server
sits
up
for
you,
while
the
same
is
not
available
in
common
machine
work.
E
What
happens
in
that
case
is
if
you,
if
you
would
go
to
the
patent
section,
which
probably
it's
not
showing
up
here-
okay,
it
is
so
these
valencian
that
you
would
see
if
you
would
upload
something
from
here,
it
will
grab
the
pattern
name.
What
that
is
a
display
name
that
is
coming
in
this
pattern
in
column.
It
will
drop
it
from
whatever
the
name
was
of
the
pattern
on
top.
Basically,
there
is
a
field
called
name
in
the
patterns.
It
will
grab
that
name
from
here.
A
Okay,
actually
just
the
answer
like
if
the
answer
is
hey,
look
we're
going
to
have
common
attributes
across
patterns,
applications
and
filters.
Then,
if
those
common
attributes
are
file,
name
display,
name
and
right
now,
applications
doesn't
you
know
it
only
has
one,
then
it
needs
to
have
a
second
one
added.
It
needs
to
be
split
out
and
then,
as
we
implement
that
at
those
two,
as
universal
attributes
of
you
know,
objects
like
these
that
in
some
cases
some
we
either
can
allow
the
file
name
to
be
optional
or
we
can
mandate
it.
A
We
just
need
to
make
sure
that
plugins
also
adhere
to
that.
You
know
as
a
client.
They
also
adhere
to
the
same
requirement
and-
and
they
can-
I
think,
that's
the
I
mean
yeah.
Your
explanation
is
a
good,
a
healthy
one
of
like
well
like
technically
patterns,
don't
support
both
at
the
moment
but
then
like
and
so,
but
as
we.
If
we
go
to
just
make
this
uniform,
I
think
it'll
be
easier
in
many
respects.
It's
just
the
same
modal
or
same
component,
it's
populated
with
different
data,
the
and
potentially
different
actions.
A
E
Yeah
we
can
yeah,
we
definitely
can,
although
just
just
to
basically
inform
we
already
keep
track
of
where
this
thing
was
captured
from
it's
just
not
being
displayed
right
now.
So
that's
something
we
do
keep
track
of.
Basically,
it's
location.
A
Okay,
okay
yeah,
that
makes
sense.
So
I
I
don't,
and
for
my
part
I
don't
particularly
have
a.
I
have
a
strong
opinion
per
se
about.
I
think
the
only
opinion
that
I
really
have
is
that
is
that
display
name
be
distinct
from
the
identifier
whatever
that
ends
up
being,
and
I
think
for
each
pattern
for
pattern,
has
a
construct
application
as
a
construct
and
filter
as
a
construct.
I
think
each
of
those
have
their
own
identifier.
A
They
would
then
each
have
their
own
display
name
and
to
the
extent
that
they're
represented
as
a
file
that
they
would
have.
You
know,
a
location,
a
file
name
or
a
location,
and
I
think
that
unless
I'm
missing
the
mark,
all
of
the
way
that
the
the
data
structure
behind
each
of
those
three
constructs-
I
think
those
can
be-
I
mean,
there's
commonalities
across
them
and
and
for
the
purposes
of
file,
name
and
display,
name
or
location
and
display
name
that
those
could
be
the
same
either
way.
It'll
serve
us
very
well.
A
Yep
and
it
doesn't
neces
at
this
point-
it
doesn't
necessarily
have
to
go
very
deep
more.
Yes,
it's
what
you
said,
but
it's
actually
focused
specifically
on
what
are
common
attributes
across
patterns
apps
and
filters,
which
makes
it
yeah,
which
I
think
makes
a
little
bit
of
an
easier
challenge,
because
the
filters
end
up
going
a
little.
You
know
a
little
deeper
with
additional
metadata,
but
and
who
karst
is
that
I
can't
see
you
so
I
don't.
Where
did
you
go?
A
I'll
try
if-
and
you
know
what
it
can
be-
is
just
just
a
set
of
bullet
points
that
talk
about
what
the
attribute,
what
attributes
are
currently
being
tracked
for
each
of
these
constructs
and
that's
and
what's
common,
what
that'll
really
help
with
driving
the
user
experience
for
as
megana
and
gaurav
and
abi
and
folks
work
on
these
three
areas
for
the
user
as
well,
that
that,
at
least
for
right
now,
the
users
of
mastery
as
they're
using
the
ui
here
they'll,
have
a
have
a
common
experience
up
to
the
point
that
one
of
these
has
additional
metadata
or-
and
some
of
that
has
to
do
with
when
you
go
to
deploy
the
thing
and
how
it's
being
applied,
whether
it's
just
a
simple
you
know
apply
or
whether
it
there's
additional
questions
to
ask.
A
G
Yes,
yes,
yes,
I
had
few
questions
like
I
was
apply.
I
was
applying
the
same
filters
to
like
the
rjfs.
G
And
make
rjfs
form
available
for
the
remaining
two.
G
Applications
of
filters
patterns
application
site,
so
I
have
just
added
and
then
it
is
actually
working
for
the
application,
because
the
home
workload
and
home
trades
that
are
coming
from
the
server
like
from
the
api
call
has
the
schema.
That
is,
you
know,
suitable
for
applications
only
right
now,
so
I
was
not
sure
like
how
to
like
make
it
happen
for
other
things
like
for
filters
and
other
patterns.
G
So,
first
of
all
this
is
the
third
icon
that
I
have
added
just
temporarily
since
just
to
check
out
things
and
when
I
click
on
it,
it
will
actually
take
this
yaml
file
from
here
and
it
will
convert
it
to
the
json
and
then
parse
it
accordingly
for
the
form
and
just
push
it
to
the
schema
and
the
things
are
generated
here
right.
So.
G
From
here
right,
so
another
container
name,
sorry
autocomplete
container
name
two,
and
I
can
I
use
any.
You
know
that's
in
1994
now
and
I
can
submit
right.
So
it's
it
generated
a
new
pattern
for
me
with
this
by
duplicating
the
previous
pattern
that
I
just
opened,
and
the
new
pattern
is
generated
here
with
the
yaml
configuration
like
we
just
generated
it
this
so
actually
it
is.
It
is
writing
things
in
a
different
manner
for
now,
so
I
will
fix
it
and
yeah.
G
So
I
can
see
the
information
right
here.
I
can
even
reiterate
the
previous
process
to
make
it
make
make
it
as
a
new
pattern
for
ir
for
now-
or
I
can
just
add.
An
update
button
here
like
here,
is
submit
button,
delete
button
and
I
can
add
one
more
button,
which
is
for
updating
things
so
that
I
can
upload
update
it
in
the
current
form.
Only
so
that's
the
progress
for
now
and.
G
It's
not
working
for
different
things,
since,
if
you
see.
G
G
Failed,
I
guess
it's
expired,
token
expired.
So
basically,
it's
not
following.
G
G
And
secondly,
the
ui
server
is
fixed.
I
guess
because
I'm
no
I'm
not
getting
the
same.
You
know
loading
thing
after
refreshing,
the
ui
server
again
and
again.
So
I
think
that
was
that
problem
was
fixed
with
that.
E
So
obviously,
actually
this
is
valid
patterns
just
that
it's
not
yet
valid,
because
the
pr
hasn't
been
merged
once
it
will
be
merged.
This
pattern
would
become
like
basically,
the
schema
distance
schema
would
automatically
update,
and
so
the
pattern
would
actually
pass
through.
It's.
G
E
So
again,
two
things
actually
this
is,
I
don't,
I
think,
while
testing
out
someone
uploaded
this
particular
filter,
but
this
is
this
is
a
pattern
file.
It's
not
a
filter
as
first
thing.
The
second
thing
is
about
the
concern
regarding
schemas.
So
the
reason
you
are
not
seeing
some
of
the
schemas
is
because
these
schemas
may
be
coming
from
different
components
and
those
components.
This
is
actually
the
right.
Basically,
this
is
the
correct
filter.
E
So
what
you
have
to
do
to
actually
apply
it
is
to
run,
is
the
adapter
once
you
will
actually
spin
up
history
adapter,
it
will
register
its
json
schema.
This
is
something
that
this
your
adapter
actually
handles.
That's
somewhat
the
name
conveys
onward
filter
sd.
If
you
would
have
one
is
your
doctor
running,
it
will
register
json
schema
and
then
this
pattern
file
would
work
just
fine
right
now
the
server
might
be
rejecting
it.
Saying
that
hey
you
do
not.
Basically,
this
is
not
a
bad
pattern.
G
Okay,
okay:
I
was
worried
about
like
how
to
incorporate
this
under
a
new
schema
like.
Is
there
any
better
approach
to
do
it
for
the
like
into
the
rjfs
home.
E
G
Okay;
okay,
from
which
api
like
from
which
endpoint.
E
Yeah,
you
will
be
able
to
see
the
schema
for
every
component
that
aims
industry
server
yeah,
it's
just
that
you
are
not
being
like.
It's
not
returning
those
schemas
right
now,
because
you
do
not
have
history
adapter
running,
because
even
the
share
server
doesn't
know
that
those
schemas
exist.
It
will
only
get
to
know
about
them
once
instead
after
starts,
and
basically
when
one
when
you
start
up
a
steered
after
instance,.
A
Okay,
just
also
to
clarify,
I
think,
for
everyone
else
that
that,
for
a
filter,
the
user
experience
will
be
fairly
consistent
from
filter
to
filter,
to
filter,
but
between
applications
and
between
patterns.
They
may
describe
very
different
things.
A
So
when
someone
goes
to
edit
a
given
pattern
or
edit
an
application
that
may
mean
that
you're,
you
need
to
display
any
number
of
components
to
be
able
to
configure
and
so
really
like
the
tool
tip
that
we're
using
to
show
to
edit
or
the
modal
that's
being
displayed
to
edit
rjsf
components
so
obvi
that
that
won't
work
for
patterns
or
applications
like
we'll
need
to
have
a
different.
What
we'll
need
to
do
is
in
a
pattern.
A
pattern
may
be,
you
know
five
lines
long
or
it
may
be
120
lines
long.
A
The
120
line,
long
file,
it
may
say:
okay,
here's
it!
This
pattern
has
one
application.
It
has
a
second
application
as
a
performance
test
and
it
just
keeps
going
and
so
those
independence,
individual
sections,
those
individual
stanzas.
So
to
speak,
they
would
need
to
be
like,
as
we
go,
to
show
them
in
the
ui.
They'll
need
to
be
componentized.
A
I
mean
like
they'll
you'll
need
to
show
the
fact
that
all
of
the
aspects
of
the
pattern
can
be
edited
and
each
of
those
attributes
can
be
configured
and
we're
doing
you
know
that
more
or
less
now
in
that
small
modal
or
that
small
tool
tip,
I'm
not
sure
what
we're
using
for
the
for
the
filters
or
for
the
app
for
the
patterns.
I'm
sorry
that
you're
doing
you're
showing
patterns
with
containers
and
replicas,
and
so,
if
you
have
you
know,
50
applications
inside
that
pattern.
A
A
E
So
yeah
there
can
be
multiple
schemas
associated
with
a
single
pattern.
Actually,
that's
a
design.
A
pattern
can
have
any
number
of
components,
different
components,
same
components
and
each
component
may
or
may
not
have
same
json
schema.
You
can
query
for
json
schema
using
the
end
point
that
you
have
a
bishop
and
using
that
you
can
get
these
schema
corresponding
to
each
component
and
based
on
that,
you
can
probably
render
rtse
forms
because
rtc
forms
feeds
on
this
and
schema.
E
A
Makes
sense
thanks,
good,
okay,
good
as
we
go
along
as
well,
it
might
help
clarify
so
megan
if
we
switch
topics
to
one
of
the
things
that
we
are
looking
at
enhancing.
J
Okay,
so
I'm
working
on
the
filter,
part
of
it
and
I
actually
just
started
working
on
it
last
week
it
was
very
unwell.
Actually,
so
I
couldn't
work
on
it,
so
I
just
started
working
on
the
filter
of
it
apart
and
I'm
trying
to
add
the
model.
This
is
no
big
update
on
that.
To
be
honest,.
A
Okay,
sure
is
there
any
okay
good
in
essence,
all
right,
let
me
clarify
anything
that
you've
been
able
to
do
since
last
week
that
we
can
talk
about
or
or
or
will
we
take
a
pass.
This.
J
To
be
honest,
there
isn't
much
I'm
going
through
the
code
and
trying
to
add
the
model
part.
So
there's
a
lot
of
code
in
that
page.
So
I'm
trying
to
understand
how
to
add
it.
So
that's
what
I'm
working
on
right
now,
I'm
getting
a
few
errors,
I'm
trying
to
fix
it.
A
Yep
makes
sense,
so
each
of
these
three,
these
were
to
basically
add
support
for
for
uploading
by
url
to
each
to
filters,
patterns
and
applications.
Is
that
right.
J
I
think
someone
else
is
going
to
start
working
on
the
patents
or
applications.
I'm
not
sure
I
saw
it
in
slack
or
I
think
someone
else
has
taken
up
the
task,
I'm
not
sure
yeah.
Currently
I'm
working
on
the
filters,
so
that's
the
one
I'm
working
on
so.
H
J
E
I
think
it
can
be
reusable
complement
because
all
three
have
this
thing
in
common:
that
is,
they
can
be
important,
the
same
way
from
remote
virus.
So
if
it's
reusable,
then.
H
A
Good
and
then
yeah,
I'm
megan,
if
you
can't
as
you
progress
on
it
this
week,
you
drop
in
intermediate
updates
as
you
go
like
or
ask
questions
as
you
go
that
way:
you're
not
you'll
get
you
don't
get
stuck.
K
Yeah
so
like
initially
when
I
made
the
changes
in
my
pr
like
I
directly
added
the
swagger.yml
file,
but
like
it's
auto,
generate
auto,
like
regenerated
like
every
time
like
there's
a
push
so
like
that
won't
work
so
like
I
have
to
edit
the
annotations,
but
the
problem
I'm
currently
facing
right
now
is
that
the
com
is
that
the
commands
used
to
like
regenerate
the
swagger.yml
file
like
when
I'm
trying
it
out
locally.
It's
giving
me
a
broken
output.
A
Hey
it's
yeah,
it's
starting,
but
it
hasn't
shared
just
yet.
I
know.
K
And
my
zoom
just
crashed
right
now.
I
just
rejoined
okay.
F
Let's
take
the
there,
you
go.
A
K
On
no
wait,
I
have
the
error
open
right
now,
so
it's
not
the
it's
not
mostly
about
the
error
like
of
like.
Even
if
there's
an
error
like
the
swagger.vml
file
is
being
generated,
but
even
after
is
being
generated
like
some
of
the
stuffs
in
the
like
docs,
it's
not
coming
like
it's
just
missing
like,
even
if
I
did
not
change
anything
just
regenerating
the
file
causes
things
to
go
missing.
K
A
K
G
G
K
Okay,
so
anyways
like
this
is
the
error
like
it's
not
really
informative,.
A
Oh
all
right
so
surya
shankar,
we'll
let
you
take
a
screenshot
of
it
and
share
it
later,
or
copy
and
paste.
Okay,
yeah,
you've,
pasted
the
error
into
chat
and
so
yeah.
I
mean
this.
A
Good,
so
that
one
of
the
individuals
that
was
working
on
this
is
piyush
singharia,
you
might
be
a
good
person
to
get
request.
Some
assistance
from.
K
Oh
yeah
sure,
like
I,
I
like,
tried
the
commands
in
the
like
guide
like
sent
by
him.
I
guess,
like
the
make
the
standard
makes
fargo
spec
and
I'll
make
swag
make
swagger
docks
like
just
running.
These
two
commands
is
creating
a
completely
like
different,
like
swagger.ml,
and
when
you
run
the
docks,
the
docs.measury.io
like
it's
giving
me
an
incomplete.
Like
response,
you
could
say.
A
C
So
I
guess
I
had
to
do
a
design
split,
but
I
wasn't
able
to
give
any
thoughts
on
this
and
integrating
it
into
the
build
process.
I
had
this
one
question
like
shouldn't:
we
release
the
binaries
for
those
filters
on
the
repo
itself
like
it
would
be
a
mess
to
build
them
every
time
we
build
docker
image
for
this
right.
F
A
Okay,
then
yeah,
maybe
let's
hold
off
on
yeah,
that
your
the
area
that
you're
gonna
dig
into
a
little
bit
probably
does
require
a
little
deeper
thought.
I
can
collaborate
with
you
on
putting
some
of
that
on
paper
because
yeah,
I
don't
know
that.
There's
a
clear
or
there's
there's
a
number
of
things
to
consider
and
you're
right
like
for
the
moment,
or
at
least
in
our
initial
support
here,
that,
if
we're
bundling
in
sample
filters
that
we're
those
are
pre-built
that
we're
not
building
them
on
the
fly.
A
Okay,
so
garav
isn't
with
us,
but
we
kind
of
talked
about
the
need
to
have
common
attributes
across
the
components
utkarsh
is
going
to.
You
know
just
briefly
document
a
set
of
specific
envoy
filter,
specific
attributes
so
navendu,
I
know
you.
This
is
a
an
area
that
you'd
worked
on
in
the
past.
Like
there's
a
couple
of
issues
that
are
going
on
with
with
filters
so
one
I
can't
delete
a
filter.
B
Yeah,
so
that
pr
was
to
let
people
store
the
binaries,
the
database,
so
the
filtered
binaries,
and
it
also
adds
an
end
point
to
the
filter
files
so
yeah
that
pr
could
be
merged.
B
A
Right
now
it
okay
good,
so
there's
a
com
so
between
someone
needs
to
have
it.
We
need
to
have
a
spec
for
what
we're
tracking
about
filters
and
we
kind
of
do,
but
I
think
it's
gotten
lost.
A
H
B
Ready
server
to
deploy
the
filters
like
pick
the
configuration
and
bundle
that
up
into
a
patent
file
and
actually
deploy
it.
I
think
there
is
nothing
left
on
the
provider
side.
A
B
A
B
A
B
There
is
a
designs:
there
was
a
distinct
spec
for
wasabi
to
spatter.
It
is
outdated,
I
guess
so
we
can
track
it
over
there.
Let
me
share
the
intention.
A
So
woodkar
as
you're
looking
at
this
as
well.
A
All
right
so
rude
rocks.
I
think
some
of
the
thoughts
that
of
the
design
that
you
would
have
probably
go
into
the
filter
hub
design
spec,
while
some
of
the
particulars
of
of
what
we're
talking
about
about
tracking
attributes
on
filters
that
would
go
into
this
dock
good.
I
think
that'll
help
provide
some
clarity,
as
we've
got
that
written
down
yep
all
right.
A
Okay,
so
all
right,
we're
we're
so
joshua
isn't
on,
and
neither
is
anybody
so
nearby,
I
think,
is
bowing
out
of
the
original
the
the
prior
commitment
to
present
envoy
traffic
mirroring.
He
spoke
about
it
a
little
bit
a
while
ago
when
he
did
his
other
presentation,
but
I
think
he's
gonna
feel
a
lot
more
comfortable
working
on
some
c
plus
in
in
get
nighthawk
on
adaptive,
load
controllers
so
and
then
josh,
I
think,
he's
still
just
waiting
for
approval
from
oracle.
A
A
All
right
here
we
go
so
if
we're
here
looking
at
patterns
and
patterns
potentially
have
all
kinds
of
things
inside
of
them
that
we're
tracking
you
know
you
there
may
make
sense.
So
when
someone
goes
to
you
know
when
they
go
to
edit
or
they
go
to
dig
into
the
details,
there
could
potentially
be
so
many
details
that
we
would
basically
end
up
with
either
another
table
in
a
table.
A
So
so
the
details
might
be
that
in
one
pattern
there
are
10
applications,
let's
say
so,
then,
if
you
get
a
sub
table
with
one
row
per
application,
it
might
make
sense
at
that
point
to
then
have
the
edit
button
to
be
able
to
edit
that
particular
app
or-
and
it
probably
most
of
the
time,
wouldn't
be
yaml.
Actually,
that's
the
thing
that
we're
trying
to
get
away
from.
We
want
to
dynamically
display
various
input.
You
know
fields
instead,.
A
Yeah,
try
to
move
away
from
the
on
the
patterns.
Ui,
try
to
move
away
from
using
a
modal
and
instead
have
a
an
expan,
a
table
and
table
break
down
each
either
it
maybe
it's
a
table
and
table,
but
it's
at
least
an
expandable
row.
Maybe
it
doesn't
make
sense
to
show
a
table.
It
just
makes
sense
to
show
the
title
of
that
component.
So
in
a
pattern,
if
you
have
10
applications
in
a
pattern,
this
would
be
the
name
of
that
component.
A
A
G
Okay,
okay,
so
currently
it's
in
the
form
of
table,
and
we
want
something
like
cards
like.
A
Yeah,
I
think
so
yeah
I
mean
I
would
go
light
on
the
card
thing
and
more
just
trying
to
present
someone
like
little
light
separators
between
one
component
in
the
configuration
of
that
component
versus
the
next.
G
Okay,
so
okay,
okay,
we'll
discuss
more
when
we
will.
A
Yeah,
if
you
would
yeah
please,
I
think
that
this
issue
is
probably
the
one
yep,
and
this
will
work.
It's
really.
It
ends
up
being
like
the
same
same
thing.
We're
just
you're,
you're,
retrieving
a
workload
from
the
workload
and
it
has
either
one
component
with
some
attributes,
or
it
has
9000
components
with
some
attributes
each.
You
know
what
I
mean,
so
it
just
needs
to
be
dynamic,
such
that.
A
A
Like
I
mean,
like
sir,
I
mean
like
eventually
you'll
get
there
and
you'll
think
of
it
as
different
for
the
time
being,
we're
really
just
looking
for
the
same
thing
that
megane
is
doing
with
a
component
for
importing
via
url
is
like
it's
the
same
ui
that
we
would
basically
desire
across
patterns,
applications
and
filters,
and
so
just
to
answer
your
question
in
a
non-technical
way,
which
I
think
actually
is
what
you're
asking
is
like
a
pattern,
can
contain
a
definition
of
any
number
of
filters,
whereas
the
filter
ui,
it
will
only
display
filters
if
they're
stored
independently.
A
A
Okay,
yeah
there's
some
designs
that
we
have
to
do
there's
a
little
bit
of
asynchronous
collaboration.
We'll
need
to
do
to
get
some
designs
in
the
right
place
that
way,
it'll
be
a
bit
more
clear
for
folks
get
some
get
some
mock-ups
going
as
well.
So
it's
a
it's
a
bit
like
obvious,
not
an
unintelligent
individual
like
it.
It's
not!
A
It's
not
well
defined,
so
we
can
get
that
changed
this
week.
A
All
righty
very
good
nice
to
talk
to
you
all
we'll
get
some
designs
and
well
written
designs
and
mock-ups
going
for
next
week,
and
then
you
dropped
in
the
link
again
to
the
spec
good.