►
From YouTube: Compliance weekly - 2023-08-30
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
the
compliance
weekly
of
the
30th
August
2023.
First
we'll
go
through
the
Milestone
board
and
discuss
the
closed
issues.
I'll
just
go
ahead
and
share
my
screen.
A
A
This
is
my
screen,
visible,
I
think
we're
still
loading
yeah.
Last
we
discussed
was
ad
models,
for
instance
gcp
login.
The
next
one
is
update
compliance
violation
date,
Quicken
labels.
This
is
with
Nate.
We
want
to
talk
about
this
yeah.
B
So
that
was
a
design
that
came
and
come
up
with.
We've
discussed
it
though,
and
there,
because
it's
a
good
lab
UI
component.
We
can't
actually
make
the
intended
change
without
causing
a
lot
of
overhead.
So
we
decided
to
scrape
the
issue
for
now
and
create
an
issue
in
the
gitlab
UI
repo
around
making
it
more
configurable.
A
Should
I
remove
it?
No.
A
The
next
one
is
ADD
name
flips
to
GCB
logging
streaming
audit
events,
I
think
this
is
also
the
Dual
net.
B
Yes,
so
we
now,
we
previously
had
added
a
name
field
for
being
able
to
name
httpdp.
This
streaming
destinations,
we've
now
added
a
name
field
for
naming
Google
Cloud
logging
streaming
destinations,
so
this
means
that
you'd
just
be
able
to
more
easily
identify
which
streams
the
setup
for
which
and
be
able
to
name
them.
However,
you
want
to.
A
The
next
one
is
not
seeing
failed
sign
in
order
Dimension
or
not
Jason,
so
this
was
created
a
week
ago
and
coincidentally,
I
was
working
on
another
issue
where
we
wanted
to
add
audit
events
for
failed
logins
using
the
gitlab
auditor,
so
that
Mr
actually
fixes
this
one.
So
I
have
added
a
comment,
also
verified
locally,
but
the
logs
are
now
in
order.
Json
I
also
tagged
the
creator
of
this
issue,
let's
see
if
they
upgrade
to
16
for
and
they're
able
to
fix
this.
A
So
close
this
the
last
one
is
no
no
audit
event
for
user
removal
from
group
by
domain
experts.
C
Yes,
this
one
was
a
bug.
I
worked
on.
This
was
we
falsely
were
logging,
the
user
was
the
member
was
added
to
a
group,
even
when
the
domain
restrictions
after
that
basically
didn't
allow
access.
So
this
fix
remedies
that
we
don't.
We
don't
no
longer
audit
if
the
member
isn't
valid.
So
we
check
before
that-
and
this
gets
rid
of
that
bug.
C
Yeah
yeah,
we
just
blocked
the
audit
event,
even
though
the
member
was
wasn't
actually
created
in
that
case.
So
there
was
a
basically
a
failed
check
for
the
member's
existence
before
we
audit
it.
It
yeah
once
once
I
knew
where
the
bug
was.
It
was
easy
to
fix,
but
finding
it
was
the
hard
part.
A
Yeah,
so
this
brings
us
to
the
end
of
the
closed
issues.
Next
I'll
move
ahead
to
the
16
for
planning,
discuss
the
planning
for
16
for
the
first
one
is
assigned
to
me
the
compliance
adherence
report,
so
the
goal
was
to
backfill
the
compliance
standards.
Adherence
for
existing
projects,
I
have
an
MR
open
for
this,
which
is
reviewed
by
the
database.
Reviewer
I
have
plenty
of
things
to
address
there.
A
Also,
we
got
an
incident
a
couple
of
days
ago
wherein,
after
we
rolled
out
the
compliance
adherence
report,
we
were
getting
some
rollback
queries
in
the
database
which
were
running
in
definitely
so
we
have
disabled
the
feature
flag
for
now
and
that
work
is
not
getting
queued.
Enqueued,
so
I
also
have
to
investigate
on
that.
So
that's
the
progress
which
might
hamper
the
164
Target
here.
A
The
next
one
is
to
migrate
audit
events
to
clickhouse
customer.
Do
you
want
to
talk
anything
about
this.
D
Yeah
so
this
week
we
will
be
doing
some
load
testing
using
jmeter
locally,
and
then
we
can
start
doing
it
on
stable.
A
S
the
next
one
is,
we
try
fail
external
statistics.
The
Mr
was
interviewed,
I'm,
not
sure.
If
anyone
knows
what
status.
A
Probably,
when
Jay
comes
back,
he
can
update
us
on
this
one.
The
next
is
compliance
violations,
export
with
Sam.
C
Yes,
there
I
haven't
made
much
progress
yet
because
I
haven't
had
the
ability
to
get
to
it,
but
the
status
is
still
there's
still
some
DB
issues
to
resolve
and
then
we'll
absolutely
hopefully
get
it
out,
maybe
under
a
feature
flag.
If
the
issues
can't
fully
be
resolved
and
might
need
some
production
testing
with
a
feature
flag.
A
Okay,
the
next
one
is
again
with
use
same
SSO
authentication
for
merge,
request,
approval.
C
Yeah
that
one
is
Stone
development.
A
So
we
don't
like
the
streaming
already
once
the
snowflake
I
guess
we
are
blocked
on
this
one.
We
have
discussed
this
a
couple
of
times
and
this
has
been
moved
to
the
backlog.
Now.
The
next
one
is
streaming
all
the
difference
to
a
Google,
Cloud
login.
B
D
Yeah,
so
one
issue
was
remaining
in
16.3,
which
is
March
now,
and
two
more
issues
are
left,
one
being
the
documentation
and
other
is
to
start
using
the
new
column,
so
yeah
first
one
is
in
diagram.
A
The
next
one
is
a
streaming
audit.
Events
to
AWS
S3
I
have
created
issues
and
have
still
not
started
working
on
this
because
of
the
adherence
report,
so
once
I'm
done
with
that,
I'll
I'll
switch
over
to
this
one,
but
we
have
a
plan
to
add
or
extreme
audit
events
to
AWS
history.
At
least
the
group
object
events
in
the
initial
development.
B
Yes,
I've
created
the
MVC
epic
added
a
bunch
of
issues
and
planned
that
out
of
requested
a
review
from
Cam
and
Elia
just
to
get
some
feedback,
it's
all
front
end
at
the
moment.
So
hopefully,
then
we
can
start
scheduling
in
some
of
that
for
16.5,
but
yeah
we'll
see
how
we
go.
A
All
right,
the
next
one
is
to
add
the
ability
to
stream
positive
events,
filter
them
by
subgroups
or
projects,
I
I'm,
not
sure
about
the
status
of
this
one.
We
plan
to
release
this
in
16th
floor,
at
least
for
the
group
I'm,
not
sure
where
we
are
right.
Now
all
the
Milestones
seems
to
be
65,
except
these
two.
A
Not
sure
if
it
would
be
able
to
release
this
in
164
or
not
the
next
one
is
HTTP
destination,
streaming
order,
events
and
movements.
A
B
This
will
this
is
adding
the
active,
the
active
headers
to
the
HTTP
streaming
destinations,
so
that
is
I,
believe
in
review
and
the
API
site.
So
they'd
been
started
in
the
previous
milestone.
A
What's
this
like
a
requirement
from
the
customer
or
something
that
we
came
up.
B
To
it's
been
in
the
product
for
a
while
now
and
has
just
not
been
enabled
it's
just
adding
something.
So
we
wanted
to
tidy
this
up.
A
The
next
one
is
comprehensive
instance,
level,
audit,
logs
I,
believe
a
lot
of
us
are
already
working
on
one
or
two
issues
in
this
one.
So
and
it's
probably
a
long
so.
A
Has
been
consistently
adding
coverage
so
I
believe
this
should
be
on
track.
Nick.
Do
you
have
any
Edition.
B
No
and
I
haven't
been
able
to
catch
up
with
Mark
the
last
couple
of
weeks,
so
I'll
try
to
catch
up,
I
believe
the
group
level
streaming
was
in
review.
There
was
a
problem
that
a
few
blockers
but
had
been
unblocked
now
and
then
was
planning
on
getting
into
the
saml
SSO
authentication,
for
which
request,
at
least
starting
to
plan,
that
out
with
the
work
that
Sam's
done.
A
First,
let's
check
what
we
have
in
December.
A
I
mean
we
have
some
FYI
and
questions.
Maybe
you
want
to
help
you
guys.
B
Yeah,
just
to
I,
guess,
reiterate
and
we've
created
an
email
to
add
a
slight
process
around
being
clearer
to
outline
the
expectations
for
Milestone
planning
yeah.
Please
have
a
read
through
and
add
your
thoughts
or
at
least
thumbs
up
and
I
have
gone
through
and
added.
So
this
new
labels,
scoped
labels
added
and
I've
added
those
to
all
of
the
current
milestone,
planning
and
ready
for
development
issues.
B
So
please
review
those
and
respond
back.
If
you
don't
agree
or
yeah,
we
can
go
from
there.