►
From YouTube: Octant Community Meeting - April 15, 2020
Description
April 15, 2020
Agenda
Update on 0.12
combined logging
plugin API changes (ActionRequest)
navigation fixes
breadcrumbs
Documentation
Updating docs to be more user friendly
Implementing search on the docs for even more user friendliness
End-to-end testing
Demo
Open Q&A - add your questions here
A
Hi
everyone
and
welcome
to
the
Auckland
community
meeting
today
is
April
15,
2020
and
per
usual
get
a
bunch
of
status
updates
to
go
through
and
if
you
want
to
add
something
to
the
open
Q&A.
Please
do
so
here
in
the
hacking
D
and
let's
share
my
screen.
So
you
all
can
see
the
agenda
then
I'm
gonna
hand
it
over
to
Wayne.
B
B
We
had
mentioned
last
week
that
we
are
looking
at
doing
something
early
this
week,
potentially
Monday
or
Tuesday,
that
God
held
that
mean
by
me,
because
I
I,
wrapped
up
a
couple
PRS
that
have
some
implications
around
plugin
API
changes
and
also
added
the
combined
logging
so
and
I
want
those
to
be
part
of
o
at
12.
So
we're
we're
gonna,
wait
for
those
to
get
reviewed
and
get
merged
in,
but
I
wanted
to
just
talk
about
them.
Briefly,
I,
don't
I,
didn't
link
the
actual
items
in
the
agenda.
B
B
So
this
is
the
combined
logging
PR,
and
so
this
fixes
is
there's
a.
There
was
a
couple
outstanding
issues.
One
was
the
just
to
get
all
of
the
all
of
the
logs
for
all
of
the
containers
that
were
part
of
a
pod
and
then
the
other
one
was
to
be
able
to
look
at
all
of
the
descendant
pod
logs,
so
so
any
like
throughout
the
history
of
this,
this
pod
existing
being
able
to
see
all
of
the
the
logs
from
various
containers.
B
So
and
then
there
was
another
part
of
this
which
was
plugin
authors
currently
we're
having
to
create
a
list
of
explicit
containers
that
they
would
then
pass
in
and
and
get
new
logs
for
each
individual
container
most
of
the
time.
What
they
want
to
do
is
just
call
new
logs
and
and
and
get
all
of
the
log
data
and
go
through
it
themselves,
similar
to
when
you're,
using
cube
CTL,
and
you
do
all
containers.
So
this
PR
kind
of
covers
all
all
three
of
those
things.
B
B
The
the
next
one
that
I
wanted
to
cover
is
one
I
just
put
up
today
that
involves
plugins,
and
so
this
is.
This
will
actually
be
a
a
breaking
change
for
the
plugin
API,
specifically
to
the
action
request.
So
what
this
does?
Is
it
it's
the
start
of
enabling
plug-in
authors
to
handle
internal
octant
actions
currently
in
this
PR
we're
only
going
to
expose
a
single
action,
which
is
the
set
name,
space
action?
B
If
you
have
some
type
of
long-running
task
or
work,
that's
polling
data
you'll
be
able
to
interrupt
or
cancel
that
context
and
switch
and
restart
to
work
with
the
new
namespace
instead
of
having
to
well
right
now
you
just
you,
don't
know
you
actually
don't
you
would
have
to
you
can't
do
it
right
now,
so
this
this
enables
you
to
do
it
in
a
way
that
is
easy
and,
and
people
are
familiar
with,
so
it
does
change
the
action
request.
The
service
action
request
object
to
now
include
an
action
name
previously.
B
So
in
action,
if
Jonas,
if
you
click
on
the
files,
changed
and
scroll
down,
just
a
little
bit,
they'll
be
a
file
and
they're
called
doc
go,
which
is
the
yeah
that
one
there
so
we've
added
a
doc
doc
go
file
for
this
to
kind
of
show
how
you
can
use
this.
These
actions
within
your
plug-in
I,
don't
know
of
anyone
who
is
actually
doing
this
manually
like
attempting
to
use
them
before.
So
it
probably
will
not
impact
a
whole
lot
of
people.
B
But
if
you
do,
if
you
were
using
actions
in
your
plugins,
the
action
request,
object
is
changing
and
it
would
and
is
now
going
to
include
this
action
name
field
and
so
you'll
need
to
rebuild
once
we
release.
Oh,
that's
what
we'll
be
sure
to
to
really
let
people
know
that
that's
happening
and
be
very
remind
folks
frequently
that
there's
a
plug-in
API
breaking
change
happening
and
then
the
next
thing
I
wanted
to
cover
was
just.
B
There
was
a
handful
of
fixes
for
the
nav
just
a
handful
of
small
improvements
that
Milan
has
been
working
on,
adding
more
tests,
improving
the
the
current
selection
and
just
general
cleanup
and
refactoring
of
some
things.
So
that's
all
going
to
be
a
part
of
Oh
doc
12
as
well.
That
is
number
eight
for
three
quickly
clean
it
up
later.
So
that's
843.
A
C
B
So
yeah,
so
moving
on
I
wanted
to
talk
about
documentation.
That
has
been
something
that
we
have
been
talking
about
in
the
last
few
community
meetings.
Sam
has
started
some
work
around
getting
our
component
library
and
some
examples
around
that
documented
and
I
have
just
started
on
doing
some
work
around
getting
a
user
guide
for
octant,
dev
going
and
so
I
just
wanted
to.
Let
folks
know
that
we
are
giving
the
attention
and
we're
giving
it
some
priority
and
we're
hoping
to
have
a
good
round
of
new
and
updated
documentation.
B
A
B
And
I
didn't
make
a
note
of
this
on
the
edge
in
Thank,
You,
Jonas
I.
Think
that's
great
I
that'll
be
useful.
Once
we
have
documentation,
that's
worth
searching
it's
quite
there
yet,
but
yeah.
That's
that's
excellent.
I
want
I,
didn't
put
this
on
the
agenda,
but
I
wanted
to
call
out
Sam
recently
put
up
a
PR
for
a
proposal
to
enhance
and
redo
our
end-to-end
testing.
This
is
very
important.
B
It's
something
that
is
currently
lacking
in
octant
right
now
and
getting
getting
this
kind
of
refresh
updates.
Our
existing
end-to-end
testing
will
really
help
create
a
much
more
confidence
level,
and
not
only
all
of
our
PRS
that
were
putting
in,
but
also
the
releases
that
we're
putting
out
and
I
think
it's
going
to
greatly
reduce
the
amount
of
regressions
and
and
just
like,
even
small,
surface
level,
bugs
that
we,
you
have
been
seeing
released
to
release
so
I
just
wanted
to
call
that
out
and
say.
E
Yeah
I
didn't
really
have
too
much.
I
might
update
the
proposal
as
we
start
taking
a
stab
at
it,
and
we
do
have
some
left
over
I
guess
those
good
starting
based
from
the
previous
attempt
as
well,
and
so
we're
still
using
the
same
tech.
We're
just
going
to
be
smarter
about
how
we're
doing
at
this
time-
and
hopefully,
it'll
lead
to
a
point
where
we
just
don't
feel
like
it's
a
green
checkmark
that
our
code
has
to
run
through
and
we
feel
like
it's
doing
something
useful.
B
Yeah,
that's
great
and
I
also
wanted
to
mention
that
we
are
actually
I'll.
Put
this
the
link
for
know.
That's
the
wrong
hold
on
this
is
adding
the
link
for
the
proposal
for
end-to-end
testing
in
there.
I
also
wanted
to
mention
that
we
are
working
on
another.
This
is
this
is
useful.
There's
a
pull
request
up
right
now
to
implement
the
new
breadcrumbs
that
Milan
has
been
working
on,
and
that
will
also
be
part
of
or
not
12.
That's
and
that's
another
thing
that
kind
of
goes
under
that
navigational
fixes
heading
this.
B
The
feeling
is
the
same
and
an
independent
of
we're
using
octant
you'll
you'll
have
a
sense
of
how
to
move
around
and
how
to
get
back
to
where
you
were
and
I.
Think.
That's
just
going
to
be
a
really
helpful
small.
It
seems
small
but
I'll,
be
I.
Think
I'll
be
really
helpful
and
have
a
good
impact
on
general
usage
of
octa.
B
B
Think
so,
after
this
ODOT
12
release
goes,
we
were.
We
were
waiting
specifically
for
the
navigation
piece
to
be
finished,
so
once
the
once
that
12
is
released
and
we
have
the
new
navigation
and
breadcrumbs
working
then
we'll
probably
in
the
next
you'll,
probably
see
in
the
next
release,
an
update
to
just
get
all
of
the
the
baseline
feature
parity
up
to
speed
with
the
electron
app
once
the
navigation
is
there.
It
really
should
not
take
too
much
effort
to
get
that
functioning
because
we're
we're
just
going
to
get
it
to
baseline.
B
It's
just
a
feature
parity
of
what
we
have
now
we're
not
going
to
be
focusing
on
adding
any
of
the
desktop
integrations
that
we
want
to
put
in
there
for
the
first
version.
The
first
version
is
just
going
to
be
same
octant.
You
have
now,
but
just
launched
as
a
standalone
app,
so
that
specifically
Windows
users
have
a
much
better
experience
with
launching
it
and.
B
The
first
pass
probably
know
what
will
I
imagine
what
we'll
do
is
we'll
release
the
first
pass
just
to
get
folks
moved
over
to
that
version,
and
then
we
will
implement
auto
updating
as
a
separate
item,
mainly
because
there's
some
complexity
there
that
we'll
want
to
deal
with
and
handle
that
I
think
would
probably
push
out
the
release
of
the
electron
allocation
longer
than
I
would
like
I'd
like
to
get
in
people's
hands
and
get
them
using
it
and
get
them
from
any
types
of
issues.
So
so.
D
B
If
you
can't
yeah,
we
can
say.
Thank
you
so
first
thing
I
want
to
it's.
The
action
I'll
just
show
the
plug-in
I'm
here
already
on
this
pot.
I'll
show
the
log
streaming
so
to
the
user.
There
won't
be
much
difference
in
in
what
they
see
when
they
click
on
logs.
Except
now
you
are
seeing
you'll
notice.
On
the
far
left
column,
there
is
combined,
there's
there's
a
new,
a
new
field,
it's
the
Jason
one
and
Jason
T.
So
this
is
a
combined
output
of
two
containers
within
the
same
pod.
By
default.
B
D
B
B
Similar
to
like
so
like
similar
to
this,
where
it
says
all
namespaces,
we
got
on
the
cluster
review,
yeah
yeah,
absolutely
yeah.
Thank
you
yep,
so
yeah!
So
that's
that's
it
to
again
to
the
user.
There
should
not
be
much
for
us
on
the
back
end.
This
is
a
really
nice
change,
because
this
is
now
streaming
out
to
the
client
I
mentioned
in
the
previous
community
meeting.
What
we
used
to
do
before
is
we
would
take
the
whole.
B
We
would
ingest
all
of
the
log
into
memory
and
then
ship
it
to
the
client
every
five
seconds,
and
this
is
now
streaming
so
I
if
I,
let's,
this
I
think
this
would
work.
So
if
I
pop
up
in
a
port
forward
I
go
to
the
to
the
logs.
No,
my
my
service
is
broken,
so
I
can't
I
can't
actually
port
for
it.
Maybe
this
one
works.
One
of
these
works.
D
C
D
B
On
both
because
since
we're
not
so
before,
we
would
do
is
we
would
open
the
stream
can
ingest
the
entirety
of
the
log
ship,
100
lines
of
that
off
to
the
client
and
then
close,
the
stream.
Now
we
open
the
stream
and
just
the
log,
and
then
we
just
sit
with
the
stream
open
and
we
only
receive
or
send
information
from
the
API
when
there's
actually
a
new
entry
in
the
log
file.
B
B
D
D
B
B
Yeah
the
this
happen
we
last
night,
I
did
a
demo
on
a
podcast
the
other
day
and
I
was
trying
to
run
off
this
merged
crazy
master
that
wasn't
actually
well
tested,
and
this
happened
to
me
that
time
I'm
used
to
it
now
it
doesn't
even
bother
me.
Let's
see
I
can
I
can
probably
just
no
I
can't
I
can't
you
know
what
I
can
do.
I
really
want
to
show
this,
because
I
think
it's
I
think
it's
neat
anyway.
I
will,
as
I
was
gonna
talk
about
that
I'll
move
on.
B
So
the
other
thing
I
want
to
show.
Is
this
the
plugin
responding
to
the
namespace
changes,
so
you
can
see
up
there?
It
says
current
namespace.
Now
it's
default
now
it's
auxin
demo.
So
this
is
actually
the
plug-in
code
itself
registering
an
action
handler
that
receives
the
action
from
octant
when
the
namespace
changes.
B
You
can
imagine
this
being
extended
to
things
like
when
the
context
changes
other
other
events
that
might
happen
within
with
an
octant
right
now,
the
only
one
that
we're
putting
into
the
package
so
that
it's
public
is
the
namespace
one.
That's
the
one
that
is
needed
for
a
plug-in,
that's
currently
being
worked
on,
but
as
as
needs
arise,
we'll
continue
to
add
them.
Adding
them
does
not
break
in.
It
does
not
create
any
breaking
API
changes.
B
And
that's
that
so
that's
it
for
for
the
for
the
action
stuff!
It's
it's
pretty!
It's
pretty
neat!
It's
it's!
It's
an
important!
It's
really!
It's
really!
It's
a
good
step
in
the
right
direction.
So
there's
there's
been
a.
This
has
been
an
open
issue
originally
opened
by
the
by
Jason,
who
was
working
on
the
Tecton
plugin.
He
originally
opened
this
issue
a
few
months
back
and
so
having
this
can
this
work
completed
now
I
think
is
going
to
be
really
useful
for
a
lot
of
folks.
B
It's
great
okay,
so
one
last
thing
or
gonna
try
this
again:
I'm
gonna
go
I,
think
I,
fixed
I,
think
I
fixed
my
my
Jason
server
I'm
gonna
go
try
and
find
out
right
now
and
if
I
did
then
we
can,
we
can
do
the
I
can
show
the
log
streaming
yeah.
Okay,
so
now
we
go
to
logs.
You
can
see
that
there
is
the
log
and
then,
as
I
click
and
this
browser
window
over
here,
you
can
see
the
the
entries
come
into
the
the
log
panel.
B
D
B
D
D
I
times,
thumb
is
important
if
you
want
to
correlate
things
an
impact
on
time,
but
for
most
people
they,
they
basically,
for
example,
think
about
how
you
draw
something
right:
you're
gonna,
look
at
lines.
Fifty
to
fifty
fifty
one
highlight
them.
Let
me
copy
them
in
another
thing
and
then
go
to
lines
a
hundred
to
two
hundred
and
say:
okay,
or
this
is
how
it
happened
later
on,
and
you
put
them
next
to
each
other.
B
B
We
kind
of
have
the
the
freeze
already
and
we
get
for
free
just
based
on
the
viewer
we're
using,
but
the
ability
to
now
resume
so
like
a
good
example
be
like
you're
using
this
filter
here
and
you
want
to
know,
go
like
oh
I
found
what
I
was
looking
for.
There's
things
happening
and
I
want
to
just
resume.
Then
I
would
click
something
in
there.
So
yeah
we
can
add.
We
can
add
a
issue
for
forgetting
those
couple
features
in
there
and.
D
Then
one
last
thing
and
take
this
with
a
grain
of
salt
I
haven't
been
a
developer
for
like
16
years
now,
but
when
I
was
one
of
the
biggest
things
that
you
could
have
something
like
this,
in
addition
to
filters,
also
have
an
option
for
highlighting.
So
someone
could
give
you
four
or
five
terms
that
you
want
to
highlight,
but
you
don't
want
to
filter
based
on
those.
D
B
D
But
yeah,
but
instead
what
I'm
talking
about
is
allow
them
to
filter
on
something
and
only
show
the
filter,
but
then
highlight
the
few
things
are
important
to
them.
So,
for
example,
if
you're
following
I'll
give
you
an
example,
if
you're
following
a
transaction
ID
and
someone
that
wrote
a
multi,
a
multi
pod
service
that
has
transaction
IDs
or
some
some
form
of
identity
that
crosses
application,
boundaries
or
pod
boundaries,
then
they
might
want
to
highlight
that.
But
that's
not
what
they
want
to
filter
on.