►
From YouTube: 2023-04-27 Pipeline Security Group call
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
Interesting
all
right,
hi.
Everyone
today
is
the
27th
of
April
and
we
are
meeting
for
the
pipeline.
Security,
Group
call
and
Jocelyn
is
also
joining
in
a
bit.
It
seems
all
right.
Let's
get
started
with
the
announcements.
So
Max
has
a
bunch
of
announcements.
The
first
is
reminder
that
next
week
is
verify
async
week,
Jocelyn
to
you,
hi,
hello,
hi
I
was
just
reading
through
the
announcements
that
Max
has
here.
A
Next
week,
the
next
week,
all
right-
this
is
not
the
async
work
right
next
week
we
have
async
week,
so
we
can
just
like
go
ahead
and
see
if
you
want
to
make
the
meetings
async
on
our
calendar
and
then
upcoming
verify
hackathon
all
right.
So
this
starts
on
22nd
May.
B
A
We
have,
until
the
end
of
the
week,
to
contribute
to
our
competition
analysis,
Jocelyn
and
I
saw
that
you
had
posted
like
a
summary
of
our
discussion,
so
that
was
I.
Think
that
kind
of
concludes
the
issue
and
I
really
like
the
action
items
that
were
associated.
You
want
to
talk
about
that.
C
C
I
know
we
didn't
really
like
imagine
to
build
artifacts,
since
that's
not
our
area
of
focus
but
yeah,
so
I
I,
basically
I
took
the
threads
and
I
looked
at
like
what
were
broken
down
into
actual
suggestions
on
on
actionable
items
as
well
as
items
that
I
think
were
ideas,
but
maybe
needed
a
little
bit
more
deep,
diving,
for
example,
like
Ci
job
token
versus
GitHub
tokens
are
we
solving
the
same
problem
is
what
you
know?
Are
they
solving
it
better
than
us
like?
C
Do
we
want
to
make
changes
that
type
of
stuff?
So
those
would
be
things
that
we
should
investigate
a
little
bit
more
before
choosing
a
course
of
action
on
that
and
then
I
broke
out
two
potential
collaborations,
so
yeah
I
did
my
best
to
kind
of
like
break
them
all
out
in
areas
where
folks,
like,
like
I,
think
security
best
practices.
C
That's
something
Marcel
had
already
like
commented
like
Yay
I'm,
gonna
work
on
this,
and
so
just
additional
like
action
items
below
for
what
might
be
things
that
we
need
to
consider
for
for
some
of
these
items
and
then,
if
they
sounded
like
something
that
we
actually
already
have
in
the
backlog
spent
lots
of
time
in
the
last
few
weeks,
just
going
through
our
entire
backlog.
C
Listing
like
hey,
you
know:
are
these
two
things
the
same
or
hey?
Is
this
like
an
iteration
on
something
that
we
already
have,
and
so
just
really
like
cleaning
up
our
thoughts
around
that
and
I?
Think
there's
a
few
I
want
to
say
there's
a
few
that
I
listed
as
like:
hey
like
these
are
actionable
things
that
are
at
lower
lift
that
we
can
just
get
started
on.
A
Got
it
and
yeah
going
back
to
the
issue
that
muscle
had
created
on
Mira's
suggestion
it
kind
of
really
aligns
with
what
the
runner
and
the
release
is
it
the
delivery
team,
the
new
name,
the
team
is
doing.
They
are
coming
up
with
Pages
like
for
their
stage
groups,
which
have
all
the
terminologies
that
they're
using
like
everything
on
one
place,
so
that,
like
there's,
no
confusion
like,
for
example,
what
we
use
the
term
artifacts
for
what
we
use
the
term
workspace
for
well.
A
Workspace
is
not
related
to
those,
but
I
think
this
aligns
with
that,
and
it
will
bring
some
clarity
on
how
those
different
pieces
on
very
different
pages.
They
connect.
C
Yeah
I
think
so
like
we,
we,
there
was
a
an
effort
to
rewrite
the
deprecation
notice
for
CI
job
token,
because
I
think
the
terminology
that
we
used
internally
did
not
align
with
our
documentation
and
so
yeah
I
think
really
going
through.
What
we
have
in
in
kind
of
aligning
those
words
will
really
help
our
customers.
B
A
Lastly,
I
gave
this
like
a
gender
level
facelift
like
pushing
all
the
links
in
the
Box,
because
they
were
taking
a
lot
of
space
and
also
adding
an
template
so
that
we
can
easily
just
copy
paste
and
get
started.
A
That's
all
the
announcements.
Do
you
want
to
like
take
it
from
Pure
Jocelyn.
B
C
So
we
have
Miranda's
beautiful,
recording
I,
think
super
excited
to
see
us
in
the
Ops
showcase
and
I'm
super
excited
in
general,
for
the
artifacts
page
being
in
the
wild
I
keep
telling
the
the
support
team.
When
people
are
like,
oh
well,
you
know
they
want
to
figure
out
how
to
delete
the
artifact
from
like.
Have
they
checked
out
the
new
artifacts
page,
so
I
am
shamelessly
plugging
plugging
away
on
this
one.
C
C
Let's
see
so
we
have
discussion
topics.
There
is
the
new
variable
page
I
know:
jihu
has
been
working
on
this
as
well
as
well
as
actually
our
Azure
Native
integration
and
so
for
some
of
the
items
that
have
been
in
Flight
with
that
team.
I
think
what
we're
really
trying
to
do
is
making
sure
that
it's
like
our
team,
is
now
involved
in
any
of
the
discussions.
C
Any
of
the
reviews,
since
since
that's
our
space
now,
and
so,
if
you,
if
you
get
some
miscellaneous
pinks,
that's
exactly
what
this
is
about,
is
making
sure
now
that
ownership
of
the
category
has
changed
that
we
have
a
say.
If
nothing
else
like
we
understand
what
they're
trying
to
do
since
we
will
own
any
sort
of
long-term
ramifications
associated
with
their
implementation.
C
B
C
Some
issues
where
it's
like,
hey,
like
pipeline
authoring,
keeps
getting
pinged
in
like
it
takes
a
while
before
eventually
someone
says:
oh
hey,
what
do
you
think
Jocelyn
and
then,
like?
Oh
hey,
what
do
you
think
Max
so
we're
trying
to
bring
the
team
into
those
as
awareness
for
what
work
is
going
on
and,
like
I
said,
if
we
have
to
maintain
it,
we
should
probably
be
part
of
the
discussion.
A
Yeah
and
I
I
I've,
just
like
I,
have
planned
to
get
to
this.
The
front-end
issue
today,
I
gotta,
know
about
it
in
the
morning
that
they
have
already
started
on
the
front
and
Mr
so
I'll
go
and
take
a
look
and
I
saw
this
comment
which,
like
neither
of
us,
has
yet
attended
to,
which
is,
at
the
end
of
the
issue
of
the
front-end
surface
predefined
variables.
A
B
A
A
It's
this
one,
coupling.
A
B
C
All
right,
cool,
yeah
I
feel
like
some
of
the
issues
I
have
noticed
like
they.
They
have
like
a
product
person
in
some
of
the
issues
and
then
the
actual
devs
are
in
the
merge
requests
asking
questions
and
they
don't
necessarily
I
feel
like
tie
back
to
each
other
in
terms
of
the
the
issue
and
Mr.
So
it's
definitely
been
an
interesting
experience.
C
Is
the
team
board
and
does
anyone
have
any
thoughts
around?
Is
it
useful?
What
would
make
it
more
useful?
What
are
things
that
we
have
found?
Useful
I
know
one
one
thing
we
well
I
I
need
to
work
on
is
at
one
point
you
know
we
changed
our
process
in
the
handbook
to
to
prioritize
within
those
boards
manually.
C
Like
that
way,
we
could
like
shift
them
up
and
down,
and
so,
since
we've
transitioned
to
Secrets
management,
we
really
haven't
done
that
so
I
think
like
that,
that's
one
thing
that
needs
to
get
done.
C
B
It's
a
helpful
overview,
but
I
don't
often
go
to
it
first,
because
it's
a
little
bit
overwhelming.
Maybe
that's
just
me,
though,
because
I
only
have
any
influence
over
some
of
the
things
on
the
board.
So
then,
looking
at
the
whole
board
is
a
little
overwhelming
and
you
can
filter
it
by
more
tags,
but
still.
C
Okay,
so
I
mean
maybe
maybe
we
just
look
at
reducing
like
columns
or
something
or
even
get
the
backlog.
I
don't
know
if
there's
a
way
to
just
say,
like
hey,
only
show
like
the
top,
you
know
10
items
because
we
can.
We
can
scroll
for
a
very
long
time,
a
very,
very
long
time
in
our
backlog.
B
B
C
Now,
okay,
I
I
have
something
that's
not
necessarily
a
blocker,
but
I
have
gotten
a
tremendous
amounts
of
pushback
from.
C
Csms
and
customers
around
the
JWT
breaking
of
a
change
in
the
future.
Can
we
name
them
a
little
differently
by
the
way
I
was
telling
to
beat
the
kill
last
night,
the
eye
job
token
c-I-j-w-t
token.
We
are
the
same
length
and
they
have
almost
all
the
same
letters
and
I'm
like
no.
C
We
own
both
and
they're,
both
being
deprecated,
this
Milestone,
which
has
been
really
really
fun,
but
I've,
gotten
like
just
a
tremendous
amount
of
pushback
on
this
and
so
I
we're
kind
of
like
talking
through
what
what
approach
we
should
take
on
this,
like
in
general,
we
got
feedback
from
CSM
Community,
that's
going
to
customers,
three
milestones
in
advance
and
being
like,
hey
here's.
The
laundry
list
of
all
Breaking
changes
that
are
coming
in
the
next
major
release
doesn't
go
great
and
I.
C
Think
another
thing
that
you
know
in
our
minds:
we're
thinking
like:
okay,
hey
they
have
three
months
to
make
this
change
for
really
large
Enterprise
customers.
C
I,
don't
know
if
that
really
is
enough
time.
If
we
think
about,
we
have
the
holidays
in
between,
like
the
whole
new
year,
like
the
December
to
January
time
off.
On
top
of
it,
it
I
understand
the
struggle
that
that
our
csms
have
because
of
some
of
these,
like
larger
breaking
changes.
So
that's
something
that
I
also
listed
in
the
PM
stand
up
as
something
we
should
consider.
I.
C
Also
only
half
jokingly
said
hey,
it
would
be
awesome
if
the
PM,
who
announced
the
application
had
to
follow
through
with
it
but
different
issue,
so
having
some
discussions
right
now
with
Mark
and
Dove
and
Max
just
on
how
we
can
handle
this,
because
if
we
actually
remove
the
old
methods
of
JWT,
we'll
break
a
lot
of
people
and
so
I'm
trying
to
figure
out
how
we
can
like
phase
this
in
without
too
many
people
being
too
angry
at
us.
C
Yeah,
so
not
a
blocker
but
just
FYI,
but
we
will
be
making
some
changes.
I.
Think
to
that
plan
based
on
the
response.
C
So
the
next
item
was
the
CI
variable
referencing.
C
I
am
not
100
sure
this
might
be
a
little
too
technical
for
me,
but
I
think
we
have
some
general
questions
of
how
how
expansion
of
variables
is
being
used,
maybe
should
be
used
and,
and
so
I
think
that's
something
to
research.
A
little
bit
more
on,
but
I
was
wondering
like
like
when
I
put
this
in.
C
It
was
primarily
for
the
back
end
team
to
see
if
there
was
anything
like
specific
that
they
felt
might
be
issues
with
infinite
expansion
of
variables,
because
I
can
assume
that
those
strings
can
get
a
little
long.
C
If
someone
was
was
really
really
trying
to
push
the
limits
of
the
system
there,
but
this
is,
we
do
have
a
customer
who
is
interested
and
our
variables
experience
is
something
that
we
really
should
be
thinking
about
in
terms
of
reducing
churn
with
our
customers
right
like
if
our
stuff
doesn't
work
well
for
them,
they
will
seek
alternatives,
and
so
that's
yeah.
C
That
was
that
was
why
I
brought
up
this
issue,
but
I
think
I
think
this
is
something
we
should
definitely
like
research
a
bit
more
and
understand,
like
you
know,
if
you
want
to
expand
like
what
what
are
what
are
we
talking
about
and
and
look
into
that.
A
Yeah,
and
also
like
one
of
the
comments
in
one
of
the
comments
on
the
issue,
Marshall
has
linked
the
docs
page
and
the
documentation
actually
says
that
I
don't
know
tags
can
be
expanded,
so
what
kind
of
expansion
we
are
talking
about.
These
two
places
that
are
not
matching.
A
Okay,
so
I
have
dropped
a
comment
on
the
16.0
Retro
and
this
is
to
improve
the
communication
between,
like
all
the
team,
members
and
ux,
so
that
we
are
able
to
involve
and
include
each
other
in
places
that
needs
our
attention
so
that
we
can
just
like
sail
smoothly
and
be
aware
of.
What's
going
on
and
also
like
make
do
all
the
iteration
related
discussions,
provide
feedback
gather
inputs
at
a
stage
where
we
don't
really
have
to
take
a
step
back.
A
So
usually,
when
there's
a
lot
of
discussion
that
happens
in
the
design
phase,
I
have
like
personally
experienced
that
we
don't
have
to
kind
of
make
any
compromises
when
we
move
it
to
planning
breakdown
like
the
discussions
that
happen
in
planning
breakdown.
So
we
can
like
just
weigh
the
issue
in
that
phase
and
move
on
to
development
and
that
works
really
well,
because
there's
no
ux
debt
that
there's
not
much
ux
that
that's
generated
when
we
use
that
method.
A
So
it's
kind
of
a
win-win
situation,
and
that's
why
I
was
just
trying
to
understand
from
the
team
that
what
is
it
that
I
can
improve
like
and
what
is
it
that
we
can
change
in
our
communication
style
that
we
so
that
we
can
communicate
better.
C
B
Yeah
I
guess
just
I
think
I
would
agree
Shifting.
The
discussions
earlier
helps
to
iron
out
what
we
actually
want
to
happen
and
and
making
sure
that,
like
the
designs
are
understood
and
that
edge
cases
are
covered,
and
maybe
I
will
put
some
more
thought
into
that
and
write
something
in
the
Metro
we'll
see.
B
C
Thanks
Miranda
and
I,
just
have
one
last
thing
to
add
is
just
from
a
product
side.
Our
Q2
okrs
are
in
work.
C
C
We
will
probably
focus
more
on
the
secrets
manager.
Integrations
I
know
like
we
do
want
to
build
our
own,
but
I
want
to
be
realistic
that
that's
going
to
take
a
little
bit
of
time.
So
in
the
meantime,
is
how
do
we
support
the
the
different
customers
who
already
are
using
a
third-party
Secrets
manager,
and
so
this
will
likely
be
our
our
big
area
focuses
for
Q2,
that's
not
to
say
like
we'll
have
to
have
like
a
like
two
or
three
Integrations
done
in
Q2.
C
It
just
means
like
we.
We
have
a
plan
forward,
potentially
right
like
who,
which
one
should
we
work
on?
Next?
We
have
some
data
that
shows
maybe
AWS,
but
we
also
have
some
data
that
shows
or
other
like
why
we
might
want
to
do
Google
Cloud.
C
First,
we
want
to
see
how
things
go
with
our
with
the
Azure
integration
that
jehu
has
been
working
on,
which
sounds
like
it
might
be
ready,
if
not
the
Milestone,
the
next
and
so
there's,
there's
kind
of
like
a
lot
of
I'll,
say
swirl
in
that
area
and
I.
C
Think
part
of
it
is
just
making
progress
towards
knowing
what's
next,
maybe
having
some
sort
of
mini
Playbook
in
terms
of
like
hey,
when
there
is
a
new
provider
to
integrate
with
like
here
are
the
things
we
we
should
be
aware
of,
or
we
should.
You
know
care
about
as
part
of
that
process,
but
really
making
it
easier
for
us
to
do
those
Integrations
quicker
and
faster.
A
C
You
I
I,
am
discovering
my
multitasking
talking
and
typing
skills
are
not
amazing
and
I
will
own
that.
C
So
cool
all
right.
Well,
thank
you.
Both
thanks
for
pinging
me
I
was
like
in
the
middle
of
a
slack
thing
and
was
like
oh
wait.
What
time
is
it.
A
Right
so
I'll
go
ahead
and
like
put
this
recording
on
unfiltered
and
share
on
the
channel
right,
yep
perfect.
Thank.