►
From YouTube: Govern:Security Policies group discussion 2022-12-06
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
Hello,
everyone
welcome
to
weekly
governance,
security
policies,
group
discussion.
We
don't
have
lots
of
things
in
our
agenda,
but
let's
get
started
so.
First
of
all,
we
have
one
item.
That's
actually
mentioned
like
during
our
like
work
on
tags,
for
adding
tags
to
security
policies
and
such
you're
saying
that
there's
a
problem
with
running
those
with
child
pipelines
like
this
child
pipelines
are,
are
always
Troublesome,
so
yeah
you
do
have
to
elaborate
on
that
or.
B
Yeah
sure
so
so
I'll
checking
or
testing
the
flow
there
I
actually
found
that
we
cannot
pass
on
the
tax
to
a
child
python
unless
we
change
the
template
and
since
we
are
actually
having
a
defaulted
update,
the
template
either
right.
So
we
cannot
pass
the
text
directly
in
pipeline.
That
happens
only
for
SAS
the
scanning
scanning
execution
policies.
B
So
no
that
part
didn't
work,
so
I've
created
another
Mr
to
update
the
docs
and
remove
the
passing
passing
on
the
text
to
the
pipeline
Park.
So
probably
for
now,
that's
that
would
be
the
first
step
and
as
Alan
mentioned,
we
can
probably
take
that
as
a
part
of
the
other
Spike
that
we
have
to
remove
the
child
pipeline
entirely.
A
Yeah
yeah
I
have
one
idea:
I
want
to
try
today,
as
I
have
some
time
to
do
some
coding,
so
maybe
I'll
I'll
just
try
it
on
see
if
it
works.
I'll,
let
you
know
in
the
more
we're
gonna
find
out,
because
if
that
will
be
simpler
than
creating
a
validation
in
Adderall
that
that's
definitely
more
beneficial
for
us
all
right
time,
you
wanted
to
add
something.
C
Just
a
note
that
I
don't
know
if
I,
if
this
is
part
of
this
or
not
or
if
I
created
another
issue,
but
if
we
could
stop
using
child
pipelines
for
SAS
and
dependency
scanning.
That
would
be
really
helpful
because
it's
breaking
the
pipeline
for
several
customers.
A
Yeah
yeah,
definitely
that's
why
we
have
the
spike
and
hopefully,
instead
of
like
having
implementation
issues
out
of
this
bike.
We're
gonna
have
a
Mars
with
the
fakes
and
we're
gonna
fix,
because
we
had
some
discussions
with
Miracle
as
well,
and
he
also
was
mentioning
that
he's
some
trouble
with
with
child
pipelines,
as
you
you're
not
able
to
directly
get
the
results
of
your
like
child
pipeline
in
your
like
main
pipeline.
So
you
have
to
go
further
and
see
the
results
there.
C
A
Great
okay,
great
all
right,
another
thing:
yeah,
as
you
know,
we
have
a
budget.
Like
your
holiday
party
budget,
we
haven't
decided
what
we're
gonna
do
within
our
group.
As
our
group
group
is
pretty
small,
there
are
two
options
that
we
can
take.
We
can
either
join
like
set
growth
and
data
science
for
filter
get
together
or
on
the
same
date,
there
will
be
like
sex
section
separating
day,
I'm,
not
sure
if
they'll
be
merged
or
not
at
least.
A
We
know
that
there's
some
sessions
and
you
can
join
them
and
you
can
reimburse
food
for
up
to
100
dollars
so
feel
free
to
do
it.
If
you
want
to
do
something
specifically
for
our
team,
let
us
know
yeah,
that's
it
I,
don't
think
we
need
to
discuss
it
right.
A
I
I
did
Small
Change
in
our
planning
process.
I've
included.
I
will
be
discussing
this
with
Sashi,
where
I've
included
the
verification
steps
in
into
refinement
process.
So
whenever
you
refine
an
issue
now
you
need
to
add
verification
steps
plus
additionally,
some
additional
cases
that
we
would
like
to
test.
A
This
will
help
us
better
understand
what
we
want
to
test
after
the
issue
is
completed,
and
this
will
help
someone
that
will
verify
the
issue
itself
to
to
actually
test
if
it's
working
or
not,
and
we
we
have
a
problem
in
the
past
where,
where
some
of
our
features
were
not
fully
tested,
and
because
of
that,
we
had
some
bugs
that
we
need
to
find
a
way
to
to
resolve
them
before
they
are
becoming
a
problem
for
others.
So
so
that's
why?