►
From YouTube: Octant Community Meeting - Feb 12, 2020
Description
February 12, 2020
Agenda
-------
Introducing Milan!
Plugin updates.
service.Request is now an interface #645
Get no longer returns a found bool #643
DashboardClient Create and Delete coming
Unmarshal all the things #646
Actions example plugin
Logging updates. #660
Angular9 back in progress. #665
YAML viewer (Monaco) updates soon unblocked.
allows us to lazy load components :+1:
we hope, we think, probably
Open Q&A - add your questions here!
-------------------------------------
More example plugins? Best practices, patterns?
Yes, we want to have a set of example plugins.
We want to provide narrative documentation around plugins.
We want to have best practices around plugins and create some common conventions.
When will the Octant plugin page be up?
Soon™
A
A
B
Sure,
hello,
everybody
I
just
started
this
week.
My
name
is
Milan.
I
spend
lots
two
big
last
three
years
in
pivotal
working
on
that
data,
visualization
library,
so
this
I
think
fits
really
well
with
mine.
Just
I'm
excited
to
be
on
a
team
and
looking
forward
to
work
with
you
more
I
already
started
looking
into
some
of
the
work
or
the
weighted
issues,
but
yeah
I'm
still
at
learning
it
codebase.
C
Yeah,
so
we
this
last
week,
we've
been
spending
a
lot
of
time
working
on
making
some
updates
to
plugins
one
of
the
first
things
we
did
was
he
addressed
this
outstanding
issue
where
the
service
request
was
a
concrete
struct
that
was
being
passed
around
and
had
some
mast,
private
properties
and
a
mix
of
public
properties
and
public
methods,
and
so
we've
converted
that
into
an
interface.
This
allows
for
better
unit
testing,
as
you
can
just
supply
a
mock
or
a
fake
for
the
service
request
into
your
handlers.
C
Now
and
it'll
continue
to
be
the
place
where
we
are
able
to
make
API
changes,
as
well
as
version
and
pin
things
on
the
requests,
so
that
is
currently
in
master
and
will
be
part
of
the
next
release.
That
is
a
breaking
API
change
for
plugins.
The
path
property
which
you
used
to
access
directly
is
now
accessed
through
a
path
method.
It
still
functions
in
the
same
way,
but
that
that
is
now
a
method
instead
of
a
property.
C
C
It
was
something
that
where
it
would
return
that
it
was
not
found,
even
though
it
was
found,
and
then
it
would
result
in
an
error
and
then
the
result
of
that
was
that
things
would
not
get
properly
rendered
or
Marsh
are
sent
out
to
the
front
end,
because
there
would.
It
would
be
interpret
this
as
an
error
instead
of
just
a
empty
response.
So
Sam
fix
that
up,
and
that
is
another
breaking
API
change.
If
you're
using
the
get
method
off
of
the
dashboard
client
it
it
returns.
C
Two
values
now,
which
is
the
object
you're
trying
to
get
and
in
herre,
and
so
you'll
have
to
you'll,
be
wanting
to
do
nil,
check
on
the
the
object
and
no
longer
use.
This
found
value
which
was
found
found
was
found
to
be
error
errant.
Sometimes
anyway,
it
came
out
weird
the
next
when
I
finished,
these
plug-in
updates
I'll
take
questions
specifically
about
plugins,
but
I'm
gonna
go
through
the
list.
The
next
thing
we're
gonna
be
addressing
is
that
the
dashboard
client
currently
does
not
have
create
or
delete
a
lot
of
plug-in.
C
Authors
are
wanting
this
behavior
and
the
ability
to
have
their
plugins,
especially
things
around
custom
plugins
around
custom
resources,
be
able
to
create
and
delete
those
custom
resources.
So
that's
something
we're
gonna
be
adding
to
the
dashboard
client
interface
for
plugins.
There's
an
issue
created,
I,
didn't
link
it
because
I
forget
which
one
it
is
the
next
thing
we've
been
working
on
is
the
unmarshal
all
the
things
ticket
Sam
created
this
issue
as
a
tracking
issue.
C
This
ties
into
a
lot
of
the
things
that
people
have
mentioned,
where
they're
trying
to
use
button
or
button
group,
or
they
want
to
use
a
embed,
a
form
or
they
want
N
and
those
things
aren't
rendering
like
that.
There's
no
errors.
Everything
looks
fine,
but
they're
not
rendering
when
they
go
to
view
the
content
response
for
their
plugin,
and
the
reason
this
was
happening
is
because
we
have
an
unmarked
go
file
which
actually
maps
all
of
the
types
that
we
support
and
allows
them
to
be
unmarshal
from
JSON
back
into
concrete
objects.
C
Because
of
the
communication
between
plugins
and
octant
is
done
over
G
RPC.
We
have
two.
What
we
do
is
we
take
that
response
from
from
the
plugins
and
we
hydrate
them
and
then
put
them
on
to
the
stream.
So
if
we
can't
unmarshal
those
things
from
the
the
plug-in
data,
then
we
can
actually
send
them
out
over
the
stream.
C
So
Sam
and
I
have
been
working
through
the
list
of
items
deciding
what
is
and
what
isn't
going
to
be
part
of
this
kind
of
refresh
of
the
plugins
and
we're
just
checking
those
off
as
we
go.
I
think
we
have
a
few
more
that
we
have
to
make
some
decisions
on,
but
there
was
a
couple
that
have
already
been
landed
button
and
button
group
was
one
and
Sam
took
care
of
well
see
them,
which
one
did
the
annotation.
D
C
So
you
can
take
a
look
at
that
if
you're
interested
in
getting
actions
custom
actions
into
your
your
plugins,
this
should
give
you
a
good
idea
of
how
its
kind
of
write
those
and
the
conventions
involved
there.
So
that's
it
for
the
the
current
update
on
plugins.
Are
there
any
questions
or
the
things
that
people
want
to
know
more
about.
D
Ok,
there
is
one
component
I
believe
it's
the
I
think
it's
still
the
law
component.
There
was
a
request
from
I
believe
Jason
from
the
tech
dawn
team
he
wanted
to
well.
He
thought
that
the
law
component
currently
requires
too
much
information.
You
need
actually
need
to
know
what
the
containers
are
before
you
actually
create
that
component
and
a
better
way
of
going
forward
might
just
be
to
just
provide
the
name
of
the
pod,
and
it
will
just
automatically
go
through
all
of
the
containers
for
each.
If
we,
you
could
move
forward
with
that.
C
Yeah,
yes,
so,
as
Sam
mentioned,
there
was
an
issue
about
the
setup
for
the
log
component.
That
is
something
that
is
part
of
the
next
update
item,
which
is
the
the
logging
tab.
Improvements,
I
agree
with,
with
with
Jason's
request.
I
think
that
you
do
have
like
the
fact
that
we
have
to
go,
make
a
request
to
get
a
list
of
the
containers
and
then
make
another
request
to
generate
the
component
with
that
list,
even
when
what
you
want
just
by
default
to
have
it
do
all
of
the
containers,
which
makes
a
lot
of
sense.
C
So
that
is
part
of
the
logging
tab,
improvements
that
664
the
logging
updates.
We
created
an
epoch
to
track
kind
of
all
of
the
work
that
that
can
go
into
the
the
logging
tab.
That
Milan
is
going
to
be
looking
at
and
working
through,
there's
quite
a
few
things
that
have
come
up
as
we
started
to
look
into
the
logging
tab
being
able
to
have
all
the
logs
be
viewed
at
once
defaulting
it
so
that
all
of
the
containers
are
are
populated.
C
Just
like
we
do
for
the
terminal
being
being
able
to
pause
the
logger,
ensuring
that
the
logger
is
scrolled
down
to
the
bottom
on
the
initial
load,
where
you
might
already
have
some
data
that
has
been
put
into
the
stream
and
then
also
being
able
to
view
multiple
logs
at
the
same
time,
so
I
think
someone
called
it
log
aggregation,
I'll,
probably
rename
the
ticket,
because
we're
we're
not
actually
going
to
physically
do
anything.
We're
really
just
gonna
display
them
at
the
same
time
and
and
that'll
kind
of
be
one
of
those.
C
You
know,
they'll
have
a
tag.
They'll
have
a
timestamp,
they'll
and
they'll
say
what
containers
were
coming
from
and
then
you'll
be
able
to
use
the
filter
to
kind
of
further
reduce
it
down,
but
that
all
just
be
a
visual
thing
in
warnet.
We
want
to
actually
be
doing
any
type
of
coalescing
of
logs,
so
so
yeah
there's
a
whole
update
coming
for
for
logging,
and
it
should
make
things
a
lot
better
with
respect
to
you,
making
it
usable
and
functional
for
people.
One
of
the
other
things
I
wanted
to
call
out
is.
C
There
was
an
issue
open
specifically
about
virtual
nodes,
running
on
aks,
the
your
kubernetes
service
and
I'm.
Looking
at
that
right
now
and
have
been
named,
I
don't
have
access
to
a
jury
yet
I'm
working
on
that,
but
I
have
been
able
to
kind
of
walk
through
the
code
and
I
think
I
know
why
it's
happening
so
that
was
issue
649.
It
looked
like
it
was
directly
impacting
somebody
so
that
that'll
be
resolved
fairly
soon
as
well.
Some.
A
C
Yeah,
so
the
you
know
works
for
me,
so
those
I
think
your
Zen
hub
might
just
be
distinct,
but
I
will
make
a
comment
in
the
issue
that
that
it
is
an
epic
being
tracked
by
Zen
hub
and
for
the
best
viewing
experience
will
want
to
you'll
want
to
have
either
a
view
it
on
Zen.
But
where
have
the
plug-in
installed
in
their
browser
sounds
good
and
yeah
I.
Don't
know
why
I'm
not
logged
in
here
but
yeah
that
make
sense.
C
Thank
you
and
since
we're
on
that
real
quickly,
I
have
a
PR
up.
That
kind
of
that.
That
outlines
the
details
of
how
our
Zen
hub
lanes
work
and
also
points
people
to
the
the
browser
extension
in
that
as
part
of
the
contributing
markdown.
That's
in
the
repo.
So
once
that
lands
people
will
be
able
to
have
a
better
just
understanding
of
the
tooling
we're
using
to
kind
of
track
the
project
and
get
work
done
so
that.
C
So
the
angular
yeah,
the
the
last
item
on
the
agenda,
is
the
angular
9
is
back
in
progress,
so
there's
actually
open
PR
for
for
the
angular
9
upgrade
for
those
who
aren't
familiar
that
angular
moving
angular
9
is
part
of
being
able
it's
a
long
dependency
chain
of.
We
want
to
use
the
Monaco
editor,
which
is
what
V
s
code
uses,
and
we
want
to
use
that
in
our
for
our
llamo
viewer,
as
well
as
some
other
parts
of
the
octants
eventually,
and
so
the
latest
version
of
that
uses.
C
Typescript
375,
angular
8,
which
is
what
we
were
currently
on,
does
not
support
that
version
of
typescript.
There's
a
there's,
a
bunch
of
differences,
so
we
were
up.
We
went
down
the
track
of
upgrading
to
angular
9.
We
ran
into
some
issues
with
the
clarity
libraries
that
we
use.
They
recently
have
released
an
update
for
clarity,
3,
which
is
supports
angular
9.
C
So
you
get
the
latest
thing
so
we're
we're
using
that
convention
to
do
this
upgrade,
but
all
of
the
data
transformations
and
all
of
the
small
minor
things
that
need
to
happen
so
that
we
can
be
ready
for
when
angular
9
does
their
official
release
are
part
of
this
665
issue,
and
once
this
issue
is
merged,
we'll
be
able
to
then
continue
to
move
forward
on
the
Monaco
integration.
So
this
is
really
great
news.
C
It's
gonna
get
us
unblocked
on
the
the
Yam
of
your
updates
and
and
further
content
once
that
yamo
viewer
update
is
in
place
that
will
get
us
rolling
on
starting
to
get
the
the
context-aware
editing
in
place
into
octant
and
some
of
those
more
advanced
features
that
were
that
we're
hoping
to
roll
out.
So
this
is
all
really
great
news,
so
I've
been
testing
and
running
the
angular
and
I'm
branch
all
day
and
so
far
so
good.
C
A
E
Have
one
question
this
is
John
from
Fiamma
I've
been
playing
with
up
to
the
little
bit
recently
actually
I've
been
trying
to
devise
a
harbor
plugin,
and
my
question
was
kind
of
more
broadly
around
your
example.
Are
our
actions
really
awesome
when
and
I
wondered
like?
Is
there
any
plan
as
hub
as
often
functionality
increases,
to
add
to
the
example
plug-in
or
to
provide
multiple
example
plugins
to
keep
those
in
the
core
repo,
or
even
like
an
example
of
design
patterns
for
plugins,
so,
for
instance,
in
harbor?
C
I
can
I
can
take
this
and
then
Sam
can
add
to
it.
So,
yes,
we,
we
have
a
strong
desire
to
create
first
off,
better
kind
of
narrative,
documentation
around
plugins,
so
concrete
examples
of
how
you
might
approach
certain
situations
and
how
you
will
how
we
feel
would
be
the
best
way
to
handle,
just
like
the
things
you've
described
in
a
plugin
client
like
external
client,
access
and
shared
clients
and
things
like
that
loading
data
like
persisting
data
and
loading
it
knocked
it
restarts,
which
is
something
that
has
come
up
around
plugins
so
there.
C
C
So
someone
could
then
check
out
the
octan
plugins
example
repository
and
would
have
a
host
of
examples
like
a
standalone
plug-in,
a
plug-in
that
extends
pods,
a
plug-in
that
wraps
the
CRD
and
does
custom
actions
a
plug-in
that
calls
a
third
party
API
and
does
so
with
a
you
know
back
off,
so
that
it's
not
constantly
spamming
the
the
API
every
second
things
like
that.
All
of
those
are,
we
do
want
to
get
examples,
for
we
have
some
various
issues
created
around
documentation
and
updating,
plug-in
documentation,
and
so
I
know.
C
D
Yes,
so
one
thing
that
we
also
like
that
better
support
for
is
just
better
support
for
testing
unit
testing
components.
So
I
know
the
story,
isn't
currently
really
great
right
now
and
I
think
making
that
request
interface,
turning
it
yeah,
making
that
request,
interface
public
is
going
and
exposing
stuff
like
pads
and
making
that
a
lot
more
testable
is
going
to
provide
a
long
way
for
just
making
plugins
a
bit
more
stable
and
exposing
an
API
changes
that
we
need
to
make
sooner
than
later.
D
E
Cool
Thanks,
I
I'm,
definitely
down
for
helping
with
documentation
or
like
developing
design
patterns,
and
things
like
that.
I'm
contributing
I
just
saw
a
couple
of
comments
from
Brian
around
like
completely
rejigging
the
whole
plug-in
model
and
doing
changes
so
I
was
wondering
like
is
that
still
happening?
Is
it
worth
doing
a
whole
bunch
of
effort
into
my
documentation
here?
If
things
are
going
to
change,
or
are
we
like
far
enough
out
that
the
effort
is
gonna
be
worth
it?
Yeah.
C
So
around
those
so
the
the
comments,
those
changes
are
happening
so
and
that's
part
of
the
this.
This
plug-in
update
that
we're
doing
now
where
we
are,
where
we're
breaking
some
of
the
api's,
and
we
are
really
digging
into
identifying
the
needs
of
plugin
authors
and
trying
to
create
that
balance
between
what
octants
wants
to
be
responsible
for
and
what
we're
gonna
make
plug-in
authors
responsible
for
and
so
yeah.
C
This
is
all
coming
together
right
now,
and
so,
as
you
are
developing
your
plugins
and
all
everyone
who
who
is
developing
plugins
is
you're
working
on
things.
If
you're
running
up
against
issues
or
you're
you're
you're,
finding
a
pattern
that
you're
commonly
using
yeah
I
would
say
you
know,
share
it
with
us,
create
an
issue,
bring
it
up
at
the
community
meeting.
However,
whatever
your
preferred
method
create
a
repo
with
the
example
and
then
send
that,
in
whatever
your
preferred
example
is
for
for
communicating
those
thoughts
and
ideas.
F
C
It's
it's
there's
a
there's,
an
issue
that
has
kind
of
a
long
tail.
It
might
be
a
good
idea
to
create
a
new
one
from
it,
but
Sam
left
a
comment
that
we
want
to
extract.
The
existing
example
plug-in
out
to
its
own
repo,
which
was
part
of
a
larger,
which
was
actually
part
of
the
645
issue,
and
then
we
have
multiple
issues
around
plug-in,
documentation
and
auto-generating,
some
documentation
around
plug-in
components
and
things
like
that.
So
it
the
work
is
all
captured.
C
F
G
Things
that
it's
now
that
have
mulana
on
the
team
looking
at
this
through
afresh
the
device,
maybe
Milan,
can
help
work
on
some
of
the
plugins
and
and
coming
from
a
new
person's
perspective.
Gonna
probably
identify
a
lot
more
things
that
make
sense
to
some
of
the
working
on
the
project
for
a
while.
So
maybe
that's
a
good
opportunity
for
us
to
improve
documentation
and
how-to
guides.
Yeah.
F
C
Also
say
that
most
of
our
stuff
for
plugins
is
driven
by
the
community
members
who
aren't
working
on
octave
day-to-day.
So
we'd,
like
the
perspective
on
plugins,
is
generally
already
coming
from
a
point
of
view.
That
is
not
someone
who's
in
the
trenches
working
on
octave
daily,
which
is
why
it's
shaping
up
so
well.