►
From YouTube: WebAssembly Filters Meeting (Dec 06th, 2021)
Description
WebAssembly Filters Meeting - December 06th, 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
B
So
I
guess
it's
visible
properly
yeah.
It
is
yeah
so
about
the
github
import
issue.
The
main
blocker
I'm
facing
is
that
currently
it
is
accepting
only
one
pattern
that
we
can
upload
from
a
single
url.
So
the
issue
I'm
facing
with
that.
How
can
I
get
the
whole
pattern
from
a
single
folder,
because
the
approach
that
we
suggested
with
this
thing
that
we
can
convert
the
whole
file
into
a
single
url
raw
so
that
we
can
get
whole
patterns
or
the
wasm
files
accordingly?
B
So,
but
from
the
previous
update,
I
think
the
earthquake
said
that
we
can
get
this
whole
whole
pattern.
Thing
is
already
conversion.
The
whole
conversion
thing
is
already
available
in
the
server,
so
the
server
server
will
be
handling
this
automatically.
So
I'm
having
issue
with
this
thing,
the
implementation
of
this
thing.
So
what
I
should.
A
So
I
couldn't
exactly
so.
The
issue
is
that.
A
The
server
is
handling
something
for
you
and
actually
I'm
I'm
not
quite
sure
what
what
exactly
so,
were
you
questioning
how
the
how
the
user
experience
should
look
like
what
we're
questioning
from
implementation.
B
No,
the
implementation
point
of
view
about
the
user
experience
the
it
will
be
same
as
for
the
simple
url
upload.
A
Okay,
so
so
are
you
wondering
that
how
how
to
do
recursive
imports,
why
the
api
is
that
yeah.
A
Okay,
so
let
me
share
link
the
dock
where
all
of
this
is
actually
documented.
This
is
sort
of
I
think
yeah.
It
is
so
in
here.
If
you
would
like,
you
can
see
that
the
endpoint
name
is
actually
slash.
Aps
experimenter,
slash
pattern:
it
used
to
be
slash
api,
experimental,
slash
button
now
experimental
has
been
removed
from
it
other
than
that
everything
is
actually
as
the
docs
is.
That
is,
if
you
want
to.
A
Let's
say
if
you
want
to
import
something
from
from
the
repository
that
you
are
actually
pointing
to,
and
that
is
the
service
hyphen
mesh
hyphen
patterns,
that's
the
org
name,
so
owner
would
be
replaced
with
service
hyphen
mesh
hyphen
patents.
A
repository
name
is
service
hyphen
mesh
type
in
parents,
so
that
is
the
repository
section
and
branch
is
something
you
will
have.
To
also
add,
that
is
mean
is
master
because
we
use
master
branch
as
default
branch.
A
So
this
is
what
you
would
actually
set
in
the
post
body
and
in
the
path.
What
you
can
give
is
sample
sample,
slash
the
star
star.
That
would
mean
that
would
instruct
a
machine
server
to
go
to
the
samples
to
repository
directory
and
then
recurse,
everything
that
is
inside
it.
B
So,
okay,
so
the
conversion
thing
will
automatically
be
handled
with
this
api
only
what
conversion
by
conversion
I
mean
that
so
previously
we
were
just
taking
a
raw
file
of
this
thing
to
upload
and
by
conversion
I
mean
that
taking
the
whole
folder
and
converting
all
the
files
into
a
single
so
that
they
can
be
uploaded
one
by
one
automatically,
with
a
single
import.
A
Yeah
we
don't
actually
do
conversion,
it
is
yeah,
I
mean.
Even
if
there
are
directories
just
like
it
is
in
samples
all
of
them
will
be
actually
handled.
I
mean
they
will
be
all
pulled
in.
It's
not
exact
conversion
that
happens
in
the
server
but
yeah.
Basically,
everything
will
be
pulled
in
without
any
issues.
A
B
Okay,
so
I'll
try
with
this
approach
only
so
this
explicitly
thing
is
not
required.
A
Yeah
pretty
much
it's
not,
but
also
the
reason
you
may
want
to
use
servers.
Implementation
is
because
message:
server
can
also
measure
server,
also
supports
private
repositories
if
a
fertility
provider
supports
and
measure
cloud.
So
if
someone
is
locked
and
using
a
sheet
cloud,
they
can
even
pull
in
stuff
from
their
private
repositories,
which
which
definitely
this
approach
would
not
be
able
to
take
care
of,
because
private
repositories
will
not
be
accessible
via
just
api.
Without
basically
token
it
won't
be
accessible.
A
A
So
would
you
want
to
discuss
the.
A
Yeah,
so
let
me
propose,
and
probably
someone
can
improve
on
it
or
maybe
comment
on
it.
So
what
I
was
proposing
was
that
we
accepted
the
repository.
We
accept
the
repository
name
and
the
org
name
or
probably
in
the
same
input
box
or
something
the
reason
to
do.
The
reason
I
am
suggesting
not
to
take
in
url
is
because
someone
can
just
try
to
copy
and
paste
copy
and
paste
a
url,
and
that
may
or
may
not
work
that
may
or
may
not
work
directly.
A
A
That
is,
that
is
the
reason
I'm
assisting
not
to
directly
probably
take
in
the
url,
because
someone
someone
can
definitely
get
confused
like
if,
like
the
developers
who
are
developing
it,
we
get
confused
when
they
don't
see
the
spec.
A
So
how
like
probably
we
cannot
expect
others
to
basically
know
by
default,
so
the
I
think
what
we
can
do
is
we
can
take
in
the
repository
name
around
with
the
organization
or
the
username,
and
we
can
also
take
in
branch,
maybe
in
another,
in
another
input
box
or
something,
and
then
we
can
take
in
the
directory
we
can
take
in
which
directory
you
want
to
from
which
director
you
want
to
pull
in,
and
probably
a
check
box
for
recursion
like
to
request.
A
C
A
Terms
of
implementation,
what
will
happen
is
that
star
star
would
be
added.
So
let's
say
someone
select
someone
typed
in
samples.
That
is
the
directory
I
want
to
pull
in
from
and
then,
when
someone
do
the
check,
you
actually
add
a
slash
star
star
that
will
instruct
machine
server
to
do
the
recursion
so
basically
just
starting
some
coding
on
top
of
the
on
top
of
api,
because
api
is
not
like
the
most
user-friendly
thing.
Yeah.
A
In
case
someone
has
suggestions,
probably
lee
like,
if
you
have
any
suggestion
on
this
particular,
I.
C
Yeah,
well,
I
missed
the
ui
piece
of
it
or
the
ui
aspect
of
the
consideration,
but
did
follow
the
notion
that,
like
even
in
the
the
code
that
you
were
sharing
a
moment
ago,
gaurav
that
it
maybe
it
was
intentionally-
I
don't
know,
maybe
you
were
just
giving
examples
of
what
a
url
might
look
like,
but
in
in
the
code
that
you
were
showing
not
not
this
but
in
vs
code.
C
C
C
Actually
I'll
wait
for
you
to
confirm
that
this
is,
I
guess
so
yeah,
so,
okay,
so
yeah
when
I
was
saying
that
I
felt
like
it
was
one
of
those
comments
where
it
was
like.
Oh
you
know
you
didn't
capitalize
such
and
substance
like
yeah,
that's
because
I'm
only
like
10
into
my
work
and
so
comments
like
that.
Aren't
very
helpful
in
this
case
since
you're,
not
saying
that
I
feel
like
this
is
a
very
helpful
comment.
C
19
needs
to
be
completely
variabilized
every
single
thing
in
there,
the
protocol,
the
domain
name,
the
owner,
the
repo,
the
branch,
the
whole
thing
we
don't
want
to
have,
while
we
might
have
special
code
handling
interactions
with
github.com,
specifically,
that
would
be
through
a
different
protocol
and
it
depends
on
what
protocol
they're
authenticating
with
or
that
they
have
authenticated
with.
C
B
There's
a
number
of
other.
C
Software
applications
that
you
might
use
that
are
out
there
that
walk
people
through
entering
in
their
their
their
github
repo
name,
their
their
org
and
repo
name
and
which
is
probably
too
complex
for
what
you're
looking
to
do
like
yeah,
you
need
to
be
able
to
accept
and
validate
a
in
the
case
of
github.com.
C
C
A
Yeah,
I
don't
know
yeah,
so
probably
I
mean
I'm
not
sure
if
I
explain
it,
probably
or
not,
but
in
case
so
so
one
point
of
confusion
could
be
that
how
the
proposed
body
should
be
constructed.
In
that
case,
url
is
just
github.com,
so
owner
would
be
replaced
with
the
owner.
It's
it's
variables.
So
let's
take
the
example
of
samples.
It
would
be
service,
hyphen,
mesh,
hyphen
patents,
repository
would
be
service,
life
and
measurement.
A
Buttons
branch
would
be
something
coming
from
probably
any
other
input
box
where
they
are
saying
master
or
main
or
xyz
anything
a
custom
branch.
Probably,
and
then
you
will
actually
append
this
particular
thing,
the
branch
that
they
have
just
entered
and
in
the
path
again
there
could
be
an
input
box
where
you
are
asking
that,
okay,
which
path,
probably
we
will
have
to
present
our
input
box
rather
than
a
select
box,
because
right
now
we
at
least
right
now
we
get
mystery
server
doesn't
actually
provides
you
the
current
unlisted,
it's
actually
traversing.
A
It
doesn't
provides
you
beforehand.
What's
the
structure
of
it
of
it
is
so
you
will
have
to
probably
give
your
input
box
from
that
input
box.
You
will
actually
get
the
bar.
That
is
the
second
attribute
in
the
in
the
request
body,
and
the
third
attribute
is
save.
If
someone
is
importing,
we
can
probably
assume
that
it
is
save
is
true,
so
that
is
something
you
don't
have
to
actually
ask
the
user
for
so
that
will
be
always
safe,
good
and
true.
B
Okay,
yeah
and
the
third
one
will
be,
I
think,
handled
by
the
user
logged
in
provider.
B
The
third
one
you
said
that
save
will
be
true,
so
I
think
yeah.
A
Actually,
I
was
pointing
so
if
you
would
see
second
to
a
the
request
in
the
in
the
implementation
section.
The
second
point
that
is
request
body
may
look
like
following
in
the
in,
in
that
you
can
just
probably
look
at
the
first
example
that
is
do
a
in
there.
There
are
three
attributes,
url
path
and
save
the
url,
something
that
you
will
actually
ask
for
directly.
A
That
is
what
the
org
name
is,
and
what
repository
name
is,
and
you
will
also
ask
what
the
branch
name
is,
that
will
actually
that
will
actually
construct
the
url.
That
is
the
first
attribute.
The
second
attribute
is
part
that
is
you.
You
would
ask
what
directory
you
you
want
to
import
from,
and
probably
a
checkbox
as
well.
If
someone
clicks
on
checkbox,
that
basically
means
you
have
to
append
star
star
as
well
star
star.
A
If
you
have
used
block
patterns,
it
is
the
exact
same
clock
pattern
yeah,
it's
a
clock
pattern.
If
so,
when
someone
clicks
on
basically
does
the
checkbox
thing
that
is
yes
request.
Yes,
you'll
grab
everything
from
the
directories,
then
you
would
actually
add
star
star
as
well,
and
the
third
attribute
is
something
you
don't
have
to
ask
the
user
for,
because,
if
they
are
importing,
you
can
actually
expect
expect
that
they
do
want
to
save
it.
The
same
can
be
true.
This
api
is
actually
used
at
multiple
places
for
conversions
as
well.
A
That
is
why
the
save
attribute
is
there,
so
you
can
probably
skip
that.
If
you
skip
it
it
is,
it
is
meant
that
you
want
to
save
it.
So
that
is
how
basically,
you
construct
a
post
body,
a
single.
The
two
example
is
what
all
what
you
need
to
get
the
github
import
working
a
pro.
You
don't
have
to
probably
look
into
other
things.
The
provider
is
something
that
will
again
be
taken
care
by
the
mystery
server.
It
will
take.
B
A
B
C
Oh
cool,
well,
there's
I
don't
know,
I
don't
know
if
the
particular
person
on
the
call
can
kind
of
feel
like
they
sort
of
feel
their
spidey
senses
going
off.
They
kind
of
feel
like
I'm
about
to
say
their
name.
C
I'm
just
kind
of
waiting
for
it.
Sort
of
this
person
might
have
just
gotten
done
with
their
exams
and
be
you
know,
looking
for
something
to
do.
I
don't
know.
C
F
C
Couple
of
things
close
together
in
the
past
this,
this,
the
I
don't
know
who
wrote
this
spec,
but
it
looks
fairly
well
written
and-
and
the
nice
thing
about
this
particular
focus-
is
that
well,
it's
kind
of
it's
pretty
kind
of
related
to
what
we're
doing
with
like
writing
code
and
checking
in
code
and
stuff.
Is
it's
interacting
with
these
source
code,
repository
systems
and
so
yeah
kind
of
a
neat
thing
to
do
it
might
be?
I
don't
know
megan
if
you
have
a
look
as
well.
C
If,
if
you
guys
have
more
questions,
that's
totally
fine.
We
like
in
terms
of
ux
for
the
most
part,
we're
just
going
for
something
pretty
simple
at
the
moment,
because
we're
not
trying
to
provide
a
highly
curated
like
that
that
one
experience
that
we
talked
about
a
long
time
ago
about,
if
they're,
using
oauth
and
mesh
reserver,
has
the
permission
to
go
behind
the
scenes
and
like
look
at
the
users,
all
the
users
repos
and
all
their,
and
we
will
get
there
eventually.
C
C
It
will
look
through
each
of
the
files
to
see
if
they
are
appropriate,
fit
for
a
file
to
import
and-
and
so
one
thing
that
again,
this
is
thing.
This
is
things
that
can
be
built
upon
later,
but
just
as
as
user
experience,
when
someone,
maybe
they
enter
in
the
location
of
a
directory
and
they
click
import
or
they
might
actually
click
like
scan
or
traverse.
Or
you
know
some
other
action,
because
what
might
be
nice
is
if
they
point
to
a
directory.
There's
a
hundred
files
in
the
directory.
C
90
of
them
are
not
filters,
but
10
of
them
are,
and
only
six
of
them
they
actually
want
to
import
again
like
it
might
be
night.
This
is
a
nice
to
have
that.
Oh,
what
we
do
is
we
show
them
a
confirmation,
dialogue
that
says
well
out
of
the
100
files
we
found
10..
Here's
the
10
check,
check,
check,
check,
check,
check,
all
10
are
checked
import
or
give
them
an
opportunity
to
uncheck
the
four
that
they
didn't
want,
leave
just
those
six
and
then
like.
C
We
won't
have
to
make
it
very
complex
if
we
can't,
if
we,
if
that's,
if
we
don't
really
get
there
now
fine,
then
we'll
just
try
to
import
all
ten.
I
think
there's
logic
that
is
either
currently
in
mesh
reservoir
or
kind
of
on
its
way
to
being
built
to
avoid
duplicative
like
if
they,
if
they
did
that
same
import
like
five
times
they
imported
ten.
C
You
know
10
filters
five
times
they
have
like
10
filters
duplicating.
They
have
50
filters
duplicating
themselves
and
I
think
mesh
reservoir
is
going
to
try
to
handle
some
of
that.
But
but
some
amount
of
asking
the
user
is
is
ultimately
desirable.
Sometimes
users
will
say:
oh
yeah,
I
would
like
to
have
well
you
think
this
is
a
duplicate.
It's
not.
C
I
made
a
change,
and
so
I
do
want
you
to
you
know
they
want
to
tell
mesri
mastery
to
import
it
again
anyway,
look
like
I'm
making
it
more
complex,
like
it's
a
complex
thing,
the
behind.
If
you
want
to
get
it
all
right
and
stuff,
but
we
don't
want
to
get
it
all
right.
We
just
want
to
give
the
important
input
successfully
someone
to
validate
some
of
the
input
that
they're
given.
E
E
Be
clear
about
what
needs
to
be
done,
so
we
just
like
a
model
or
something
will
open
up
and
we'll
ask
for
a
url
right
and
what
else
we'll
be
asking
about
the
path
to
like
the
directory.
One
slash
directory
two
two
that
will
be
asked
and
we'll
ask
if
it's
recursive
or
not
and
then,
if
he
checks
it,
then
we're
gonna.
Add
that
two
stars
there
and
then
like
basically
create
a
post
request
for
that.
Is
that
what.
A
A
Much,
although
I
was
so
pretty
much
exactly
that,
although
I
was
suggesting
that
instead
of
taking
the
url
directly,
we
can't
just
take
in
owner
repository
because
if
someone
is
doing
github
import
that
is
implicit
and
the
reason
probably
not
taking
the
url
is
because
someone
can
definitely
get
confused.
They
might
think
that
okay,
I
can
copy
anything.
A
So
let's
say
they
are
on
the,
but
they
are
looking
at
a
yamal
and
they
think
that
okay,
I
can
just
copy
this
this
path
and
if
I
would
paste
probably
mesh
is
going
to
import
it.
It's
not
it's
going
to
get
confused,
because
this
is
the
structure
like
the
first
thing
has
to
be
when
the
second
thing
has
to
third
thing
has
to
be
branched,
and
that
is
not
how
the
urls
are
actually
constructed,
so
they
can
definitely
get
confused.
They
can't
try
to
paste
it
in
it
won't
work.
A
E
Okay,
so
we
need
to
keep
some
text
fields
there
for
owner
and
repository
right,
yeah.
A
None,
let's,
let's
move
on
to
the
next
item
before
we
move
on
to
the
next
item.
Tell
me
if
I'm
wrong
so
so
is
so
is
charles.
Are
israel
joining
us
for
the
us
for
the
first
time,
or
am
I
completely
mistaken.
A
F
A
D
D
Oh
yeah,
I
did
have
some
change
like
nvm
files,
I
tried
to
do.
Mbmus
version
was
different,
but
anyway
mainly
it's.
The
focus
should
be
on
go
down
to
the
file
where
it
says
the
spec
file.
D
I
did
have
some
data
cy
attributes
to
locate
some
elements.
Oh
there,
you
see
that
that's
the
you
go
up
a
bit.
That's
the
file
I'm
using
for
to
upload
filter.
D
So
I
don't
know
I
did
have
some
simple
tests
for
I
see
I
saw
there
were
like
some
similar
functionality
like
some
testing
on
the
like
on
the
ui
itself.
D
Maybe
that's
not
needed
at
that
point
like
the
ones
above,
but
basically
it's
this
test
for
for
the
post
request,
so
it
intercepted.
It
means
it's
we're
spying
on
it,
and
so
it
sounds
correct,
post
api
filter
request.
D
So
once
we
when
we
spy
it,
we
just
take
a
look
at
the
body
that
it
has
the
proper
structure
and
that
also
that
the
content
is
as
for
what
is
expected,
so
we're
using
a
lot
of
looks
like
some
promises,
but
it's
some
then
comments
from
cypress,
but
it's
basically
very
similar
and
and
well
yeah.
That's
that's
it.
I'm
not
sure
if
the
state
attribute
is
from
the
request
body
is
actually
needed.
D
I
wouldn't
know
if
that's
some
implementation
detail
that
might
not
be
relevant,
but
at
least
I
did
like
a
very
gray
gray
box
testing.
You
know
I
didn't
take
such
a
close
look
at
the
back-end
code,
but
looking
at
the
request
and
the
components
and
well,
this
is
what
I
came
up
with
and
the
actual
upload.
If
we
look
at
line
number
and
44,
this
attach
file
method.
This
is
coming
from
the
last
one
yeah.
This
is
coming
from
a
cypress
file
upload.
D
So
this
is
a
package
that
helps
simplify
this,
but
I
did
take
a
look
at
the
internal
code
of
that
and
this
is
basically
sending
a
change
event
directly
at
the
boxes.
So
at
the
input.
D
Sorry,
so
to
me,
it's
like
we're
doing
something
that
the
browser
already
like
does
when
the
user
clicks
and
selects
a
file.
So
I
don't
see
it's
a
big
issue
and
yeah
we're
passing.
You
know
that
the
file
the
file
path,
so
it
looks
and
and
the
contents
need
to
match.
So
I
don't
know-
I
don't
know.
If
there's
any
comments
or
questions
about
this.
D
D
I
mean
yeah,
you
could
maybe
I
can
share
the
oh
yeah
it
does.
The
link
to
appear
is
already
in
the
ci
slack
channel,
so
anyone
can
go
and
take
a
look.
A
Look
at
it
and
it's
it's
pretty
straight
and
good
right
now,
so
we
need
to
add
some
more
things
like
upload
file
is
already
there,
so
it
was
one
of
the
most
complex
thing
which
needs
a
new
file
upload
to
be
done
right
so
other
than
that
remaining
methods
will
be
much
easier.
I
guess
one
more
thing
that
I
just
noticed
is
that
whenever
we
successfully
post
a
request,
we
get
a
response,
as
in
the
snack
bar
that
pattern
successfully
uploaded.
So
a
snack.
C
D
Okay,
should
we
go
in
this
same
step
in
the
in
the
one
in
line
32
like
this,
like
in
the
false
request
like
I.
C
D
A
A
A
So
I
think
once
the
file
is
uploaded
and
when
we
get
the
successful
like
201
response
from
the
server
the
snap
bar
is
visible
like
it.
It
just
comes
to
the
screen,
or
maybe
it
is
it
is
having
time
out.
I
will
just
confirm
it.
Yeah.
A
Now
it
comes
in
when
I
subscribe
saying
that
is
when
you
actually
try
to
upload
this
particular
file
or
anything
as
soon
as
the
server
responds
back.
If,
if
the,
if
the
response
is
non
500
or
something,
then
then
a
snag
bar
comes
in
of
success,
and
if
it
is
an
error
message,
then
actually
our
error
message
comes
in.
So
basically
what
sheikh
was
saying.
D
Of
course
yeah.
That
sounds
great.
I
think
that's
very
good
input
I'll
I'll.
Take
a
look
at
that.
I
I
haven't
paid
so
much
attention,
maybe
because
you
know
that
the
test
runs
very
fast
and
cyprus.
Runner,
like
you,
can
like
go
back
in
time
by
hovering
over
certain
step
steps,
but
maybe
I'm
missing
something
because
I
didn't
see
the
sniper
back.
It
should
be
there
I'll.
D
Just
take
a
look
and
something
else,
so
I
was
thinking
into
so
all
of
this
input
I'll
work
on
that
for
this
test,
and
I
was
hoping
we
could
like
create
a
template
for
these
steps
and
then
other
other
tests
could
reuse
it,
but
I'm
I'm
a
bit
afraid
that
since
every
component
has
its
own
like
code
like
there
might
be
differences.
D
I
was
just
wondering
if,
like
the
ways,
the
way
that
the
upload
is
handled
for
all
of
the
three
pay,
like
pages
or
components
like,
is
that
the
way
it's
gonna
like?
Is
there
a
lot
of
work
remaining
or
is
there
like?
Is
there
any
plans
of
refactoring
the
code
to
reuse
the
same
function
like
like
yeah
to
reuse,
the
same
utility
for
this
or
like?
Is
there
any
differences
that
wouldn't
allow?
D
D
A
Yeah,
actually
so
just
I
mean
just
what
I
know
so
I
think
or
the
actually.
The
test
that
you
have
here
would
work
pretty
much.
A
Basically,
the
test
can
almost
remain
same
for
application
patterns
for
patterns
and
application.
The
test
would
at
least
right
now
the
test
would
look
a
pretty
much
similar,
because
the
files
that
they
accept
are
also
just
yama
and
at
least
if
you
are
just
talking
about
the
upload
file
test.
In
that
case
it
accepts
yaml
and
only
one
exact
same.
However,
for
filters
right
now
we
accept
wasm.
Now
this
is
this
is
actually
where
things
may
start
to
get
diverged
even
right
now,
and
that
is
for
filters.
A
We
accept
wasm
and
for
patterns
we
except
yami
for
application.
We
accept,
yaml
and
and
in
future
for
filters
we
may
accept
a
yaml
along
with
a
along
with
a
binary.
That
is
not
something
that
is
either
documented
or
has
been
heavily
discussed,
because
there
were
some
ideas
in
community
that
what
we
would
want
is
the
ability
to
upload
a
binary
as
well
as
some
default
configurations.
A
So,
just
like,
I
was
demoing
the
basic
authentication
basic
authentication
pattern
in
that
we
had
a
binary
and
we
also
had
a
basic
pattern,
a
lot
of
which
could
be
basically
was
just
tempting.
So
in
that
case
it
could
be
just
basically
we
could
just
save
it
alongside
binary.
So
right
now
right
now.
I
think
that
the
behavior
for
at
least
uploading
and
all
they
are
pretty
much
similar.
A
The
only
point
of
diverse
diversions
right
now
is
the
type
of
content
that
is
being
uploaded
and
that
for
patterns
and
applications
again
same
even
today,
and
it
differs
for
filters
that
turns
out
to
be
poison
file.
That
is
a
binary
other
than
that
everything
is
exactly
same,
and
I
I
I'm
not
sure
if
they
would
diverge
a
lot
in
future,
but
the
reason,
actually
we
have
like
components
for
everything,
as
you
were
pointing
out,
is
because
it's
because
a
lot
of
actually
we
use
mui
data
tables.
A
So
the
data
table
we
actually
reuse
that
component
but
construct
table
for
every
component,
and
second
reason
is,
I
think,
the
I
think
the
upload
function
is
also
being
repeated.
So,
as
you
were
pointing
out
that
maybe
some
some
scope
of
refactoring
is
right,
so
I
I
also
think
that
there
is
some
scope
of
refactoring
there
so,
and
that
is
actually
the
major
reason
we
have
a
huge
competence
for
each
of
them.
The
reason
is
not
quite
diversions
or
differences
in
them.
A
It
may
diverge
in
future,
but
and
not
at
least
what
I
can
think
of.
I
don't
think
a
lot
of
divergence
would
be
there
like.
I
think
that
there
would
be
still
tables.
I
think
that
the
table
would
still
look
same
for
uploading.
I
think
the
content
metaphor
as
I
was
pointing
out
earlier,
but
the
rest
will
actually
remain
same
so
so,
just
to
conclude,
I
said
a
lot
just
to
conclude.
I
I
think
that
these
tests,
as
you
were
saying
that
can
be
templated
out.
A
D
D
Will
that
change
in
the
future
and
in
this
or
and
it
is
the
same
for
all
of
the
other
kinds
of
uploads
like?
Would
it
be
test
patterns
test
application
or
is
the
user
expected
like
yeah?
Will
the
user
be
able
to
define.
A
Yeah,
actually
so
for
for
patterns
for
patterns,
that's
something
I
can
immediately
tell
and
navindo
would
be
the
guy
for
for
application
filters,
because
he
actually
implemented
those
end
points,
but
for
patents.
What
what
happens
is
that
because
it's
a
yama
in
patterns?
Basically,
if,
if
you're
writing
a
pattern,
it
is
mandated
that
you
provide
a
name.
There
should
be
a
name
entity
in
that
particular
yaml,
and
that
is
what
is
picked.
A
So
if
you
have
a
yaml
with
name
entity
called
xyz,
that
is
what
the
file
name
would
turn
out
to
be.
So
when
the
response
would
come
in,
that
is
the
file
name.
What
do
we
see?
That
is
the
file
name
we
save
from
for
filters.
I
think
test
filter
is
being
chosen
automatically.
Basically,
that's
the
name
that
we
that
navido
actually
chose
was
because
the
binaries
don't
have
that
attribute.
A
So
there
is
nothing
you
can
extract
from
it,
so
that
is
where
probably
that
name
is
coming
coming
from
and
for
application,
probably
naveed
can't
tell
if
we
are
actually
extracting
it
on
the
fly
or
we
are
falling
back
to
a
default.
Well,.
C
C
There's
a
nice
nicely
formatted
human
friendly
display
name
that
you
can
show
for
a
pattern
like
a
pattern,
is
a
great
example
where
one
of
the
first
lines
inside
of
the
yaml
file
for
a
pattern
is,
is
hopefully
a
human
display
name
is
written
there.
It's
a
required
element
is
to
have
a
name
whether
or
not
it's
nicely
spaced
and
capitalized,
and
all
that
is
up
to
the
person
that
wrote
the
pattern.
C
Introspecting
that
pattern
grabbing,
that
name
and
putting
it
into
the
measure
ui
table
that's
great,
but
is
a
separate
consideration
from
the
actual
file
name
itself
like.
Is
there
any
reason
that
the
file
name
of
any
of
these
three
artifacts
application
pattern
filter
that
the
original
file
name
as
it's
presented,
either
as
it's
uploaded
from
the
user's
local
file
system
or
as
it's
imported
from
github
or
some
other
url?
C
So
if
we're
using
test
something
something
that's
just
I,
I
would
expect
that.
That's
just
quick
filler
stuff,
we
should
not
be
renaming
every
filter,
that's
uploaded
to
test
filter,
and
now
I
see
that
the
uploaded
filter
name
on
line
great
there's
a
dif
there's,
a
distinction
between
the
filter,
name
and
the
file,
the
filter
file
name.
D
I
like
to
add
that,
in
this
kind
of
test,
we're
even
mocking
the
the
response,
so
it
really
it's
not
like
that
valuable
for
us
to
to
take
a
look
at
that
because,
whatever
we
add
in
the
fixtures
folder
like
whatever
is
the
content,
let's
say
like
that's
the
subsequent
get
request
received
after
the
upload,
like
that's
even
being
marked,
so
so
it's
kind
of
like
like
pretty
irrelevant
at
this
level
of
steps,
but
but
but
this
will
be
kind
of
reused
for
the
end-to-end
test
that
will
actually
check
for
for
a
real
response
from
the
back
end,
and
you
know
it'd
be
good
to
have
like
some
level
of
like
congruence
between
like
what's
happening
over
here
and
what
we'll
test
at
an
end-to-end
test.
D
C
C
Okay;
okay,
where.
C
D
A
there's
this
on
a
filter
above,
like
you
scroll
up,
please
like
there.
I
think
it's
kind
of
different,
like
than
a
pattern,
because
this
is
an
envoy
filter
right,
so
there's
no
or
maybe
there's
a
name,
but
it's
somewhere
else.
D
C
C
This
might
make
the
test
too
fragile,
like,
but
but
as
a
matter
of
as
a
matter
of
making
sure
that
the
functionality
is
correct
in
this
area,
like
the
fact
that
we're
able
to
introspect
a
pattern
and
retrieve
a
potentially
nice
display
name,
the
fact
that
we're
able
to
do
that
is
a
couple
of
one
is
because
it's
yaml
it's
text,
so
you
can
actually
go
into
the
file
too,
because
we
defined
what
the
definition
of
that
file
is.
C
You
could,
potentially,
you
could
do
that
for
kubernetes,
because
it
is
defined
what
that
is
supposed
to
be,
and
it
is
text
that
you
can
read
in,
but
it's
not
really.
It's
not
really.
All
that
advantageous
like
you
can
just
when
someone
imports
any
of
these
artifacts,
we
can
prompt
them
for
a
human-readable
display,
name
that
they
might
like
to
provide.
We
should
also
auto-suggest
what
the
default
is,
which
would
be
in
the
case
of
filters
and
in
the
case
of
applications.
C
It
would
just
be
the
file
name,
so
the
display
name,
the
automatic
suggestion-
would
be
the
file
name
itself,
allowing
people
to
override
that
with
something
else.
In
the
case
of
a
pattern,
the
automatic
suggestion
would
be
the
intro
sp
this
the
name
of
the
pattern
that
we
would
have
pulled
out
from
the
yaml
itself.
D
C
Post
1.0
that
might
be
the
right
thing
to
do:
pre
1.0
we're
in
treacherous
waters
because,
like
it's
subject
to
you,
know,
subject
to
change.
D
Yeah,
that's
what
I
was
wondering
like.
I.
I
wouldn't
like
to
leave
anything
here
that
would
break
easily,
especially
because
this
changes,
so
I
can
comment
that
out
and
just
leave
it
to
do
that.
You
know
after
1.0
or
something
they
should
be
like
address
again
or
something
else.
Something
like
that.
D
Okay-
and
I
just
last
question-
is
this:
like
is
this
something
like
like
is
the
objective,
a
basic
objective?
I
know
there's
like
an
excel
file
with
scenarios,
but
at
least
like
can
we
bring
that
up
quickly
like
I
just
want
to
make
sure
like?
I
don't
think
that
they're
that
clear,
like
what
to
test
at
this
level,
because
they're
like
oriented
as
like,
like
an
end
to
end
ish-
and
this
is
an
integration
test,
so
not
sure,
maybe
the
excel
file.
D
We
could
refine
it
a
bit
like
a
little
scenario,
or
maybe
it's
just
my
confusion.
I'm
not
understanding
like
like
certain
words
that
are
being
used.
I
recall
it's
like
it's
like.
Oh,
the
upload
works,
fine,
but
I'm
not
sure
to
be
honest.
Like
talking
about
the
test
scenarios,
I
guess
spreadsheets.
C
A
A
Is
this
where
the
excel
sheet
has
been?
You
know.
D
A
Okay,
super,
oh,
it
should
be
like
yeah
go
ahead
yeah,
so
I
think
so,
I'm
not
sure
if
the
scenario
is
being
covered
or
not,
I
think
one
scenario
that
would
be
quite
one
test
case
that
would
be
quite
relevant
to
capture
would
be
so
in
patterns.
We
have
that
deployment
in
that
play,
but
if
someone
has
noticed
that
we
wouldn't
actually
does
a
lot
of
thing,
so
probably
you
would
also
want
to
test
that
out.
That
is
when
you
click
the
play
button.
A
Has
it
did
it
return,
200
up,
200
series
response,
or
it
just
returned
something
else.
Probably
that
would
be
a
good
this,
because
so,
if
it
is
a
if
it's
an
integration
test
you
you
can
assume
that
if
the
response
was
anything
other
than
200,
then
it
will
it
was.
A
It
was
a
success
because
mystery
server,
usually
basically
the
the
status
quo.
It's
a
most
of
the
time,
pretty
accurate.
So
basically,
that's
one
of
the
one
of
the
test
scenarios
that
we
would
probably
want
to
cover
and
that
will
that
may
or
may
not
be
same
in
all
of
them.
That
is,
a
filter
may
have
a
different
behavior,
while
pattern
may
have
different
one
so
right
now,
if
you
would
click
on
that
play
button
in
the
same
table.
A
A
In
that
case,
it
should
actually
return
200.
It
should
return
a
success
message,
even
if
nothing
actually
happened,
because
we
detected
that
nothing
needs
to
be
actually
changed
so
yeah.
Basically,
that's
the
scenario.
Probably
we
should
test
that
is.
Is
the
deployment
working
or
not,
along
with
the
upload.
D
Yeah
sure
it's
not
here
yet
I
haven't
got
gotten
there
yet
so,
but
it's
yeah,
as
you
say,
we
we're
going
to
at
this
this
kind
of
test
we're
going
to
mark
like
every
response
from
the
back
end
and
just
make
sure
that
the
ui
behaves
correctly
and,
of
course,
these
steps
will
like
kind
of
test
will
also
be
beneficial
in
the
end-to-end
there's
another
endpoint
folder
and
I'd
be
adding
some
like
similar
tests,
but
without
the
marks
and
just
I'm
making
sure
that
the
backing
also
is
saying-
and
you
will
send
this
kind
of
request
right-
a
response.
D
Sorry,
so
it
might
change
like
because
right
here,
we're
not
introspecting
like
or
spying
on
the
responses,
because
you
know
we're
controlling
them,
but
once
once
the
end-to-end
tests
are
worked
on,
like
I
I
feel
that's
like
it
might
be
part
of
a
different
ticket.
D
C
D
It's
just
like
a
different
test
setup,
but
it
but
it's,
I
feel
like
it's
a
lot
of
work,
but
but
at
least
the
integration
ones,
once
they're
done,
they'll
be
a
good
starting
point
for
the
end-to-end
ones
or
maybe
the
other
way
around.
I
don't
know
it's
like
everything's
happening
at
the
same
time,
so
so
about
the
scenarios.
Can
we
just
take
a
look
at
them
like
just
want
to
make
sure
I'm
not
missing
anything
like
I
don't
see
them
here
should
be
in
the
somewhere
over
here.
D
Okay,
so
show
an
error.
Okay,
I
need
to
look
for
the
errors
like
okay,
I'll,
take
a
look
like
an
invalid
response,
but
how
can
I
trigger
an
invalid
response,
like
in
in
an
actual
applic
measuring
in
install
like,
like
an
actual
like,
like
the
real
app?
How?
How
would
I
trigger
any
valid
response
like
in
the
expected
outcome?
I
see
it
show
an
error
in
the
pattern.
File
is
invalid.
D
I
think
we
need
to
expand
that
definition,
but
I
don't
this
takes
a
lot
of
time
to
maybe
we
can
take
it
offline
like,
but
but
if
that
could
be
added
to
that
to
the
issue,
that'd
be
very
helpful.
You
know.
A
Okay,
yeah
also,
actually
so,
for
this,
the
endpoint
will
return
a
non-200
response.
If
it,
if
it
doesn't
validate
the
entire
file,
sorry
yeah
yeah.
Actually
it
doesn't
returns
400.
I
think
it
returns
yeah,
it
returns.
400
401.
I
think
that's
what
that's
what
it
returns.
If
the
patent
file
is
invalid,
it
doesn't
do
that.
D
A
Yeah,
if
you,
if
you
so
the
patent
file,
actually
looks
like
this.
A
patent
file
is
going
to
look
roughly
like
this.
That
is,
you
have
a
name
field,
and
then
you
have
services
field,
and
these
are
things
to
find
what
it
looks
for
is.
Does
this
have
a
name
feed
and
does
this
have
services?
That's
it.
It
doesn't
do
any
more
any
further
validation,
because
that
that
is
part
of
try
running
that
is,
it
tries
to
create
by
a
par
it
tries
to
create
execution
plan
and
those
kind
of
things.
A
So
when
so,
if
the
endpoint
is
running
401,
that
basically
means
that
of
the
yamaha
that
we
entered
that
wasn't
quite
fitting
the
structure
of
patent.
It
doesn't
go
any
deeper
than
that,
so
that
is
actually
what
about
a
filter.
A
So
right
now,
like
the
keywords
yeah,
I
think
nobody
can
correct
me,
but
I
think
if
you
upload,
if
you
are
actually
uploading
a
filter,
it
is
going
to
be
except
it's
accepted
if
it's
not
going
to
error
out.
So
I
think
this
expected
outcome
is
for
patents
because
it
because
it's
not
a
blob,
a
binder
binary
large
object,
it's
not
a
blob,
so
we
can
actually
verify
if
it's,
if
it's
correct
or
not,
I
mean
if
it's,
if
it's
fitting
a
certain
template
or
not,
but
I
think
for
filters.
A
E
D
Sure
I'll
just
explore
a
bit
on
that
like
trying
to
get
a
failure
and
then,
if
not,
then
it
would
just
be
for
patterns
and
apps.
So
I
think
it's
clear
thanks.
A
C
A
We
are
almost
on
time,
so
last
previous
week
we
had
a
question
is
what
supported
and
onward
and
ashish
mentioned
it's
not,
and
it's
right,
viva
synthetics
by
default
is
not
supported.
You
have
to
convert
into
warzone
if
you
want
to
drop
it
into
onward
istio
or
any
data
plane
does
not
do
watch
to
warsome
conversion.
What?
If
someone
is
wondering
what
it
is?
A
It's
favoritism
they
text,
that
is,
if
someone
has
written
x86
assembly
or
any
smd,
pretty
much
similar
as
well
wave
assembly
takes,
and
that
is
basically
cpu
independent
assembly
that
complies
with
assembly
specification.
Obviously
you
can
write
that
text
and
you
can
compile
it
into
wasm
if
you,
if
you
want
to
and
then
you
can
drop
into
one
way
by
default,
it's
not
so
ashish
was
correct.
A
So
I
think
that
we
are
at
end
of
time,
as
well
as
our
agendas
for
today
pretty
good
time
to
wind
wind
up
the
call.
So
it
was
a
good
call.
We
had
we
were
short
on
agendas,
but
that's
pretty
much.
Fine,
probably
we'll
have
far
more
agendas.