►
From YouTube: Compliance weekly - 2023-08-09
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
Foreign
welcome
to
the
compliance
weekly
for
August
9
2023
first
up
is
to
walk
the
Milestone
board,
so
I'll
go
ahead
and
share
my
screen.
A
And
looks
like
last
week,
we
ended
off
on
deleting
accounts.
Personal
projects
causes
error
to
audit
events,
so
start
with
this
one
ADD
test
for
gcp
login
cash
update
me.
C
D
It
was
observed
in
testing
environments,
that
instance
level.
Audit
events
are
not
streaming
sometimes,
but
Mark
eventually
forms
found
out
that
maybe
that
wasn't
streaming
workers
issue
or
sidekick
worker
issue,
but
Marco
is
not
able
to
regret
it
later.
So
he
has
closed
it.
A
Okay,
thanks
and
then
I'll
speak
to
this
one
yeah.
The
adherent
support
list
was
merged
in
and
connected
to
the
graphql
query
that
josefa
had
made
I
just
want
to
do
a
quick
note,
thanks
to
zayford,
for
doing
that,
quick
fix
on
the
constant
but
yeah
that's
up
and
behind
a
feature
flag.
E
Some
weird
issue
when
like
when
you
go
to
the
compliance
and
run
the
studios
tab
and
you
try
to
move
to
the
compliance
framework
star,
which
is
the
third
tab.
The
selector
is
still
on
the
second
tab,
which
is
the
violation
stuff,
so
I'm
not
sure
what
part
of
this
it's
just
a
UI.
But
if
you
can
just
take
a
look
yeah.
A
I'll,
take
a
look.
This
one
automatic
user
deactivation
isn't
logged
to
audit
events.
Does
anyone
know
about
this?
One.
B
Okay,
yes,
yes,
Samia
had
added
these
ordered
events
for
the
user
deactivation
a
few
Milestones
ago,
and
it
was
found
that
it
was
the
slight
bug
where
I
can't
quite
remember
it,
but
yeah.
They
created
the
email
and
fixed
this
up
straight
away.
So
thank
you
are
doing
that
all
right.
A
Okay,
thanks
next
up
migrate
usage
of
audit
changes
mixed
into
auditor
service.
Personally,.
C
Yeah,
so
basically,
ordinary
changes
is
already
using
auditor
service.
Here,
it's
just
a
wrapper
around
it,
so
I
just
close
the
issue.
Next
one
is
also
with
me
here.
The
project
changes
class
was
not
generating
any
duplicate.
Audit
events
I
verified
that
locally
and
closed
session.
B
But
basically,
in
a
subgroup
you
are
allowed
to
create
and
edit
compliance
Frameworks,
which
caused
a
few
issues
because
they
are
automatically
applied
to
top
level
groups.
We
just
had
to
remove
their
functionality
and
there
was
just
a
flag
that
wasn't
being
evaluated
to
a
probability
and
was
being
evaluated
as
a
string.
So
it
was
a
quick
fix
but
yeah,
something
that
was
causing
a
little
bit
of
confusion.
B
A
Nice,
nice,
quick
fix,
add
audit
events,
for
instance
streaming
headers
hitesh.
D
As
added
audio
device
streaming
headers,
for
instance,
level
auditing
in
destinations,
now
that's
done.
A
Thank
you,
follow-up
ad
streaming
destinations
for
the
top
linked.
B
Yeah,
this
was
just
closing
it.
We
is
won't,
do
the
way
that
currently
the
streams
are
and
the
destination.
Sorry
streams
are
added,
we
have
the
HTTP
and
then
the
gcp
one,
so
we're
not
able
to
add
the
gcp
ones
to
the
top.
At
the
moment,
we'll
probably
look
at
this
again
when
we
add
in
a
third
streaming,
Destination
type.
A
Okay,
so
let's
get
QA
failure
and
QA
specs
features.
Anyone
know
this
one.
F
A
A
Follow-Up
from
our
documentation
for
available
audit
event
types
think
Nate.
Do
you
remember.
E
I
can
talk
about
this
one
so
located
in
we
created
the
documentation
for
the
list
of
available
audit
events,
then,
even
while
reviewing
that
he
suggested
to
add
a
couple
of
changes
to
explain
these
columns,
so
he
created
that
Mr
and
that's
also
much
to
production.
Now.
This
is
close.
E
A
Thanks
next
up
add
documentation
for
event
filters,
for
instance,
destination.
D
A
Great
place,
add
event,
type
information
for
audit
events
using
Auto
event,
service
and
group
creation.
D
Yeah,
so
this
regarding
to
that
audit
operation
being
sent
as
the
event
type
for
group
creation,
so
we
have
now
changed
it
to
group
created
so
Mark
I
know.
I
have
also
mentioned
it
in
some
issue
that
you
are
using
audit
operation
as
Z
event
type
for
group
creation.
So
please
take
a
note
of
this,
because
otherwise
the
test
will
start
to
fail.
E
Yeah,
so
this
was
the
second
check,
so
this
is
like
whenever
NMR
like.
If
this
the
group
settings
of
the
project
setting
doesn't
have,
this
check
enable
the
in
the
com,
compliance
Center,
the
adherence
report
we'll
see
it
as
paid.
So
this
is
the
second
check
and
the
third
check
for
checking
if
at
least
two
approvers
are
there
in
every
merge
request.
That's
also
in
the
maintainer
review
right
now,
so
once
that
is
first
we'll
be
done
with
all
the
three
checks
for
the
gitlab
standard.
A
Thanks,
that's
awesome
and
this
one
add
instance:
scope
for
audit
events
and
documentation
attached.
D
E
Yeah,
so
this
was
just
merely
a
verification:
I
verified
that
quality
events
are
not
created
when
the
feed
supplies
are
not
updated.
We
have
a
condition
there
and
we
also
have
an
aspect
to
validator.
So
I,
just
close
the
issue
I
got
a
commented
close
to
issue.
A
E
Yeah,
so
the
goal
was
to
implement
two
more
checks:
I
have
implemented
two
more
checks.
The
second
one
is
in
maintain
a
review
right
now.
I
also
have
an
MR,
which
is
in
draft
for
running
these
checks
whenever
a
new
project
is
created
so
once
the
third
check
is
merged.
I
can
also
push
that
Mr
for
review,
which
was
my
plan
in
this
Milestone,
but
yeah
I
just
took
a
look
at
that.
A
Thanks,
that's
awesome
and
then
to
add
on
to
that.
For
the
UI
side,
the
sidebar
Mrs
created
I
just
did
I
did
notice
something
that
I
need
to
address,
and
then
I
also
want
to
take
a
look
at
what
you've
mentioned
with
the
issue
when
you
switch
to
the
third
head.
A
A
Yeah
I
think
she
makes
for
this
one
emit
instance
level
streaming.
Audit
events.
D
A
So
thanks
streamed
order
events
filtering
with
UI.
B
Yes,
we
have
released
the
name
field,
one
so
that's
been
ticked
off
the
filtering
by
project
is
probably
a
little
bit
ambitious
and
might
not
make
it
in
16-3.
So
but
that's
yeah,
sort
of
was
always
an
ambitious
goal.
E
It's
the
next
one
is
with
me
integrating
third-party
storage
systems,
so
we
wanted
to
complete
snowflake
this
time.
This
Milestone
but
I,
checked
that
snowflake
doesn't
have
a
public
rest
API
to
integrate
with,
and
the
GDK
like
tsdk
that
they
have
that's
only
in
Java
and
they
don't
have
a
Ruby
version
for
it.
We
also
spoke
to
the
people
at
Snowflake
and
they're,
saying
that
they
are
like
actively
developing
the
rest
API
so
once
that
is
public,
we'll
be
integrating
it
with
that.
E
So
I
was
just
taking
a
look
at
the
instead
of
integrating
with
snowflake
I
started,
taking
a
look
at
the
AWS
version,
so
I
think
yeah
I'm
currently
seeing
how
we
can
integrate
it
with
with
that.
But
it
will
be
like
a
couple
of
issues.
A
Okay,
no
thanks
and
thanks
for
looking
at
the
alternative
until
that's
that's
ready,
arsenaline
with
the
migrant
audio
events
to
click
host
clip.
C
Yeah
on
this
last
week,
I
created
a
mod
for
query,
Builder
and
that
got
merged
yesterday.
So
the
next
step
is
to
create
another
Mr
for
writing
a
model
specific
to
black
house
and
also
start
with
clickhouse
production.
Readiness
review
Nate
has
also
created
IMR
for
clickhouse
production,
Readiness
and
yeah.
F
E
Yeah
the
this
is
the
NVC
one
that
we're
working
on
so
yesterday,
I
also
created
Mr
to
remove
the
feature
flag
and
that
is
also
merged.
Now,
so
I'll
be
just
going
ahead
and
closing
this
Epic.
A
A
Sam
was
working
on
the
compliance
violation,
export
fam
and
I
paired
last
Thursday
or
Friday
I
guess
for
his
time,
and
we
had
discussed
it
and
I
think
there
was
some
concerns
with
from
the
maintainer
database
review
if
I
remember
correctly,
so
we
did
a
little
bit
of
debugging
and
through
database
lab,
we
were
able
to
reduce
it.
A
little
bit
and
I
haven't
followed
up
on
that.
Yet,
but
I
believe
we
got
it
to
a
point.
A
That's
acceptable,
we'll
I'll
follow
the
same
with
that
on
the
next
pairing
yeah
Heart
Smart,
with
default,
Branch
protection
drop
down.
C
Yeah
for
this
we
have
done
the
back
filling
of
data
and
I've
created
two
more
Mrs
to
for
adding
those
new
new
fields
in
the
API
which
are
in
review
right
now,
and
the
next
ones
that
those
are
merged.
I
can
start
with
the
documentation
and
actually
start
using
those
columns.
The
usage
of
columns
will
shift
to
16.4
because
backfilling
was
done
in
this
milestone.
A
B
A
Nice
hitesh
trust
and
safety
streaming
audit
events,
requirements.
D
So
I
started
on
one
of
the
issues
in
this
related
to
user
registration
from
UI,
so
I
faced
one
issue
regarding
several
details,
which
gets
filled
up
after
the
onboarding
is
completed
so
I'm
thinking
of
adding
a
new
audit
event
rather
than
using
the
existing
one,
because
that
will
provide
the
existing
one
is
providing
incomplete
detail.
A
Okay
sounds
good
Mark,
who
has
increased
onto
end
test
coverage.
F
Yeah,
my
focus
at
the
moment
is
re-enabling
the
streaming
audit
event,
tests
and
updating
them
and
then
yeah
I'll
get
started
on
the
next
priority.
New
test
I
was
going
to
ask
you
Nate,
which
one
should
that
be.
F
B
Yeah
yeah
I
feel
like
we
did,
discuss
this
and
I've
completely
forgotten.
B
Yeah
the
same
yeah,
the
Samuel
one
with
the
work
that
Sam's
doing
I,
think
it'd
be
good
to
test
the
password
off
and
then
add
in
the
salmon.
At
the
moment,
I
think
authors
I
mean
that
we
definitely
want
to
make
sure
we
don't
break.
A
A
Yeah
I
think
that's
it
for
the
planning
issue.
Nate
you
it's
qta,
Q2,
okay,
let's
have
been
added
I,
think
everyone's
had
a
chance
to
actually
see
them.
Anything
you
wanted
to
discuss
with
those.
It
was
a
little
too
early.
No.
B
No
I
just
wanted
to
call
out
again
that
they're
in
there
and
yeah
please
go
in
and
add
any
details
you
want
around.
You
know
specifics.
B
Thanks
around
you
know
what
will
constitute
a
percentage
at
each
change
that
sort
of
stuff
but
yeah.
We
can
go
over
that
in
detail.
A
Cool
thanks,
yeah
and
then
the
last
note
for
today
was
just
the
hackathons
coming
up
on
August,
10th
and
11th,
which
I
believe
is
the
next
day
for
a
majority
of
folks.
Here,
I
just
wanted
to
see
who
was
planning
to
participate
and
if
we
wanted
to
move
it
out,
but
it
looks
like
there
is
a
little
bit
of
participation
in
the
issue
and
in
the
slack
channel,
so
we're
good
to
go
ahead
with
it.
Just
start
or
I
can
put
a
little
note
on
the
issue.
A
Oh,
yes,
sorry
thanks
Nate
yeah,
so
it
would
I
wanted
to
know
it
would
be
pretty
nice
if
to
pair
with
each
other.
If
you
can
it's
going
to
be
definitely
hard
with
different
time
zones,
but
I
think
there's
a
few
ideas
on
the
list.
If
anything
anyone
wants
to
pair
together,
it's
definitely
encouraged
but
don't
have
to
and
I
know
making
time
zones.
Work
is
hard,
so
yeah.
E
I
was
thinking
like
those
ideas
are
pretty
Less.
In
my
opinion,
I
mean
it's
difficult
to
complete
those
in
a
single
day,
so,
like
this
time
could
be
just
picked,
an
epic
which
has
multiple
issues
somewhat
somewhat
related
to
like
what
we
had
last
time,
creating
the
yaml
files
for
the
missing
events.
If
we
have
any
epics
of
that
kind,
we
can
probably
like.
A
Yeah
no
but
yeah
that
was
all
for
today.
I
will
stop
the
recording.