►
From YouTube: Compliance weekly - 2023-08-01
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
Welcome
everyone
to
compliance
weekly
first
of
August
2023.
Let's
talk
through
the
Milestone
broadcast
the
last
one
that
we
discussed
was
Tamil
SSO
authentication
net.
The
next
one
is
on
you,
update,
auditing
and
streaming
Docs.
B
B
I
think
another
one
you're
talking
about,
though.
Yes,
this
was
done
in
conjunction
with,
and
even
so
we
spent
I
think
there's
about
five
imrs
in
this
issue
to
completely
overhaul
the
ordered
events
streaming
docs,
which
is
a
great
achievement.
So
thanks
everyone.
A
A
I
think
it
would
be
related
to
now
I'm
using
auditor.ed.
It
Zappa.
C
Yeah,
so
this
so
monitoring
the
Cabana
logs
to
catch
audit
events
without
a
yaml
file.
I've
been
monitoring
this
for
a
month
now
and
finally,
we
closed
it
because
we
were
not
getting
any
new
audit
events
without
yaml
for
more
than
15
days.
We
also
created
a
subsequent
Mr
for
activity,
raising
an
error
whenever
a
new
audit
event
is
added
and
the
associated
yaml
file
is
not
added
to
it.
Coincidentally
and
Mr
was
created
yesterday,
and
we
actually
saw
that
the
pipeline
failed,
so
I
think
it's
working,
fine,
so
good
job.
B
Yes,
so
there
is
now
a
name
field
on
streaming
audit
events,
so
users
can
name
them
and
it
shows
up
as
the
under
that
name
in
the
accordion.
So
it
just
allows
users
to
better
organize
their
order
of
into
streaming
destinations.
D
C
So
this
is
the
one
I
was
talking
about,
so
whenever
a
new
like,
whenever
someone
tries
to
audit
a
new
event
without
a
yaml
file,
we'll
be
raising
an
exception
from
the
code
base,
so
this
will
prevent
user
like
developers
from
adding
a
new
audit
event
without
a
yaml
file,
so
it
streamlines
things
for
us.
The
the
next
one
is
also
on
me.
So
we,
since
the
audit
events,
are
now
mature
enough
and
we
have
a
a
generic
approach
on
how
to
add
a
new
event.
C
C
We
even
need
an
argument
for
this,
so
during
the
planning
stage,
the
product
managers
and
the
developers
can
see
if
we
need
an
audit
event
for
this
particular
for
that
particular
question,
so
yeah
I
think
we
should
also
probably
broadcast
this
somewhere
right
in
the
engineering
Channel
or
maybe
so
that
also
the
product
team
is
also
aware
like
they
should
be.
They
should
think
of
for
for
every
new
feature.
They
should
think
if
an
audit
event
is
required,
so.
C
Yeah
I
think
we
can
add
it
add
to
that,
but
I
was
also
thinking
if
maybe
posting
the
product
Channel
I'm,
not
sure
if
it's
allowed,
probably
the
perfect
match.
Sure
thanks.
C
Okay,
the
next
one
will
tell
me
so
this
this
was.
We
wanted
to
create
a
doc
for
listing
all
the
available
audit
events
that
we
have
so
that
users
can
see
like
What,
that
particular
event
name
means
and
they
can
use
that
to
filter,
add
as
a
filter
into
streaming
destinations.
So
the
the
tricky
thing
was
not
to
create
a
doc
which
has
to
be
created
manually.
So
this
is
an
automated
dock.
You
just
have
to
run
the
rake
and
the
entire
documentation
is
generated.
C
So
whenever
a
new
event
is
created-
and
someone
misses
to
add
that
to
documentation
the
pipeline
in
Salem
ask
the
author
to
actually
push
the
documentation
changes
as
well.
So
this
is
similar
to
the
graphql
documentation
that
we
have
right
now.
B
A
So
there
was
this
bug
which
got
introduced
because
of
the
project
project
destroyed
audit
event,
refactoring
with
it
that
I
did,
and
so
because
of
that
the
instance.
Audit
events
page
was
giving
error
if
a
project
belonging
to
username
spaces
deleted.
So
there
was
this
Mr
created
by
Michael,
who
was
which
was
actually
catching,
that
error
and
one
another
MRI
I've
created
for
fixing
that
error.
The
root
cause
was
that
the
scope
of
the
audit
event
was
not
user,
but
user
namespace.
A
C
Yeah
I
think
we
can
have
that
in
the
auditor
class
checking
we
scope
and
raising
an
error
if
it
doesn't
belong
to
any
of
these
okay.
C
Create
one
you
can
also
club
the
same
issue
for
actually
updating
the
documentation,
I
guess
which
was
spending
since
a
long
time.
A
Yeah
yeah
I
have
added
created
an
issue
for
that
and
working
on
it.
A
E
C
A
C
The
UI
side,
I
guess
the
basic
structure
was
in
place
last
Milestone
and
this
Milestone
Jay
was
working
on
integrating
the
graphql
API
on
the
front
end
so
that
it
displays
the
correct
data
and
the
database
are
not
the
marked
data
I'm,
not
sure
where
it
is
right.
Now.
A
Nice
I
made
any
sense,
so
there's
a
yeah.
You
are
saying
something
so
mostly
follow-up
Mrs
as
well
as
some
documentation
are
pending
and
test
along
with
adding
name
to
no.
No,
that's
not
part
of
that.
So.
E
C
A
B
Yeah,
so
we
have
the
name
fields
done
as
you
saw
has
been
released.
The
next
thing
is
to
try
to
do
the
filth
and
Web
projects
in
the
API,
but
I
think
this
is
more
of
a
stretch,
go
on
and
say
here,
they'll,
probably
roll
over
to
16
foot,
but
we'll
keep
on
it.
C
I
started
reading
their
documentation,
but
unfortunately
it
seems
like
the
snowflakes
snow
pipe
streaming.
Api
is
relatively
a
new
feature.
I
released
this
much
and
it's
still
a
preview
feature,
and
they
only
have
a
Java
SDK
for
integration.
They
don't
have
a
rest
API
for
it
and
they
also
don't
have
any
other
sdks.
So
probably
it's
not
a
straightforward
thing
to
implement
and
we
can
keep
this
as
blocked.
Yeah
I'll
be
posting
a
comment
on
the
issue
itself,
with
all
the
appointments.
D
Yeah,
so
for
this
we
have
completed
the
query
analysis
right
now.
We
have
a
issue
for
production
Readiness
which
we
are
going
to
do
in
16.4.
There
again,
we
will
be
doing
some
query
analysis
to
find
out
what
kind
of
infra
we
will
need,
but.
B
C
Yep,
so
on
this
one
I
guess
most
of
the
issues
are
closed.
The
feature
flag
is
also
rolled
out
globally.
We
only
think
left
is
to
close
the
feature
flag
issue
because
I'm
planning
to
leave
like
clean
the
feature
flag
in
the
next
Milestone.
So
we
can
just
leave
the
feature
flag,
close
the
determination
and
the
Epic
itself.
So.
E
It's
time
yes,
yeah
the
original
status
doesn't
fit
anymore.
Technically,
the
export
was
flagged
on
the
from
the
DBT
and
I'll
need
to
rework
it
I'm,
going
to
give
it
like
to
the
end
of
the
week
to
try
to
come
with
something
shippable
and
if
that
doesn't
work
out
I'm
going
to
let
it
roll
over
to
the
next
milestone.
D
Yeah
for
this
one,
currently
there
is
a
Mr
which
is
doing
backfilling
of
the
data,
which
is
in
review
right
now.
Once
that
is
merged,
I
will
be
able
to
work
on
further
issues.
D
There
is
an
update
here
that
one
of
the
issues
now
shifted
to
16.4,
because
we
are
doing
backfilling
in
this
Milestone.
So
a
goal
would
change
for
16.3
I
would
add.
The
I
would
add
the
comment
and
then
update
it.
E
A
E
Started
this,
like
last
week
before
I
got
sick
I'll
be
continuing
on
this
I've
made
a
little
bit
of
progress,
but
not
much
yet.
A
C
Yep,
so
we
close
the
okr
to
ensure
compliance
of
positive
event.
Names
I
closed
it
here.
Yeah
nice
work,
everyone
special
thanks
to
hercimer.
He
created
a
lot
of
scripts
to
actually
find
out.
The
events
which
are
missing
them
is.
B
Second,
there
sorry
just
quickly,
I
think
it's
a
huge
accomplish
accomplishment
to
get
this
done.
It
was
half
in
progress
when
I
first
came
from,
came
to
kitlab
and
I
think
as
I
put
in
the
fencing
it's
about
231
weight,
212
issues
and
three
sub
epics,
so
a
huge
amount
of
effort
from
everyone.
Thank
you.
A
D
Yeah
so
last
week
we
completed
the
POC
for
clickhouse
and
I
have
closed
that
Mr
now
and
currently,
working
on
a
query
Builder,
which
will
help
us
to
generate
SQL
queries.
So
I
have
updated
the
okay
progress
to
90
percent.
B
Yeah
so
the
first
one
was
just
an
FYI,
so
congrats
to
mark,
on
a
four-year
anniversary,
huge
milestone,
great,
to
have
been
part
of
this
team,
although
not
in
this
time
zone,
and
then
next
was
another
fys.
It's
just
the
last
week
to
add
your
thoughts
to
the
Retro
issue.
B
Please
remember
to
have
a
look
as
we
are
reviewing
the
Milestone
plan
goals
against
what
actually
happened
now.
So
it's
just
a
great
way
for
us
to
check
in
with
how
we
went
to
the
individual
milestone.
A
I
think
this
is
the
second
weekly
of
the
milestone
and
we
need
to
review
the
product.
Dashboard
should
I
stop
the
recording
before.