►
From YouTube: Octant Community Meeting - Jan 29, 2020
Description
January 29, 2020
Agenda
0.10 released
bug fixes coming in 0.10.1
Electron prototyping
Angular9
Monaco
octant-vulnerabilities-plugin by Daniel Pacak from Aqua Security
Open Q&A - add your questions here!
(dpacak) What’s the status of adding buttons / action handlers in custom plugins?
Soon, https://github.com/vmware-tanzu/octant/issues/421
A
A
B
There
was
blog
post
for
the
release,
its
cow
words
and
but
yeah.
So
the
the
release
came
out.
We,
as
mentioned
previously
in
the
last
community
meeting.
We
were
the
main
big
things
were:
adding
the
container
exec
and
the
workload
viewer,
and
then,
alongside
of
that,
was
a
bunch
of
other
quality-of-life
fixes
that
were
in
there
all
that's
up
in
the
release,
notes
which
are
available
in
linked
from
the
blog
post
there,
hip
and
so
yeah.
B
We
have
some
bugs
that
shook
out
of
that
that
we
are
addressing
now
well
most
from
already
addressed,
but
the
the
main
ones
are
we're
going
to
be.
What
were
they?
Let's
see,
I
gotta,
I
gotta
take
a
look
at
what's
in
our
our
changelogs
folder
here,
oh
yeah,
so
we
are
fixing
some
failures
around
pod
metrics
for
the
workload
viewer.
We
there
was
some
community
member
who
fixed
some
typos.
We
had
in
the
build
scripts
around
go
module.
B
We
removed
the
duplicate
pod
log
that
shows
up
when
you're
viewing
pod
logs.
We
fixed
a
CRD
washer
race
condition,
also
fixed
the
workload
navigation
path
when
you're
running
octave
on
Windows,
and
we
fixed
some
access
error,
type
assertions
for
the
CRT
watcher
the
and
we're
also
going
to
be
doing
a
fix
for
some
of
the
access
denied
and
unauthorized
access,
API
spam
that
happens,
and
you
have
credentials
and
then
they
go
away
while
octant
is
still
running.
B
C
Kubernetes
api
is
not
made
free
for
these
types
of
we're
actually
using
the
kubernetes
api
in
a
way
that
it
was
never
imagined
to
meet
and
a
lot
of
besides
control.
So
controllers
are
easy.
The
controller
says
I'm
gonna
start
up,
it
gets
a
set
of
credentials
and
it
doesn't
stay.
Cheap
control
is
easy.
It's
usually
just
a
short
request.
So
when
currents
was
changed,
you
want
to
worry
about
it,
because
the
requests
when
they
was
so
short
that
it
doesn't
matter
and
by
the
time
they've
changed,
you
can
get
new
ones.
C
Auxin
is
long
term
and
because
the
way
we
used
informers,
it
is
very
difficult
to
actually
do
this.
So
Wayne
has
a
fix
at
a
low
level
fix
that
is
that
he's
working
on
right
now
that
actually
goes
through
and
we're
going
to
basically
use
a
leveling
to
say:
oh
wow
you're
getting
way
too
many
off
air.
Maybe
we
should
do
something
about
this
and
then
at
the
high
level,
actually
I
have
a
PR
open
that
will
once
we
get
the
the
test
worked
out,
that
it
actually
looks
at
it
in
a
totally
different
way.
C
So
that's
coming
as
well,
so
I'll
give
you
a
little
backstory
on
this.
When
we,
when
we
created
octant
yeah,
it
was
a
good
idea.
Let's
put
this
in
a
webpage,
but
the
problem
with
web
pages
is
that
there's
there's
two
major
projects
with
web
pages.
One
is
that
people
see
a
web
page.
They
assume
that
simple
web
service
behind
it
and
if
it's
a
simple
web
service
behind
it,
oh
we
can
just
throw
this
in
a
cluster.
You
do
not
want
to
run
opt-in
in
a
cluster.
C
We
have
to
create
a
new
informer
for
every
single
API
resource
for
every
single
namespace
that
you
touch
and
normally
you
know
that
can
be
kind
of
small.
But
if
you
have
a
large
amount
of
namespaces
or
something
like
that,
they
can
get
very
big,
very
quick.
So
we
really
don't
like
we
don't
like
the
idea
of
running
auxin
in
a
cluster
I.
C
Think
there's
something
we
can
do
to
get
it
running
in
a
cluster,
but
it
would
not
be
the
option
project
itself,
so
we
want
to
move
it
closer
to
an
application
and
and
there's
other
reasons
behind
its
on
your
Mac
and
on
Linux
in
on
Windows.
You
have
this
depending
on
your
window
manager
and
and
in
Linux
you
have
access
to
a
status
bar.
We
would
like
to
take
advantage
of
that.
You
should
we
want
auxin
to
be
running
all
the
time,
but
you
know
seeing
the
seeing
the
dashboard
is.
It's
not
super
useful.
C
All
the
time
we
can
show
a
much
shorter
status
and
we
can
show
you
we
can
actually
just
use
a
notification
facility
in
your
operating
system
to
tell
you
these
things
can't
do
that
from
a
web
browser.
We
actually
have
to
take
this
out
of
web
browser
and
there
are
some
some
assumptions
that
we
are
making
right
now
that
make
octant
hard
right
that
it's
in
a
web
browser.
If
we
moved
it
to
an
application,
we
can
actually
say
you
know
what
we
can.
We,
we
don't
have
to
assume
anymore.
C
We
know
exactly
what
this
thing
is
doing
and
we
can
now
put
it
in
an
application
and
we're
right
now.
I
looked
at
I
looked
at
webview
and
this
this
go
thing
called
l'autre
and
they're
great
solutions.
If
he
want
something
super
simple
that
doesn't
have
menu
bars.
So
now
we're
looking
at
electronic
and
with
with
electron
and
an
octant
yeah
it's
gonna
and
you
need
the
the
sizes
you're
downloading
a
Chrome
browser.
C
C
Well,
we
lose
a
back
button,
so
we're
going
to
redesign
parts
of
octant
to
make
it
fit
better
and
an
application
that
assumes
that
it
has
one
main
window
and
that's
it
so
that
that
work
will
be
ongoing.
There
there's
going
to
be
some
preview
work
that
will
hit
master
over
the
next,
hopefully
by
the
end
of
this
week,
but
it
will
will
probably
boot
it
from
a
new
binary,
so
you
won't
ever
see
it,
but
we're
definitely
going
to
be
starting
that
right
now.
A
C
General
no
I
think
that's
a
I.
Think
it's
fun
in
general,
I
mean
all
right,
obvious,
come
on,
say
it
people
hate
electron
apps
because
of
what
slap
does
and
if
you
look
at
slack
and
what
they're
trying
to
do,
that
is
one
implementation
of
electron.
But
take
another
slack
app
you
don't
our
electron
app.
You
don't
think
about
use
vs
code,
that's
electron,
and
is
it
as
fast
as
I
made
it
matter
here?
C
Well,
if
you
get
down
to
and
you
want
to
count
millisecond,
it's
probably
not,
but
for
usability,
yes,
pretty
good
and
and
that's
what
we're
looking
at
and
there's
I
mean,
there's
work
that
we
need
to
do
to
get
there.
One
thing
that
we
do
right
now
is
we're
an
angular
app
and
we
don't.
We
always
assume
to
be
local,
so
we
cheated,
but
there's
things
that
we
can
do
to
make
our
apps
loads
quicker
and
there's
things
that
we
can
do
well.
C
We
don't
have
to
make
assumptions
about
latency
or
anything
like
that
to
actually
make
it
more
performant.
So
hopefully
we
don't
fall
into
that
trap,
but
we
expect
our
users
to
tell
us
if
we
are,
and
we
and
I
actually
and
probably
one
of
the
heaviest
users
of
auxin
ever
I
mean
I.
Have
it
up
right
now,
I
have
always
up.
If
it
bothers
me,
we'll
definitely
get
it
fixed.
B
So
the
next
item
is
angular
9,
so
the
this
came
up
when
we
were
looking
at
adding
a
Monaco
integration
Monaco
for
people
who
don't
know
is
just
a
it's
an
open-source
kind
of
IDE,
that's
that
is
written
in
JavaScript,
typescript,
specifically
and
and
we're
currently
running
on
angular
8
and
the
latest
version
of
monic
and
angular
8
is
using
a
type
script
version
of
less
than
3.6
and
greater
than
3.4
greater
than
equal
to
three
point.
Four
and
the
current
version
of
Monaco
requires
a
tech.
B
So
for
those
who
do
yeah
so
for
those
who
don't
know
the
reason
we're
adding
so
the
there's,
some
issues
that
you
can
find
on
the
on
the
github
repo,
they
are
about
getting
a
code
and
editor
into
octant
and
the
reason
why
we're
doing
this
is
so
that
we
can
start
to
you
think
the
first
step
is
gonna,
be
to
put
Monaco
and
read-only
to
replace
the
existing
Y,
AMOLED,
etre
or
llamó
viewer
that
you
see
now
from
there.
Once
we
have
Monaco
in
place.
B
We
can
then
start
to
think
about
how
we
want
to
and
and
and
what
we
want
to
provide
as
editing
capabilities
with
an
octant,
and
this
includes
things
like
smart
editing.
So
as
your
imagine
as
you're
typing
out
some
edits
to
a
yamo
file
and
you
provide
say
a
secret
or
a
config,
if
that's
not
available,
if
that's
not
present
or
you
don't
have
access
to
it,
the
editor
can
highlight
it
in
red
in
real-time
and
tell
you
like
that
incorrect
name
and
then
to
go
even
further.
B
Potentially,
if
you
do
have
access
to
everything,
we
could
be
pulling
a
list
and
then
we
could
say:
hey
did
you,
you
have
a
typo.
Obviously,
do
you
mean
this
one
or
we
can
do
type-ahead
and
kind
of
smart
editing
facilities
around
ya
know
anything
so
that
is.
That
is
the
reason
we
are
we're.
Getting
the
Monaco
text
editor
in
place.
C
This
all
comes
from
there's
one
feature
that
I
hate
for
every
piece
of
software
that
supports
kubernetes,
where,
if
you
create
a
CRD
and
you're
typing
your
CRD,
no
piece
of
software
knows
where
it
is
goal
and
does
the
closest
by
or
the
kubernetes
for,
IntelliJ,
that's
the
closest.
By
saying
you
can
specify
what
CRT
shoot
you
have,
and
then
we
can
try
to
guess
that
what
we'll
do
inside
of
option
is
something
different.
No
one's
doing
is
that
well
actually
just
go.
C
C
This
tool
will
definitely
open
up
a
new
space
for
us
and
it
also
possesses
us
to
do
something
that
people
have
been
asking
about
for
a
long
time.
Why
can't
I
create
objects
with
octant?
Well,
because
we
didn't
have
a
good
interface
for
it
and
now
with
an
editor
and
then
the
ability
to
upload
Hamill
from
local.
We
will
definitely
have
that.
So
now
you'll
be
able
to
to
create
it
in
the
browser
or
in
the
application.
D
Yeah,
so
thanks
Michael,
letting
me
know
that
there
is
a
community
meeting.
Actually,
the
thread
started
with
a
direct
message
and
I
shared
with
my
collab.
Well,
when
I
saw
octant
I
also
pick
it
picked
it
up
as
a
developer
tool.
Development
tool,
I
started
using
it
but,
as
you
might
realize,
I
am
from
the
security
company
uncle
security
and
we
are
like
a
prototyping
or
trying
to
make
the
security
visibility
and
awareness
even
closer
to
the
developers.
D
So
that's
why
I
would
like
to
share
with
you
today
the
plug-in
that
we
prototype
it's
a
very
early
stage,
but
you
might
find
it
interesting
and
I
would
like
to
take
this
opportunity
to
ask
some
questions.
What
are
the
capabilities
of
the
current
plug-in
API
what's
possible?
What's
not
because
I
watch
the
previous
meetings
and
I
know
that
documentation
is,
you
know
just
in
the
early
stage,
so
let
me
quickly
share
the
screen
with
a
quick
demo.
D
That's
you
know,
and
before
before
the
demo
I
put
together
like
a
two
or
three
slides
slides
just
to
give
the
context
why
we
do
that
think
so.
Yeah,
let's
move
to
the
to
the
first
slide,
so
you've
probably
heard
about
the
shift
left
approaching.
Devops
people
started
using
term
deficit
coughs.
So
you
know
very
early
at
the
software
development
lifecycle.
We
would
like
to
test
software
catch
defects,
not
wait
for
this
long.
D
You
know
deployment
testing
and
assembly
what
to
do
with
the
security,
but
it's
it's
challenging
right,
because
developers
are
typically
busy
with
bug
fixes
discovering
new
frameworks,
so
they
have
lots
of
things
on
their
plate,
but
well
at
the
end,
we
want
to
evangelize
we're
going
to
promote
this
kind
of
a
shift
left
up
from
death.
Sick
hopes
all
right.
So
then
I
started
thinking
well,
let's
say:
develop
resistant
keep
CTL.
D
So
at
some
point
he
realize
ok,
I
want
to
see
the
whole
application
what's
happening
here
and
there
and
since
octant
is
wonderful
pool
for
me
and
it's
very
fast,
and
this
plays
like
a
standard,
kubernetes
resources
stay.
It
uses
containers
of
these
playing
pool
abilities
right.
So
by
doing
that,
when
I
see
my
deployment
in
this
screenshot,
you
see
like
a
tomcat
deployment
popular
for
Java
web
apps.
D
You
know
I,
don't
have
to
wait
for
the
built
I,
don't
want
to
fight
for
the
staging
environment.
I
don't
have
to
wait
for
the
security
adviser
to
tell
me
eh.
You
can't
use
this
base
image
because
your
pod,
your
work
workload
is
vulnerable.
All
right.
So
then
I
saw
the
plug-in
system
and
I
said:
ok,
let's
put
together
and
see
how
it
works,
and
so
this
is
what
I
came
up
with.
D
There
are
two
things:
one
is
op
Templar
games.
You
know
it
better
than
me.
What
is
the
open
plug-in
right?
I
can
provide
some
UI
and
I
can
read
some
data
from
see.
Are
they
in
this
case,
so
I
have
defined
the
custom
resource,
which
represents
the
report
of
the
scanner
image
and
the
second
part
of
it
is
a
well.
The
risky
is
the
name
of
a
plug-in,
it's
kind
of
it
and
put
our
name
like
a
code.
Name
I.
D
Don't
know,
however,
I
don't
have
the
real
name,
but
the
idea
is
that
developers
are
familiar
with
cube
CTL.
They
might
be
familiar
with
the
plug-in,
so
let's
develop
the
plugin
that
allows
them
to
scan
quickly.
The
given
workload,
so
let
me
switch
to
the
terminal
and
show
you
how
it
works.
So,
let's
maybe
first
start
with
the
UI,
so
I
developed
a
plug-in
it's
registered
here
and
it
provides
it
currently
only
works
for
pods,
but
it
can
be
easily
extended
to
deployment
and
stateful
sets
and
etc.
So,
with
this
plug-in,
I
want
to
contribute.
D
Okay,
let's
take
the
stone-cutting
of
the
slides
to
be
consistent,
so
I
want
to
contribute,
for
example,
here
with
with
with
a
new
tab
and
let's
say,
I
want
to
contribute
with
some
summary.
I
might
have
some
more
sensible
defaults
like
not
available
or
not
scan
it
yet,
but
you
know
just
to
give
the
idea
was
playing
with
it.
So
let's
say
I
want
to
display
the
number
of
critical
vulnerabilities
in
my
image
and
just
for
fun,
I
added
as
a
separate
car
component.
D
So
how
to
get
this
data
here,
as
I
mentioned,
there
is
a
plug-in.
It's
called
cube,
CTL
risky
for
now,
I
could
initialize
it,
which
simply
creates
a
CRD
I
could
clean
up
the
data,
so
I'm
less
intrusive
as
possible.
I
don't
want
to
modify
existing
workloads.
I
just
want
to
have
my
own
namespace,
my
own
CRD
and
Link
vulnerability
reports
with
corresponding
workouts
with
the
labels
and
then
I
want
I
want
to
scan
things
all
right.
So,
let's,
let's
get
the
part,
so
let's
count
the
stone-cutting.
D
So
if
I
do
something
like
cuticle
scan
image,
it's
in
the
default
namespace
but
I
could
provide
the
namespace
doesn't
really
matter.
The
output
is
pretty
purpose.
What
is
happening
behind
the
scenes
is
I'm
scheduling,
a
job
which
is
using
our
open
source
vulnerability
scanner,
which
is
called
tricky,
the
one
actually
which
we
also
integrated
with
hard
board.
So
this
one
is
taking
the
pod
listing
containers
and
is
you
know
running
the
job?
D
Does
condom
getting
out
the
JSON
report
and
then
saving
the
report
in
a
C
or
D
takes
a
while,
mainly
the
docket
poll.
Let's
be
bare
with
me
for
a
second
and
that's
the
thing:
I
love,
it's
Auto,
refreshing
immediately.
I
can
see
the
scan
results
here,
even
if
I
don't
implement
it
that
the
plug-in
it's
pretty
useful
for
the
command-line
freaks
right
because
they
can
say.
Okay,
I
get,
and
I
sr,
which
is
a
short
name
for
image,
scan
report.
D
D
We
could
I
played
a
bit.
We
could
scan
container
images
which
referred
to
private
registries.
We
could
also
scan
a
were
closed
or
false,
with
two
containers.
I
didn't
pay,
much
attention
to
user
experience.
I
just
wanted
to
get
the
data
and
see
if,
if
it
works
and
how
fast
is
it
in
terms
of
rendering
and
in
terms
of
scanning,
so
that
means
count
quickly.
One
more
this
one
with
is
with
with
two
container,
as
you
can
see,
I'm
spawning
at
scheduling
to
talk
about
at
these
jobs.
One
is
scanning
image.
D
Another
is
scanning
and
drinks
image.
This
kind
of
work
probably
doesn't
make
sense,
but
for
demonstration
purposes
and
we
go
here-
you
see
that
there
are
jobs
and
corresponding
ports
running
and
at
the
end,
if
you
go
here,
you
will
see
there's
one
image
and
another
one
right
so
yeah,
that's
basically
it
what
I
have
when
it
comes
to
demo.
If
you
have
any
questions,
we
can
stop
here.
If
not
I
have
a
couple
of
questions
in
regards
to
extending
a
little
bit
what
we
have
now.
E
D
Yes,
there
are
no
questions
for
the
for
the
plug-in.
I
have
a
bunch
of
questions.
For
example,
you
know
we
also
talk
further,
give
them
water
out.
There
might
be
one
one
too
many
containers
and
so
far
I
came
up
with
vulnerability
stab,
but
I
was
wondering
whether
it's
possible
to
extend
and
contribute
some
UI
components
at
the
container
level.
So
far,
I
saw
that
you
can
contribute
to
configuration
and
the
status
by
not
you
I
cannot
contribute
to
the
container
or
this
I
couldn't
find
this
kind
of
information.
D
So
that's
one
question
and
another
thing
is
I
was
wondering
if,
in
such
a
custom,
tagging
I
can
contribute
to
like
a
patterns
and
action
handlers,
for
example,
to
rescan
or
maybe
acknowledge
or
accept
some
of
the
vulnerabilities.
Let's
say
this
is
a
false,
positive,
all
right
and
I.
Just
you
know
in
order
to
see
what's
possible
in
opt,
and
that's
that
those
are
two
things
that
I'm
wondering
if
it's
possible
to
do
or
not,
I
can
answer.
C
D
D
What's
the
total
number
of
critical
vulnerabilities
so
now
I
display
the
summary
for
the
whole
pod
summing
both
but
let's
say
I
want
to
display
the
summary
group
by
the
the
container
so
display
something
similar
right
here,
and
so
this
is
this
one
of
the
news
cases
so
I
would
like
to,
for
example,
if
someone
is
reviewing
the
spec
of
this
pod
instead
of
going
here,
because
I
don't
really
know
why
this
you
know
from
which
content
it
comes
from
until
I
go
there
and
see
all
right.
This
is
from
engines
right.
D
C
What
you
would
need
to
do,
that
is,
you
would
need
access
to
the
container
itself
or
anything
inside
of
here
and
I'm,
not
saying
I,
don't
know
when
we
would
do
this,
but
to
solve
this
problem.
One
thing
we
could
do
is
we
could
generate
that.
We
could
generate
this
screen
before
we
call
the
plugins.
We
could
actually
send
this.
C
We
could
actually
send
this
to
with
the
plug-in
so
that
the
plug-in
could
actually
augment
any
output
that
was
generated,
so
you
could
actually
overlay
your
content,
which
means
you
could
actually
throw
another
item
in
the
in
the
summary
that
we're
using
inside
of
the
container
so
that
that's
one
way
that
we
could
solve
that
and
for
the
other
one.
So
if
you
wanted
to
but
a
delete
button
at
the
top
right,
we
just
don't
expose
that
right.
C
B
D
Right
so
yeah
yeah
I
got
it.
So
this
means
that
the
status
card
is
somehow
treated
differently
like
you
render
it
and
then
the
plug-in
can
append
the
status
items,
whereas
the
container
yeah,
the
our
actions
are
rendered
dynamically.
So
they
have
a
bit
different
life
cycle
and
that's
why
in
the
API
I
could
contribute
to
configuration
and
status.
It
was
not
possible
right
now
for
the
containers.
This
is
my
god
that.
C
Was
because
I
was
trying
to
be
pragmatic,
we
know
that
configuration
and
status
would
exist.
We
don't
know
the
container
will
exist,
because
if
you
just
want
a
deployment,
there
is
no
container,
but
there
will
still
be
configuration
States.
So
like
I
was
saying
before.
If
we
passed,
if,
if
we
made
it
so
that
you
could
augment,
but
you
could
actually
extend
something
that
we
sent.
Maybe
that's,
maybe
that's
the
possibility.
We'd
have
to
see
how
that
would
work.
We
are
going
to
actually
take
a
look
at
the
plug-in
API.
C
The
story
Darla
could
tell
is
that
I
literally
wrote
this
one,
a
Sunday
one,
it
goes
like.
Will
this
be
cool
and
I
wrote
it
and
I
put
it
in
there
and
I'm
like
well,
it's
useful,
and
so
we
we
have
not
put
as
much.
We
need
more
examples
to
figure
out
how
it
should
be
used,
and
then
we
figure
out
how
we
use.
Then
the
API
will
be
start
actually
gelling
and
become
a
lot
better
than
it
is
right.
Now,
yeah.
D
Because
yeah
I
think
I
have
those
are
not
very
crazy
requirements
but,
like
you
know,
extending
it
so
I
could
have
a
like
a
interaction
with
a
because
currently
the
cube,
City
risky
plug-in
is
pushing
data,
but
some
of
the
data,
like
a
pulling,
might
be
triggered
through
the
action
scene
that
you
write.
So
that's
why
I
found
this
use
case
important
and
as
I
said.
I
would
also
like
to
do
something
with
a
particular
row
item
in
the
in
the
tables:
components.
Alright.
D
D
One
day,
let's
say
I'm
crazy
and
it's
I
don't
know
how
to
do
that.
But
let's
say
I
want
to
auto
fix
this
right.
Let's
say
I
can
scan
the
image
because
I
know
we're
from
witch
doctor
image.
It
comes
from.
I
can
somehow
see
the
history
of
a
docker
image
and
I
see
that
it's
installed
with
some
package
manager
right
and
I
know
that
it's
fixed
in
some
version.
Some
of
those
are
fixed
and,
let's
say
I
want
to
provide
to
the
users
the
auto
fix
feature.
D
D
C
That's
a
feature
that
we
could
use
as
well.
Yeah,
we
don't
the
whole
grid
component.
Is
it's
pretty
basic?
It
can
display,
you
know
integrate.
You
can
display
any
other
come
well.
You
can
display
most
other
components
that
we
can,
that
we
can.
We
can
nest
them
inside
of
there.
That's,
oh,
but
we
don't
actually
have
a.
We
have
a
plan
component
leave
a
button
group,
so
we
can
do
some
things
in
there
to
make
that
better,
but
spell
out
your
use
cases
an
issue
I
would
love
to
read
them.
D
C
Wanted
to
bring
that
that
this
time
slot
is
amazingly
crazy
for
me.
I
had
to
make
someone
else
unhappy
to
be
here
today
and
I
make
the
I
will
try
to
make
the
promise
that
every
other
week
I
will
make
someone
else
unhappy.
So
I
can
be
here,
because
this
is
super
important,
but
I'm
so
glad
that
I
could
be
here
for
a
few
minutes
and
actually
I
have
to
run
because
life,
but
I
I,
love
that
Wayne
and
Sam
are
putting
in
all
the
work.
C
D
C
What
we'll
do
is
look
like
a
pass.
It's
trying
to
understand,
because
everything
you
told
me
about
doesn't
actually
sound.
Like
oh
they'll,
be
super
hard.
It
would
actually
not
be
very
hard
and
whenever
we
get
to
some
level
success,
we'll
make
some
noise
about
it
too,
because
I
agree.
We
don't
want
to
be
experts
at
everything
we
want
to
make
a
platform,
so
people
can
actually
create
tools
like
security
tools.
So
when
we
get
this
to
a
point,
we'll
definitely
make
some
noise
about
it
to
you
to
get
you
awesome.