►
From YouTube: Meshery Development Meeting (April 7th, 2021)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
hello,
oh
wow,
all
right
so
much
going
on
we're
four
minutes
after
we've
got
the
whole
gang
or
part
of
the
gang
this.
So
my
tardiness
is
an
opportune
time
to
say:
I'm
not.
I
was
never
intended
to
host
all
these
meetings.
A
You
were
never
your
ears
were
never
made
for
so
many
terrible
jokes.
It's
not
it's
unnecessary!
Let's
make
a
point
of
having
a
topic
today
about
identifying
next
week's
host.
Next
week's
measuring
dev
host.
A
A
If
you
don't,
please
say
something
in
the
slack
chat
and
if
you
do,
please
drop
your
name
in
and
so
there's
a
couple
of
newcomers
on
the
call
it's
time
for
us
to
get
better
introduced,
blossom.
A
Let's,
if
you
would,
will
you
introduce
yourself
and,
as
you
do
I'll
tell
you
this,
and
this
is
a
word
of
warning
for
everyone,
and
that
is
if,
in
the
meeting
minutes,
you
only
put
your
first
name
you're,
leaving
yourself
open
to
one
of
the
rest
of
us,
making
up
a
fake
last
name
for
you
and
they
aren't
always
kind
so
nice.
Well
with
that
blossom,
are
you
there?
Do
you
mind
saying
a
few
words
just
saying:
hi
yeah.
B
Everyone
I'm
new
to
the
community,
we're
relatively
new
and
I
am
from
I'm
contributing
from
I
got
to
know
of
nursery
through
she
called
africa
and
well.
I've
been,
I
think,
I've
been
settling
in
quite
nicely
with
josh
and
chimney
yeah.
So
I'm
really
excited
to
be
here
and
do
more
things
contributes
more.
A
A
Okay,
okay
got
you
got
you
got
you
perfect,
perfect
and
very
nice
to
have
you
blossom.
Joy
is
with
us
as
well.
Miss
joy.
Did
you
mind
introducing.
C
Yeah
hi
everyone,
I'm
joy,
meow
from
nigeria
and
I'm
joining.
They
are
five
contributing
to
the
mystery
cto
project
from
the
contribution
at
africa
and
yeah
I've
been
ruth,
has
really
been
a
great
help.
You
know
helping
us
get
acquainted
with
the
workflow
and
getting
you
know
started
with
our
contributions,
so
yeah
I'm
getting
looking
forward
to
working
with
everyone
and
contributing
more.
A
Good
old,
ruth,
okay,
thanks
good,
we
we
forgive
you
for
that
association,
it's
okay!
It's
it's
joy!
So
there's
there's
in
blossom!
I
think
blossom's
already
aware
of
this
joy,
you
might
have
caught
some
of
it
on
the
wednesday,
I'm
sorry,
the
monday
websites
call
the
sarcasm
flows
pretty
freely
here.
A
So
it's
entirely
out
of
love
nice
to
have
you
great,
okay,
cool.
We
got
a
couple
of
topics
lined
up
a
lot
of
times.
We
will,
on
this
particular
call
a
lot
of
times
it's
a
little
bit
more
like
a
little
bit
more
like
a
stand
up.
We
tend
to
get
into
some
of
the
nitty
gritty
focused
on
the
meshery
project
itself.
Project
is,
excuse
me
fairly
sprawling.
A
Like
I
don't
know,
there's
we
have
to
go
count
them
up,
there's
something
like
30
plus
repositories
for
measuring,
because
it's
trying
to
do
a
lot
of
things
and
eventually
it's
gonna,
do
a
lot
of
those
things
very
well
and
be
super
compelling
very
interesting
and
we're
getting
there
some
some
aspects
of
what
we're
the
all
of
you
are
currently
working
on
that
have
me
pretty
excited
I've
been
drinking
less
caffeine.
A
Recently
because
I've
been
getting
so
excited,
but
okay,
so
on
this
call
we
end
up
listing
down
topics
anybody's
welcome
to
list
their
topic,
drop
it
down
below
and
we
usually
put
the
person's
name
who
might
raise
up
the
topic
and
maybe
maybe
they'll
speak
to
it,
or
maybe
they
have
maybe
it's
their
question
or
something
I
don't
know.
If
I
don't
think
asuka
is
on
at
the
moment
and
so
I'll
try
to
provide
some
context
here.
Neven
you
do,
you
know,
did
you
and
you
know
who
put
this
in?
A
Oh
okay,
I
don't
know
why
you
look
guilty.
I
think
it's
because
you're,
the
only
one
that
has
your
webcam
on
so
speaking
of
webcams
are
most
welcome
here.
Please
please
indulge
us
with
your
lovely
faces,
so
there's
a
so
ci
is
continuous
integration.
So
suco
is
saying
the
continuous
integration
for
measuring
he's
identifying
it,
as
maybe
there's
a
number
of
workflows
that
could
be
combined
in
order
to
decrease
the
amount
of
time
that
it
takes
to
build
the
various
components.
I
agree
from
my
part.
A
I
agree
that
it's
not
that
we
necessarily
have
too
many
workflows
or
that
they
need
to
be
combined
in
some
respects.
They
need
to
be
perhaps
separated
such
that
they're.
Only
certain
workflows
are
only
being
being
invoked
as
appropriate.
A
So
so
I'm
going
to
cover
this
topic
really
quickly
and
then
say
that
there's
a
bi-weekly
meeting,
a
ci
meeting
that
happens.
That's
where
this
topic
is
perhaps
a
lot
more
appropriate.
So
if
all
of
you
are
aren't
familiar
with
this,
yet
I
think
most
of
you
are
but
there's
a
community
calendar
you
can
find
the
community
calendar
by
going
to
meet.layer5.io
the
calendar.
Is
you
can
see
it
visually
here?
We've
got
some
she-code
africa
happening
or
happened.
A
You
can
subscribe
to
the
calendar
here
so
that
that
button
will
take
you
to
the
same
page
that
we
were
just
on
on
thursdays
and
so
in
fact,
tomorrow
afternoon
here
there's
a
continuous
integration
working
group
meeting
that
happens.
So
this
is
a
great
topic
for
that
meeting,
but
to
give
everyone
a
particular
topic
and
and
for
just
how
the
continuous
integration
inside
of
measuring
and
across
all
the
layer
five
projects
generally
works,
is
that
they're
generally
driven
from
github
actions
from
workflows,
defined
and
run
by
github
actions.
A
Those
work
there's
so
here's
a
list
of
different
workflows,
the
workflows,
their
actual
definition,
is
under
dot
github.
A
So
rather,
if
you
go
to
the
code
base,
if
you
go
to
the
mastery
code,
you
go
to
github
the
workflows,
folder
and
there's
one
two
three
four
five,
six
six
of
these
here's
an
example
of
maybe
why
these
are
segregated.
A
There's
a
there's,
a
small
workflow
here,
to
send
a
notification
into
the
buzz
channel
in
slack
whenever
someone
stars
one
of
the
repositories
so
you're
welcome
to
try
anyone's
welcome
to
try
it
right
now,
if
you
star
really
any
of
the
repositories
within
the
layer,
five
org
that
will
invoke
this
workflow,
there's
a
copy
of
this
workflow
in
each
repo.
A
It
just
grabs
the
current
count
of
the
number
of
stargazers
and
sends
a
small
message
to
the
the
buzz
channel
in
which
is
this
channel
by
id
anyway.
That
orients
you
a
little
bit
with
the
workflow
the
fact
that
workflows
and
ci
happens
here.
Some
of
these
only
need
to
be
kicked
off.
A
You
know
at
certain
times
like
hey
this.
One
only
gets
kicked
off
literally
when
that
that
type
of
event
happens
when
some
of
them
like
from
mesri
ctl
that
command
line
client.
Well,
this
one
messy
ctl
needs
to
get
built,
mostly
whenever
there's
a
change
to
code
under
that
folder
under
the
meschery
ctl
folder.
If
there
isn't
change
the
code
in
there,
then
it
doesn't
necessarily
make
sense
to
build
it.
So
we
can
save
time
by
not
building
it.
Asuko
is
brought
up
a
great.
A
A
There
is
one
thing
that
he's
been
working
on
recently
is
ensuring
that
we're
publishing
helm
the
mesri
helm
chart
with
every
single
meschery
release
so
abhishek.
I
asked
you
recently
to
look
at
one
of
asuka's
prs
on
this.
A
I
ideally
so
I'll
try
to
pull
up
the
the
pr
but
abhishek
you
want
to
give
everybody
context
for
this.
A
A
While
abhishek
works
on
his
microphone
I'll
I'll
say
that
if
you're
not
so,
you
can
install
meshri
a
few
different
ways.
One
way
is
using
a
tool
called
helm.
It's
a
very
popular
way
to
install
applications
on
kubernetes.
A
A
Its
description
needs
to
update
on
almost
every
time
that
we
make
a
release
of
measuring
things
in
there
might
change
the
way
that
we
install
measuring,
might
change.
There
might
be
a
new
adapter
or
the
or
any
number
of
things
might
change.
We
didn't
have
the
release
of
that.
Those
helm,
charts
automated
in
the
past
and
so
asuco
is
making
sure
that
we're
doing
that.
E
So
this
particular
change
is
based
on
something
called
values.yaml
which
is
supported
by
the
chart.
So
we
we
just
list
down
the
list
of
adapters
that
we
need
to
run
in
the
values.yaml
manifest
and
basically
meshi
ctl
would
take
care
of
it
and
it
would
start
the
appropriate
adapters
while
deploying
machinery
in
the
kubernetes
cluster.
A
Nice
and
then
abhishek
as
we
go
to
to
merge
this
update.
So
two
things
asuko
ended
up,
making
a
github
to
publish
to
compile,
to
create
helm,
charts
and
publish
them.
A
A
A
Well
is
we're
publishing
helm
this
helm
chart
to
the
artifact
hub.
A
Or
rather,
meshri
is
available
on
the
artifact
hub,
so
this
is
artifacthub.io.
If
you
search
for
meshri
there's
a
bunch
of
helm-based
applications
that
people
can,
you
know,
install
meshery
is
one
of
them.
There's
a
couple
of
issues
like
here.
One
is
that
I
don't
know
why
the
chart
itself
doesn't
really
need
its
own
version.
A
A
If
they're
trying
to
install
mesh
for
using
helm
chart
and
the
charts
carrying
one
version,
mescheri
is
carrying
a
different
one,
that's
kind
of
it
and
a
side
issue
that
we
should
make
sure
to
follow
up
on
the
other.
One
is
okay:
if
this
chart
is
being
published
here
and
there's
an
edge
version
and
a
stable
version.
A
A
This
is
good
yeah,
so
linker
to
jaeger,
linker
to
jager
edge,
stable,
biz
viz
edge
stable
same
one.
Yeah
looks
like
a
pattern
that
others
have
chosen
to
do
as
well
so
abhishek.
If
you
it
sounds
like
unless
there's
a
dissenting
opinion
or
a
different
view.
F
F
A
I
think
it's
less
confusing
for
users
when
there's
just
one
version
they
don't
it
would
be.
It
may
be
important
to
us
if,
like
see
as
an
example,
they're
using
the
same
chart
version
is
the
same
as
their
release
version,
which
I
think
is
helpful.
If
I
wanted
to
go
back
in
time
to
an
older
version
of
linker
d.
Well,
I
would
go
I
I
can
see
what
version
linker
d
that
is
here,
because
the
chart
versions
are
the
same
as
the
application
version.
A
A
Nice:
okay,
unless
somebody
hasn't
comment
there
we'll
go
forth
with
to
push
on
a
system
restart.
G
Hello
hi,
so
let
me
just
share
my
screen.
Okay,.
A
G
Okay,
so
this
is
about
like
the
mystery
system.
Restart
navendur
is
the
issue
that
we
should
kind
of
follow
the
original
kubernetes
way
of
restarting
pods
that
is
terminating
them
and
then
restarting
them.
So
that
was
the
issue,
and
this
is
what
I
did.
G
Okay,
my
pc
is
slow.
Please
be
patient,
okay,
so
previously
what
we
were
doing
here,
that
we
were
stopping
measuring
completely
and
then
we
were
starting
it
from
the
like
very
scratch,
then
what
I
did
was
like.
I
was
checking
the
current
flat
platform
and
to
for
docker
I
I
did
the
same
as
before
and
for
the
kubernetes
part.
What
I
did
is
I
grab
pod
interface,
then
the
port
list.
What
are
the
pods
running
with
the
namespace
meshery
and
then
I
kind
of
deleted
them.
Yeah
parts
dot,
delete
and
I
deleted
those
ports.
G
G
A
A
Have
you
run
into
any?
Are
there
any
corner
cases
that
we
need
to
be
considerate
of?
So
if
you
delete
the
pods
and
then
reapply
them
do
they
do?
What
do
we
do
if
they
don't
start
running
again.
G
Okay,
so
yeah,
I
haven't
like
thought
about
that
thing,
because
I
read
in
the
kubernetes
dock
that
if
we
want
to
start
restart
a
running
port
any
like
just
by
default,
we
just
delete
them
using
cube,
ctrl
delete
parts
and
the
command
the
port
name
and
then
namespace
after
that,
and
it
won't
like
it
was
not
mentioned
there
that
if
there
will
be
any
case
when
we
can,
it
will
fail
or
something
like
that.
G
A
Yep
yeah:
it's
not
supposed
to
have
an
error,
but
but
it
happens
like
maybe
it
couldn't
the
images
weren't
cached
in
or
were
never
cached
and
it's
trying
to
reach
out
to
pull
down
the
images.
But
it
can't
yeah.
G
G
A
Whole
port
yeah
yeah.
Technically
it
doesn't
mean
those
things.
I
guess
what
I'm
trying
to
tell
you
like.
No,
actually
it
doesn't
literally
mean
that,
like
the
images
in
fact
have
always
been
on
docker
hub,
it
might
mean
that
your
kubernetes
system
can't
talk
to
docker
hub.
It
might
mean
that
docker
hub
is
currently
rate,
limiting
pull
requests
from
your
machine.
It
might
mean
that
the
the
images
on
your
machine
are
on
the
kubernetes
cluster
are
cached
or
or
maybe
they're
not.
I
mean
it
actually
could
mean
a
lot
of
things.
A
It
could
mean
that
you're
out
of
space
on
your
kubernetes
cluster,
so
in
the
time
that
those
got
those
stopped
other
containers,
spun
up
or
just
and
consume
that
space
or
other
processes
consume
that
space.
So
now
you
try
to
start
them
all,
but
they
won't
all
start
because
there
isn't
enough
space
like
or
there's
not
enough
memory
to
start
them
and
there's
there's
a
long
list
of.
G
G
G
A
G
A
All
right,
yeah,
no,
I
great
yeah,
do
your
question.
I
don't
think
that
we
should
check
status
on
when
you
invoke
the
restart
command.
One
thing
that
we,
I
don't
know
I'm
I'm
of
two
minds
about
like
I'm,
not
sure
if
we
should
use
the
term
restarting
here
or
like
especially
since
this
is
debug
we
might
want
to
say
deleting
pod
or
like
in
parentheses
like
restarting
in
parentheses,
deleting
or
like
deleting
in
parentheses,
then
restarting
just
because,
like
yeah,
it
is
the
command
that
they
invoked.
A
G
A
H
A
A
And
then
oh,
the
vendor,
push,
do
you
know
so
so
that's
a
great
or
you
know
so
yeah.
I
think
that.
A
Well,
I
think
we
are
getting
consensus
that
like
yeah,
including
the
word,
delete
or
something
and
they're
deleting
in
a
in
the
since
it's
a
debug
statement
like
that'll
that'd,
be
great,
you
don't
have
to
necessarily
make
a
change
now.
What
have
you
but,
but
the
other
thought
is
for
for
the
the
messages
that
the
user
sees.
A
G
The
stop
and
start
have
their
own
logs,
like
in
full
logs,
but
in
kubernetes
I
didn't
like
I
couldn't
thought
of
any
thing
to
print
information
logs
or
such
kind
of
logs.
So
in
kubernetes
we
are
only
printing,
a
restarting
machine
as
info
log,
and
the
this
part
is
real.
That's
that's
that's
what
I
did
here.
A
Oh
got
it
okay,
so
yeah.
That
makes
some
sense
like
if,
if
you're
not
checking
on
the
status
of
the
pods,
then
those
subsequent
info
lines
can
be
a
little
bit
like
if
you're,
to
include
two
subsequent
info
lines.
A
It
would
probably
be
something
like
a
restarting
messaging
delete,
deleting
pods
you
know
such
and
such
and
then
after
they're
deleted.
Then
you
know
sitting
there
and
waiting
and
pulling
for
when
they
come
back
and
then
showing
the
fact
that
they're
now
restarted
that's
kind
of
a
lot.
I
don't
know
that
that's
the
behavior
that
just
thinking
aloud
with
you
like
and
trying
to
think
aloud
with
the
vendor
and
nude
kosher
official
anybody
else.
A
A
What's
the
expected
behavior
here
like
for
the
consistency
of
user
experience,
do
you
all
feel
that
just
you
know
shooting
out
the
command
to
delete
the
pods?
And
you
know
whatever
whatever
happens,
kind
of
kind
of
happens
or
do
you
you
all
feel
that
that
need
that
command
needs
to
be
a
bit
more
orchestrated
and
logged
to
the
user.
A
H
Had
suggestion,
basically,
we
are
looking
through
the
part
list
right
so
would
it
make
sense
to
display
the
pod
name
right
whenever
something
is
being
stopped
and
restarted
so
deleting
pod
and
the
pod
name?
And
after
that
I
mean
at
line
number
89.
We
could
say
that
restarting
part.
Okay,.
H
G
A
Your
suggestion
makes
a
ton
of
sense
because
yeah
it
you
know,
maybe
it
doesn't
even
need
explaining
like
that,
makes
a
ton
of
sense.
We
should
probably
you
probably
take
that
suggestion
and
run
with
that.
One.
G
Okay,
like
info
logs,
I
will
be
writing
blocks
here
that
deleting-
and
you
know.
A
What
based
on
time,
actually
I'll?
Let
hussein
kind
of
give
you
some
more
direct
feedback
after
this
yeah
after
the
demo,
like
hey,
successful
demo,
you're,
getting
all
kinds
of
feedback.
A
All
kinds
of
unwanted
feedback-
that's
great
anybody
else,
have
any
other
quick
comments
before
we
conclude.
A
Nice,
it's
great.
It's
amazing
how
just
the
smallest
simplest,
you
know
you
know,
features
or
commands
can
take
so
much
thought
so
much
feedback.
A
That
said,
that's
what
makes
something
feel
really
good.
Is
the
attention
to
super
small
details,
congrats
piece
that
that's
pretty
cool,
that's
great,
all
right!
Okay,.
D
Yeah
but
basically,
what
that,
why
I
put
it
here,
was
like
we
discussed
about
like
how
to
version
the
components
of
measuring
docker
hub.
Currently,
we
only
tag
the
measuring
version
according
to
the
github
release,
but
we
don't
tag
the
version
of
the
other
components.
A
Yeah,
so
there
was
an
intermediate
suggestion
to
allow
people
to
yeah.
Do
it
I
think
exactly
what
you're
highlighting
here
like
within
the
config
within
mesh
config,
yeah,
you've
said
it
here,
yeah
great
okay,
what's
the
question
or
is
it
just
a
demo
and
kind
of
a
group
discussion.
D
Yeah
the
question
is
like
like
we,
we
cannot
get
an
specific
version
of
an
sdo
image
from
measuring
in
docker
hub
like
so.
If
the
user
set
sets
his
version
as
we
will
be
4.5,
he
can
he
he
won't
be
able
to
like
get
the
image.
A
Oh
then,
that's
a
bug
like
like
that
should
be
happening.
That
should
be
the
case.
You
pointed
one
out
recently
where
that
was
just
a
bug,
but
the
system
itself,
the
release
workflow,
does
does
tag
each
of
the
adapter
images
with
those
tags.
A
Okay,
I'm
just
gonna
randomly
I'll
I'll
hit
console
here,
so
this
is
the
measuring
adapter
for
console.
If
we
click
on
the
tags,
it's
been
a
while,
since
we've
had
a
release
so
about
three
months
ago,
the
last
time
that
there
was
a
release,
there
are
two:
there
are
sometimes
three
tags
that
are
given
to
a
single
image.
Let
me
increase
the
font
here
so
for
this
particular
image.
It
has
this
digest:
aa3
a3
a83
and
then
this
is
a
different
release.
A
So
88
you
know
so
okay,
so
this
is
the
same
image
with
three
tags.
It
turns
out
this.
This
carries
the
stable
latest
tag,
which
is
just
a
moving
tag
for
the
latest,
the
exact
latest
image-
and
this
this
is
the
latest,
so
it
has
it
it
also,
and-
and
this
one
moves
you
know
each
and
every
time
that
there's
a
release
this
one
and
this
one
they
don't.
A
This
one
is
a
human
readable
like
what's
the
version
number,
what's
the
release
channel,
it's
the
stable
release
channel.
What's
the
version
it's
this
and
then
this
other
one
is:
it's
always
been
questionable
as
to
whether
or
not
to
have
this
other
one.
This
is
the
commit
sha
of
the
the
git
commit
sha,
but
it
also
sticks
with
the
image.
So
these
two
stay
with
the
image.
This
one
moves.
So
if
we
look
at
like
the
image
prior
well,
it
was
a
an
edge
release
and
it
has
two
tags.
A
This
is
this
image:
888
f
a
data,
two
tags
latest
edge
release
latest,
so
we
go
back
in
time
to
like
the
last
time
a
stable
was
done.
Okay,
here's
the
the
next
latest
stable.
So
it
has
this
git
commit
shaw
and
the
version
number
which
is
one
prior
and
then
it
doesn't
have
the
latest
tag.
That's
because
the
latest
tag
moved
so
the
menu.
A
I
don't
know
I'll,
leave
the
proof,
the
burden
of
proof
of
bug
on
you
and
say
like
hey
from
from
the
perspective
of
what
we
need
to
accomplish
here,
yeah.
We
would
like
for
the
user
to
be
able
to
specify
stable,
hyphen
v04.2
and
if
it
so
happens
that
that
tag
is
unavailable.
That's
a
one-off
issue
that
is
hopefully
not
indicative
of
a
systemic
ci
workflow
issue,
but
it
could
be.
A
Gotcha
cool
then,
and
then,
by
the
way
on.
That's
great,
thank
you
for
that
diligence
in
the
venue
by
the
way
like
it
is
of
absolute
zero.
It's
a
negative
value
for
us
to
go
back
in
time
and
assign
those
older
releases,
those
tags.
It
is
a
value
to
make
sure
that
that
this
that
going
forth,
that
like
it,
is
a
value
to
identify.
A
Maybe
why
a
particular
image
is
missing
a
tag
if
it
isn't
from
one
of
us
humans
doing
it,
then
we
probably
have
an
issue
like
we
just
need
to
make
sure
that
the
workflow
systems
itself
themselves-
you
know,
are
tagging
and
if
so
long
as
they're
tagging,
like
that's
what
that's
the
fix
that
we're
concerned
with
we're
not
really
concerned
with
fix,
like
re
re-tagging,
something
because
we
have
a
hard
enough
time
trying
to
get
users
to
use
the
latest
stuff
anyway,
much
less
the
old
stuff.
A
Second,
so
while
anish
is
preparing
navindy,
do
you
want
to
introduce
the
topic.
D
Yeah,
so
we
are,
we
are
recently
adding
some
new
commands
to
sub
commands
to
measure
ectl
pattern.
We
currently
have
commands
to
apply
and
delete
a
pattern
and
we
are
also
adding
support
for
viewing
in
the
pattern
and
listing
out
the
patterns.
So
anish
has
been
working
on
measuring
ctl
pattern
view,
which
will
which
will
let
the
user
view
a
particular
pattern
that
they
have,
and
I
guess
ganesh
has
already
appeared
already.
E
So
you
guys
can
see
my
screen,
so
we
see
currently
mastery
already
has
support
for
uploading
and
applying
and
deleting
the
pattern,
but
like
recently
in
a
new
pair,
I've
added
support
to
view
these
patterns
from
the
mystery
cdn.
E
Yes,
so
we
have
added
support
to
view
a
certain
pattern
based
on
its
id
or
name.
Apart
from
that,
you
can
also
view
all
the
patterns
that
are
currently
uploaded
and
also
set
in
which
output
format
we
want.
Currently
we
have
support
for
json
and
yemen,
so,
like
yeah,
what
we
can
do
is
we
can
do
mystery
city
pattern
view,
and
I
can
then
provide
a
pattern
to
open
which
I'm
going
to
search
on.
So
let's
just
say,
I
want
to
search
for
pattern
now.
E
This
command
also
requires
a
token,
so
we
have
also
added
a
system
wide
token
flag
to
the
patents
of
command
and
can
do
so.
I
would
get
you
know
what
it
will
do
is
it
would
search
it
would
do
a
get
request
to
the
server
and
if
it's
a
name,
you
know
it
will
search
for
it
would
search
for
the
pattern
in
it.
E
So
when
she
supports
a
get
request
in
which
you
can
search
by
pattern
name
and
what
simply
this
mystery
ctm
will
do
is
take
out
the
first
result
and
code
it
so
currently,
you
know
the
pattern
that
I
have.
It
has
a
pattern
name
of
pattern,
so
it's
the
closest
match.
That's
why
it's
showing
you
now.
I
can
also
search
using
the
id
as
well,
so
these
ids
are
basically
a
uuid
v4,
so
the
measuring
machine
is
intelligent.
Enough
to
you
know
understand
if
you
have
provided
an
uid,
e4
or
just
a
simple
name.
E
E
E
Apart
from
that
we
can.
We
have
also
support
for
changing
the
you
know:
output
format
to
json
for
all
the
you
know
commands
you
can
do
this
for
like
a
single
pattern
as
well
and
for
all
the
patterns,
so
you
can
get
just
one
response
so
yeah,
that's
all
for
the
pattern.
User
command.
A
Major
major
doubts
here
I'm
this
is
this-
is
pretty
terrible.
I'm
not.
I
hope
you
hope
you
can
see
the
fat
smile
on
my
face.
Any.
A
Actually,
the
the
issue
that
you
bumped
into
with
well
like
trying
to
provide
an
intuitive
user
experience
where
you'd
let
the
user
search
for
the
pattern
by
name
or
by
id,
like
whatever
their
preference
yeah.
I
didn't
it
didn't
occur
to
me
that
oh
well,
you
sort
of
need
to
know
like
which
endpoint
is
appropriate
to
query
based
on
you
know,
and
the
fact
that,
like
you,
that
you
won't
be
able,
like
you,
can
see
on
your
screen
right
now,
the
there's
an
id,
it's
a
it's
a
uuid!
A
But
maybe
just
the
first
quadrant
or
the
first
sectant
or
whatever
it
is.
E
E
We
do
not
have
you
know,
support
for
searching
through
id,
it's
searching
through
name
or
directly
use
the
id.
A
Yeah,
it
might
be
that
we're
that
when
I
say
we,
I
guess
I
should
like
I'm
putting
too
much
work
on
us
that,
like
hey,
maybe
we
should
just
choose
name
as
it's
more
as
a
that's.
What
we're
mostly
showing
people
like
when
you
do
the
I
don't
know
if
we
have
it
yet,
but
if
you
do
a
mess
for
ctl
patterns
or
I'm
sorry
measure
ctl
pattern
list
in
the
default
output
there.
I
don't
believe
that
the
id
is
shown
or
is
intended
to
be
shown.
A
Correctly,
like
it,
it
won't
it'll
just
show
a
name,
and
so
if
and
that's
what's
generally
human
readable
and
friendly
to
see
that
it
would
probably
be
the
name
that
people
would
mostly
be
trying
to
view
they'd,
say:
okay,
well,
there's
there's
ten
of
them
here
I
want
to
get
more
details
on
this.
One
they'll
copy
that
name
and
then
you
know
view
that
and.
A
I
guess
there's
a
and
that's
just
generally
easier,
there's
a
couple
of
questions,
though
utkarsh.
Do
you
recall,
like
the
example
that
we're
seeing
here
the
name
of
the
pattern?
It's
pattern,
two
dot
yaml,
so
the
name
of
the
pattern
is,
is.
B
A
E
Them
that
was
the
name,
so
if
you,
if
they
are
getting
uploaded
from
the
ui
so
right
now,
whatever
the
file
name
is
going
to
be
that
that
filing
is
going
to
be
kind
of
the
pattern
link,
but
actually
that
implementation
will
need
to
change.
A
Nice
yeah,
because
it
because
you
could
ima
like
I
would
imagine
that
most
people
would
probably
think
that
they
would
do.
They
would
just
use
pattern
to
like
they
wouldn't
have
to
type
in
the
extension
of
the
file
and
that
yeah
if
they
gave
it
a
separate,
descriptor
or
separate
short
name
that
yeah
that
they
would
refer
to
it.
E
Actually
for
searching,
I
don't
think
you
have
to
I
mean
or
not
that
not
saying
that
the
previous
implementation
should
not
change
that
should
change.
I
mean
I
mean
assuming
that
the
file
name
is
going
to
go
bad
and
finally,
it's
not
a
good
assumption,
but
by
searching
the
api
actually
supports
that
you
can't
just
type
the
initials
of
the
pattern
and
it
will
actually
run
backward
list.
It
should
actually
run
out
for
this.
E
A
So
anish,
I
don't
know
a
little
bit
of
this-
is
hard
to
know
at
the
moment,
like
even
for
the
way
that
the
view
command
works.
So
so
we
we've
said
that
when
we
design
out
measuring
ctl,
we
want
for
the
experience
to
be
intuitive.
It's
a
user
experience.
A
Okay,
part
of
what
helps
make
user
experiences
intuitive
is
that
things
are
familiar
like
the
same
interfaces
are
familiar.
So
what
are
people
familiar
with
generally
in
the
cloud
native
ecosystem
with
cli
well
they're,
familiar
with
docker
cli
and
cube
ctl,
cli,
broadly
okay?
Well,
in
if
you're,
using
docker?
If
you
recall
last
time
you
used
docker
command,
you
did
a
docker
list
or
docker
ps.
A
It
would
show
you
the
list
of
containers,
and
if
you
wanted
to
fully
describe
one
or
look
at
one
in
more
in
depth,
you
could
either
use
the
short
name
given
to
it,
which
is
basically
it
you
can
use
its
id.
You
can
use
its
short
name
and
either
way
you
don't
have
to
specify
which
one
you're
using
you
just
use
it
and
docker
cli
figures
it
out.
Well,
that's
nice!
A
I'm
not
saying
we
have
to
live
up
to
just
that,
but
I'm
just
that's
just
an
example
of
like
in
cube
ctl
you
as
we
reflect
on
pattern
view
if
and
I
think,
there's
an
open
question
like.
Should
we
just
do
pattern
view
and
show
everyone
the
full
description
of
all
the
pattern
files,
maybe
except
if
they
have
like
15
pattern
files.
A
Lo,
you
know
loaded
like
even
one
pattern
file
might
get
a
little
bit
lengthy
and
if
we
print
all
10
or
15
or
just
even
three
to
the
screen,
it
might
be
a
lot
of
output
which
might
give
credence
to
all
you
know
to
if
someone
wants
to
do
that,
to
forcing
them
to
use
an
all
flag,
a
dash
dash
all.
A
Maybe
that
said,
if
you
reflect
on
what
how
cube
ctl
behaves
if
memory
serves,
if
you
do
cube,
ctl
describe
pods
like
a
type
of
a
thing
and
not
a
specific
pod,
but
just
pods.
I
think
it
prints
out
all
the
full
description
of
all
the
pods
you
might
have,
which,
which
is
really
long.
A
A
I
think
it's
okay,
that
or
rather
also
I'll,
say
the
commands
that
you're
writing
now.
They
will
no
doubt
change
over
time,
as
some
of
this
becomes
better
understood
that
better
understood
that
the
common
use
is
that
people
have
hundreds
of
pattern,
files
or
commonly
they
have
four
or
that
that
the
pattern
file
that
in
the
future,
not
only
can
you
identify
a
pattern
by
its
id
by
its
file
name,
but
also
by
a
separate
descriptor
like
a
short
display,
name
or
or
name
that
anyway.
Some
of
that
will
impact
how
this
this
functions.
E
A
It
might
be
in
the
list
command
if
you
would
anish,
if
you
haven't
like,
also
reflect
on
what's
described
in
the
list
command,
because
that
may
inform.
Let
me
inform
this
or
change
part
of
what
this
is,
because
I
yeah
this
one.
A
Yeah,
if
we
were
to,
if
one
of
the
versions
of
pattern
view
was
to
give
it
a
tabular
view
or
to
print
this
out
in
tabular
format,
I
think
the
reason
that
it's
printing
out
in
json
one
is
because
that's
this
json
is
the.
I
think
the
currently
supported
format
for
creating
a
new
pattern
file,
and
so
the
thought
was
you
can
sort
of
import
export
like
this.
You
can
view
and
manipulate
it
and
directly.
A
You
know
upload
a
new
one.
A
E
No
like
like,
based
on
this
currently
like,
I
wouldn't,
of
course,.
E
A
We
we
are
at
time
saved
by
the
bell
it
would
karsh
in
the
vendor.
I
guess
that's
anything
that
we
missed
for
anyone
today.
Anything
urgent.