►
From YouTube: Compliance weekly 2023 03 21
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
A
A
A
B
A
A
A
A
A
Huzaifa
iftikhar
sr.,
backend,
engineer,
govern:compliance:,
the
chatops,
come
on.,
so
the
group
project
launches
a
license,
feature,
name,
or
it
can
be
used
as
a
feature
of
flagname..
So
we
had
to
red
rename
the
feature
flag
to
another
feet,
something
else.
so,,
instead
of
like
just
renaming
the
feature
cloud,,
because
someone
in
the
self
managing
sense
would
have
updated
the.
A
A
A
A
A
A
A
A
B
B
B
B
A
A
A
Huzaifa
iftikhar
sr.,
backend
engineer,
govern:compliance:
an
error
when
someone
tries
to
audit
when,
like
they
start
using
a
string
as
an
audit
event,,
and
that
that
particular
type
doesn't
have
a
yamel
file
associated
with
it,,
so
we'll
not
be
creating
an
audit
event
for
it,
and
start
throwing
an
exception..
So
unless
we
have
normal
files
for
every
audit
event,,
we
cannot
start
doing
this.
So
that's
why
it's
in.
A
Huzaifa
iftikhar
sr.
backend
engineer,
govern:compliance:.
We
want
to
add
the
capability
for
filtering
the
compliance
violations
by
branches,,
so
it
could
be
like
protected,
branches,
or
typing
a
need
to
get
the
list
to
like
to
filter
by
that
particular
branch
name..
So
I'm
currently
working
on
the
back
end
part
of
it,
and
this
one
is
plugged
on
the
back
end,
which
elia
is
being
assigned.
C
C
A
A
A
Huzaifa
iftikhar
sr.,
backend,
engineer,,
govern:compliance:
and
like,,
and
for
the
first
iteration,
it
would
be
like
exact
match..
So
if
someone
types
like,,
if
they
have
a
branch
named
main,
and
they
type
like
m.
ai,,
then
in
that
case
it
will
not
show
any
results..
They'll
have
to
type
main
to
get
the
list
of
branches.
A
A
A
Huzaifa
iftikhar
sr.,
backend
engineer,
govern:compliance:
for
an
initial,,
and
we
see
we
could
just
at
least
start
off
with
giving,,
like
the
users
ability
to
actually
search
by
the
branch
names,,
so
they'll
be
knowing
which
protected
runs..
Of
course,
it
will
have
a
limitation
where
they
won't
be
able
to
see.
A
A
A
A
Huzaifa
iftikhar
sr.
backend
engineer,
govern:compliance:,
like
there
could
be
multiple
merge
requests
being
merged
to
a
particular
branch.
so,
for
example,
for
the
grid
cloud
project
that
we
work
on..
We
have
a
master
branch
which
is
protected,
and
all
of
us
create
our
ms.
against
the
master
branch..
So
if
there
is
a
violation
in.
A
A
Huzaifa
iftikhar
sr.
backend
engineer,
govern:compliance:
yeah..
So
so,
since
the
violations
is
at
a
group
level,,
they
could
be,,
they
could
be
2.
Projects
which
have
the
same
name,
like
both
of
them,
have
master
as
the
protective
run..
So
if
you
type
in,
master,,
they
like
the
ui
doesn't
show,
like.
A
Huzaifa
iftikhar
sr.,
backend
engineer,
govern:compliance:
the
project
associated
with
that
particular
violation.
Unless
you
click
on
that
violation..
So
we
don't
have
that
in
the
the
first
screen
that
we
have
the
landing
screen,
so
that
that
was
the
discussion.,
so
it
in
the
initial
design..
So
what
I
suggested
was,,
if
we,,
if
you
start
filtering
by
the
branch
name
instead,
and.
A
A
C
Huzaifa
iftikhar
sr.,
backend,
engineer,,
govern:compliance:,
free
filter,,
a
3
products
selected
in
the
product
filter,
and
then
searching
the
free
text
for
master.,
and
then
I
got
all
3
projects
right,,
it's
master.!
So
if
if,
if
we
have
violations
for
all
the
projects,,
then
it
will
contain
like.
A
C
C
C
A
Huzaifa
iftikhar
sr.
backend
engineer,
govern:compliance:.
That
makes
it
currently
what
we
have
is
we
simply
so
like.
We
simply
show
that
we
don't
have
any
violations.,
but
what
you're
saying
makes
sense.
the
other
option,
for
that
could
also
be
a
kind
of
a
tool
tip
on
the
search
brand,
a
search
for
like
on
the
exact
search,
like.
A
Huzaifa
iftikhar
sr.
backend
engineer,
govern:compliance:,
like
we
could
have
a
tool
tape,
or
something
like
here,
with
which,
like
covering
onto
that.
it'll,
say
it'll,
show,
like
only
exact
name,
is
supported
like
what
we
have
for
particular..
I
can
even
get
on
a
call
with
you.
post
this
one
to
actually.