►
From YouTube: Gitaly mTLS test demo
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,
my
name
is
thomas
levnikich.
I
am
the
software
engineer
in
test
for
the
counterpart
groups
gitly
and
code
review
today.
I
want
to
talk
a
little
bit
about
the
mtls
tests,
how
to
run
it
and
how
to
change
specific
things
in
it.
If
you
need
to
customize
it
so,
let's
begin,
I
will
first
show
you
the
test
itself.
A
A
The
only
significant
thing
with
this
is
that
we
are
actually
initializing
it
with
a
readme
initializing
with
the
readme
means
that
it
creates
it
during
the
project
creation.
This
is
a
little
bit
different,
normally
because
it
can
be
skipped
if
the
if
the
connection
to
italy
is
broken.
A
So
this
is
then
later
on
checked
if
the
commit
is
actually
there.
The
second
content
creation
is
done
through
a
normal
git
push
and
the
third
content
creation
is
done
through
the
api
by
creating
a
commit
directly
over
the
api.
All
of
this
is
then,
in
the
end,
of
course,
checked
and
the
test
passes
if
this
pass.
A
A
A
Now
the
first
two
are
the
most
significant,
the
other
one
is
just
for
executing
the
test
itself.
As
I
said,
both
containers
are
based
on
the
main
gitlab
container.
The
only
difference
is
that
the
gitly
container
disables
everything,
except
for
italy
and
the
gitlab
main
instance,
container
disables
only
gitly.
A
What
we
then
do
is
we
link
the
certificates
that
we
use
for
italy
and
gitlab
respectively
by
linking
them
to
the
ssl
folder
inside
the
dockers,
docker
containers,
and
but
with
that
both
instances
are
actually
using
tls
to
execute
the
test.
A
We
can
use
the
normal
method
that
most
users
will
normally
want
to
use,
and
that
is
by
executing
the
specific
command.
We
can
either
execute
it
with
the
ee
instance
or
the
cens
ce
instance,
and
because
there
is
currently
only
one
test,
it
will
also
only
execute
one
test,
but
later
on,
if
we
decide
to
add
more
tests,
this
specific
scenario
will
execute
every
single
one
that
is
linked
to
mtls.
A
What
I
would
also
like
to
point
out
here
is
that
this
here
is
the
is
one
of
the
more
important
parts.
This
is
actually
linking
the
gitlab
instance
to
use
not
its
internal
gitly
storage,
but
actually
the
tls
linked
to
the
italy
docker
container,
and
this
here
is
actually
the
link
to
the
certificate
that
we're
using.
We,
of
course,
also
need
to
trust
the
certificate
on
both
sides.
So
that's
why
we
link
also
the
certificates
inside
the
trusted
search
folder
now.
A
A
You
will
have
to
change
the
certificates
that
are
available
and
are
linked
to
this
specific
folder.
The
best
way
to
do
that
is
actually
to
just
change
the
tls
certificates
that
are
inside
of
this,
but
to
use
the
new
certificates.
You
of
course
need
to
execute
the
test,
not
just
by
using
gitlab
qa,
because
gitlab
qa
is
using
the
gem
files,
but
what
you
need
to
do
is
you
need
to
execute
your
local
gitlab
qa
instance.
A
The
test
shouldn't
take
much
longer
to
execute,
because
all
all
the
images
that
were
needed
by
docker
are
have
already
been
downloaded
by
me
in
the
first
place
before
I
even
started
this,
so
in
your
case,
it
could
take
a
little
bit
longer
because
it
needs
to
download
all
the
images.