►
From YouTube: Secrets Management Sync
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
All
righty
I
want
to
start
talking
about
the
runner
stuff
and
how
that's
going
if
you've
heard
anything
as
far
as
progress
goes,
I
just
feel
like
it's
a
black
hole.
I
haven't
heard
anything
on
it.
B
Yeah,
but
that's
that's
basically
what
we
need
now,
because
we
still
have
work
to
do,
but
we
have
what
we
need
at
that
stage
and
even
if
we
keep
doing
the
other
work,
that
makes
no
sense
without
the
runner
itself.
So
we
should
know
where
we
are
with
the
runners.
So
do
we
need?
Can
we
help
in
some
way
or
we
are
basically
any.
A
B
A
Okay,
that
works.
Let
me
I
was
just
chatting
darren
to
see
like
where
would
be
the
best
channel
to
post
on
this.
B
Yeah
it's!
It
should
be
one
of
the
channels,
it's
more
general,
but.
A
Okay,
all
right,
I
will
I'll
ping
that
right
now
and
then
we'll
go
from
there
second
thing.
Thank
you
so
much
for
creating
those
issues
and
updating
them,
I'm
going
to
add
them
to
my
direction
page,
and
I'm
really
excited
about
that
part.
A
The
one
for
the
april
so
we're
good
with
that.
B
No,
no,
I
just
saw
an
email
anyway.
All
I
found
I
brought
it
to
the
epic
and
I
kind
of
sorted
them
the
way
I
think
we
should
be
working
on
them.
Okay,
but
you
can
like
some
of
them
are
just
you
should
decide
the
priority
because
they
are
additions
and
some
of
them.
We
have
to
do
that
way
because
they're
like
dependent
but.
B
How
I
see
it,
but
it's
not
like
it's
subject
to
change
so
and
we
should
see
when
we
like
it.
I
probably
lift
this
up
to
you,
which
we're
gonna
work
on
and
when
because
we
probably
need
you,
you
want
us,
or
at
least
you
want
me
to
start
looking
at
something
else
too.
So.
A
B
Really
get
like
that
first
part
out
and
see
how
it's
going
so
we
get
any
feedback
but
yeah.
I
think
we
have
a
good
set
of
like
stuff
to
do
right
now
and
unless
some
like
customers,
or
even
more
than
one
customers
pop
up
with
some
requests
that
are
really
important,
we
should
kind
of
stick
to
that.
A
Totally
you're
actually
right
there.
Okay,
that
makes
a
lot
of
sense.
Part
of
my
desire
to
get
all
of
these
issues
created
are
so
we
can
engage
the
community
to
also
build
some
of
the
stuff
for
us
too.
So
if
we
had
a
really
well
specified
scope,
we
can
hopefully
encourage
other
people
to
contribute
so
part
of,
like
my
drive,
to
want
to
create
really
great
forward-looking
scope
is
for
us
to
scale
right.
B
Okay,
so
then
yeah
some
of
these
that
are
just
additions
and
will
follow
the
same
framework.
You
really
can
be
done
by
community
totally.
Maybe
I
should
put
some
more
attention
into
them
and
like
be
more
specific,
like
for
new
syntax,
we
want
it
to
look
like
this,
so
basically
take
this
implement.
So
so
there
is
no
guessing
yeah,
so
I'll
go
again
through
all
of
them
and
see
a
major
thought
or
just
will
flick
a
list
to
you
or
maybe
just
start
accepting
mercy
requests
to
those
that
I
think
can
be
done.
A
Exactly
and
then
I'm
going
to
to
do
a
community
enablement
session,
where
I
talk
about
release
management
and
what
we're
doing
I'll
be
presenting
that
feature
set
like
our
secret
management
direction
as
an
opportunity
to
contribute,
and
then
the
second
one
being
ci
variable
bugs.
So
that
leads
me
to
the
other
issue.
I
have
on
the
agenda.
B
Just
just
to
finish
now,
actually
I
I
realized
that
many
of
these
additions,
even
if
they
look
like
clear
to
me,
will
require
both
rails
and
runner.
Work
like
we
had
now,
so
that
could
be
a
bit
more
tricky
for
our
community,
but
they
can,
at
least
I
don't
know,
work
on
the
rails,
part
which
they
feel
comfortable
in
yeah.
So,
of
course,
we'll
still
need
to
run
our
work,
but
I
think
we
may
look
at
after.
We
have
that
initial
work
delivered
by
the
runner
team
and
we
have
an
example.
B
B
Yeah
because
like
if
we
need
the
next
time,
we
need
them,
they'll
have
to
like
prioritize,
it
put
it
work
and
we
see
it's
not
working
very
well.
So
I
really
hope
once
we
have
like
some
code
from
them,
we
can
just
follow
it
as
an
example
and
do
it
ourselves
or
at
least
try
to
do
it.
B
A
We
do
have
a
category
update,
so
we're
adding
some
feature:
labels
to
the
secrets,
management
direction,
which
includes
ci
variables,
deploy
keys
and
ci
tokens.
The
issue
or
the
mr
is
here.
What
this
really
means
is
that
our
scope
for
secrets
management
is
going
to
grow
and
allow
us
to
make
more
decisions
around
the
direction
of
like
how
we're
going
to
handle
secrets
and
ci
cd
variables
and
also
how
we're
going
to
expand
the
flexibility
of
like
the
ci
job
token.
A
B
There
was
a
active
issue
for
going
for
quite
a
while,
with
a
lot
of
discussion
about
empowering
permissions
on
ci
job
tokens
or
something
like
this.
Does
it
mean
we
need
to
take
over
this?
One
too.
B
It's
been
going
on
for
a
while,
and
they
had
a
recently.
They
had
a
sim
call
and
then
jegos,
I
think,
wrote
down
something.
So
it's
been,
and
some
customers
are
also
chiming
in
in
that
discussion,
saying
why?
Don't
you
just
extend
your
the
json
web
token
that
we
recently
created
so.
A
Oh
yeah
so
perfect,
all
right,
jan
our
tp
channel.
A
A
You
know
it's,
I
also
ping
darren
and
eli,
so
hopefully,
they'll
give
us
some
sort
of
update.
Last
time
we
connected,
we
talked
about
deploy,
keys,
it's
something
that
orig's
team
is
really
working
on,
so
something
that
we
might
want
to
add
as
a
future
tech
evaluation
issue
is
to
just
research
deploy
keys
more
thoroughly
since
we'll
be
taking
that
on
as
a
part
of
secrets,
management.
B
Yeah,
I
have
some
idea
about
them
and
yeah
they're
kind
of
secret,
because
they're
stored
and
encrypted
in
the
database,
but
okay.
So
what
what
should
I
do
about
it
right
now
or
is
there
nothing?
Okay,
so
I'll
just
have
to
give
you
a
heads
up
on.
A
Okay,
I
don't
know
what
this
deploying
to
external
platform
needs.
Code
was
for.
A
I
know
that
we
made
a
note
for
it.
It
was
like
about
the.
I
think
it
may
be
related
to
key
rotation
if
we're
talking
to
like
an
external
system,
but
I
know
for
sure
yeah.
B
The
other
one
about
rotating
secrets-
I
remember,
but
I
haven't
done
anything
about
it
and
I
just
I
just
took
a
quick
look
at
the
vault
docs
for
the
database,
one
and
how
it
works.
There
is
that
you
basically
give
vote
user
and
username
and
password
for
a
super
user
who
who
can
creates
other
users
in
the
database
and
then
vault
is
kind
of
the
manager
it
creates
when
when
it
decides
to
rotate
some
credentials,
it
creates
the
new,
the
new
user
in
the
database
and
start
returning
it
to
everyone.
B
A
That's
that's
okay.
We
can.
I
have
that
issue
so
we'll
schedule
it
in
the
next.
You
know
future
looking
priorities.
I
think
we
need
to
figure.
We
need
to
ship
our
ci
cd
integration
and
then
we
can
follow
and
suit
with
some
of
these
other
fit
and
finish
features
I'll
delete.
This
deploying
to
external.
B
A
Totally
you're
right,
it'll
come
back
up
alrighty.
B
A
B
Created
this
one
and
there's
nothing
like
any
news
about
it,
so
I
think,
do
you
know
the
base
camp,
the
company
and
that
that
basically
is
created
trails
and
they
recently
started
new
email
service
called
hey
and
I
think
they
they're
doing
that
encryption
in
hey
and
they're
about
to
open
sources
and
add
it
to
rails.
But
I
have
no
idea
when
this
happens,
so
we
can
still
do
a
research
issue
for
encryption.
Just
leave
the
rails
part
out,
because
I
was
thinking.
B
A
B
Well,
I
did
some
fishing,
I
wouldn't
say
it
was
good.
Oh
yeah,
everyone
else
did
pretty
well,
but
I
I'm
not
that
much,
but
it
was.
It
was
very
nice
yeah.
It's
I
my
right
hand
feels
a
bit
sore
after
three
days
of
casting.
B
Well,
okay,
then
I'm
at
least
I'm
it's
pretty
clear
to
me
about
the
authentication.
So
I
can
start
the
march
request
on
that
in
that
issue
and
then
wait
the
other
two
and
like
move
to
them
once
I'm
done
so
can
like
kind
of
start
transition
from
secrets
only
to
secrets
and
raw
brow
packages
or
whatever,
because
we
will
have
to
come
and
with
a
name
about
it,
because.
B
A
And
that
is
going
to
be
such
an
incredible
feature,
this
packet,
this
generic
package
registry,
not
just
for
us
like
we'll,
finally
be
able
to
deliver
release
binaries
as
a
part
of
release
generation
which
will
really
kill
it
for
us.
You
know,
but
package
is
going
to
love
this
mainly
because
nexus
is
their
top
person,
their
top
top
competitor
they're,
trying
to
erode
right
now.
B
A
A
Can
iterate
too
so
if
once
you
get
in
there
and
you
start
noticing
that,
like
the
scope
is
just
too
big,
let
me
know
and
we
can
carve
it
out
too
and
try
to
ship
it.
B
A
B
B
The
only
thing
that
they
are
doing
more
than
we
have
now,
but
we
cannot
is
like
if
you
push
a
file
and
the
file
name
has
slashes
like
directories,
then
in
the
ui
they
displayed
it
like
a
file
browser,
you
can
click
and
see
there,
which
is
always
like,
but
we
can
for
iteration
one
like
we
cannot
support
slashes.
B
So
it's
like
simple
file
or
we
can
support
them,
but
just
display
them
like
like
a
regular
file
name
in
the
list
and
they
are
not
in
a
tree
like
structure,
so
I'll
probably
stick
with
not
supporting
them
to
start
with,
because
it's
easier
and
then
we
may
like
this
and
it's
useful
only
if
you
are
browsing
through
the
ui.
If
you
are
just
like
from
ci
pulling
pushing
architecture,
it
doesn't
matter
because
right.
A
B
Yeah,
I
don't
know,
do
we
need
it
yet,
but
of
course
yeah.
B
Yeah
well,
if
you
feel
like
yeah
yeah,
maybe
let's,
let's
wait
at
least
I've
wait
this
and
we
we
have
a
concrete
plan
to
start
with
and
see
see
now.
Is
it
changing
anything.
B
A
B
A
A
A
B
A
Input
totally
okay,
so
yeah
generic
package
registry
is
definitely
top
priority
behind
vault
this
release
so
agenda,
and
then
let
me
know
if
you
have
any
other
questions
about
that.
Keep
me
give
me
close
if
you
need
any
help.
Okay,.