►
From YouTube: Compliance final planning 16.4 - 2023-08-22
A
A
All
right,
so
this
is
the
final
planning
for
16-4
for
compliance.
We're
gonna
go
over
the
priorities
first,
so
let
me
go
ahead
and
share
my
screen.
A
All
right,
so
the
top
priority
right
now
is
the
compliance
adherence
report,
the
MVC
for
that.
Getting
that
to
its
first
release
is
definitely
the
top
priority.
The
second
one
is
Samuel
SSO
authentication
for
merger
press
approvals.
This
is
re-authenticating
with
your
SSO
password.
Whenever
a
certain
setting
is
checked
for
merge,
request
approvals,
reporting
passwords.
This
is
particularly
for
audit
purposes
for
several
different
regulations
that
are
out
there
migrating
the
audit
events
to
clickhouse
Cloud.
A
This
is
a
very
important
project
that
I
will
be
working
on
for
a
few
Milestones
here,
but
this
really
sets
us
up
for
a
lot
of
improvements
in
the
future.
So
this
is
a
super
important
thing
to
get
done:
retrying
the
failed
external
status
checks,
so
that's
an
improvement
to
the
external
status
checks
that
we
already
have
so
that
you
can
easily
retry
them
and
and
don't
need
to
change
something
on
the
issue
or
the
Mr
to
to
retry
the
status
checks.
A
So
that's
a
very
good
quality
of
life
Improvement
for
users,
a
compliance
violation,
export
exporting
the
the
violations,
so
you
can
use
them
in
audits
or
as
a
report
for
anybody
that
maybe
doesn't
have
access
to
git
lab
or
that
doesn't
want
to
go
to
that
page.
If
you're
looking
at
a
specific
time
period
and
just
need
to
export
that
we'll
be
able
to
to
get
that
eventually,
so
yeah
that's
top
priority
and
then
integrating
with
third-party
storage
systems.
We've
already
done.
A
Google
Cloud
logging
we'll
go
on
to
do
AWS
and
gcp,
as
well
as
a
couple
others
like
Snowflake
and
datadog
eventually,
so
this
one
will
be
focusing
specifically
on
AWS
in
16.4
all
right
and
I'll,
throw
it
over
to
you
Nate.
If
you
want
to
go
over
the
plan.
B
Yeah
thanks
Derek
the
compliance
adherence
report,
so
we
currently
had
released
the
all
of
the
checks
that
we
had
originally
paying
for
the
MVC
and
the
basic
UI
framework
behind
the
feature
flag
in
163.
So
we
actually
want
to
complete
the
UI
and
release
that
MPC
in
164,
which
will
be
a
big
first
step
for
that
one,
the
migration
to
clickass
Cloud.
So
we
want
to
actually
plan
the
we've
done
the
query
Builder
and
are
doing
the
production
Readiness
review.
B
B
We
want
to
complete
and
release
these
both
of
these
in
16-4,
the
saml
SSO
authentication
for
merge
requests,
that's
been
planned
out
and
we
want
to
complete
most
of
the
back
end
in
16-4
and
look
to
release
that
in
16.5
yeah,
so
that
one
has
been
put
on
hold
for
a
little
bit
there.
B
But
the
next
one
is
streaming
audit
events
to
Google
Cloud
logging
at
the
instance
level,
so
we
want
to
complete
and
release
that
one
as
well
default
Branch
protection,
so
we
75
of
the
way
through
the
back
into
work.
There
there's
a
couple
of
issues
remaining,
so
we
want
to
complete
and
release
all
of
that
as
well.
B
Now,
the
next
one
is
the
streaming
audit
events
to
AWS
S3,
so
this
has
been
planned.
We
want
to
get
all
of
the
back
end
work
and
maybe
the
front
end
work
completed.
16-4
is
a
stretch
goal
but
probably
will
fall
over
to
16.5.
B
The
next
one
is
the
improve
manage
and
in
it
compliance
Frameworks.
So
we
are
started.
We've
got
the
design
complete
for
this
in
solution
validation.
We
want
to
complete
a
planning
out
of
the
MVC
for
this
and
then
look
at
starting
work
at
16.5.
B
The
next
one
is
streaming
audit
events
by
projects
and
subgroups.
So
this
was
a
adding
more
filtering
options
to
our
streaming
audit
events.
So
we
want
to
complete
the
group
level
API
to
start
with
and
then
look
at
introducing
the
UI
as
well.
For
that
and
then
we'll
look
at
doing
it,
for
instance,
level
and
also
our
streaming
to
third-party
destinations
in
the
future
milestones.
B
The
next
one-
yes,
so
there
is
so
we've
completed
the
plan
for
adding
active
and
deactivating
headers
within
the
streaming
audit
events.
So
we've
planned
that
out
and
started
on
the
API
side.
So
we
want
to
complete
that
and
roll
that
out
and
yeah
and
then
the
next
two
is
just
continually
add
in
more
audit
events
throughout
the
systems
of
make
it
more
comprehensive
and
any
more
Indian
tests
for
our
test
coverage.