►
From YouTube: Repeatable DB creation Demo (2021-10-27)
A
A
We
need
for
both
ensible
and
terraform
for
the
sandbox
environment,
and
I
started
to
prototype
that
as
well,
but
I
won't
be
able
to
continue
it
before
I
go
on
leave
and
then
move
the
sandbox
gcp
project
into
gl
in
for
config
management
and
let
that
be
sort
of
the
environment
we
use
for
testing
repeatable
db
before
we
add
a
database
cluster
to
staging
pokemon
since
you're.
The
only
one
here
does
that.
Does
that
sound
like
a
reasonable
plan
to
you
and
you
have
any
questions
about
it.
B
A
A
B
A
Yeah
I
mean
I
was
thinking
like.
Maybe
we
just
destroy
the
infrastructure
in
the
project,
but
we
don't
yet
delete
the
projects
so
that
we
still
have
the
we
still
have
the
bootstrap
in
case.
We
want
to
bring
them
over.
You
know
and
buddy,
I
suspect,
we'll
just
probably
we'll
be
fine
with
just
a
single
sandbox
environment.
Okay,
I'll
before
I
end
my
day,
I'll
I'll
kind
of
write,
these
notes
into
the
epic
and
create
the
issues
for
them.
A
The
changes
that
happen
because
of
this,
though,
are
you
have
to
you-
have
to
reference
all
the
roles
with
gitlab.infra.
So,
instead
of
role
console,
you
have
gitlab.info
that
console
that's
a
pretty
simple
change.
I
mentioned
in
1c
that
you
can't
use
the
dashing
of
all
names.
That's
not
a
big
issue.
A
B
Yeah,
I
would
agree
and
given
the
release,
series
and
rebates
of
what
have
been
recently
immersed
in
get,
they
seem
to
break
some
stuff
of
ours,
so
we
need
to
directly
catch
with
all
these
updates
so
yeah
for
answer.
It
seems
reasonable
to
drop
it,
and
maybe,
if
we
depend
on
any
of
the
common
rule,
maybe
we
can
just
import
it
verbatim.
A
Yeah
like
what
I,
what
I
did
here
in
the
mr,
is
that
instead
of
referencing
it
with
like
a
relative
path,
I'm
just
using
like
playbook
der
special
variable
and
get
roles
but
yeah.
Then
we
could
just
bring
this
like
this
console
template
and
I
think
there's
one
more
that
we
reference.
We
can
just
bring
that
into
the
role
itself.
A
Cool
okay,
I
also
moved
all
the
plugins
into
the
collection
as
well,
so
those
are
in
the
plug-in
and
filter
subdirectories
under
plugins,
but
the
same
you
have
to
represent
with
gitlab.infra
and
then
the
mean,
I
think
that's
I
think
that's
pretty
much
it
I
did.
I
did
attempt
an
upgrade
to
211,
which
I
ended
up.
I
think
I
don't
need
to
do
now,
but
so
I
might
pull
back
on
that
we'll
see
if
everything
works
well,
they
they
renamed
the
package
from
ansible
to
ansible
core
from
210
to
211..
A
A
I
don't
I
don't
know
like
so
I
I
don't
know
what's
going
to
happen
because
since
we
removed
the
external
ip,
I
think
the
ansible
host
will
be
just
whatever
ip
like
will
be
the
private
ip,
which
is
what
we
want
right
like
or
I
I
I'm
not
sure
I
need
to
try
it
in
ci,
I
I
tried
it
locally
and
it
seemed
like
it
was
okay,
but
I
I
need
to
I
need
to
verify
it
and
see.
I
guess
before
I
can
say
that
it's
not
going
to
cause
a
problem.
A
A
B
A
If
I
had,
I
had
one
more
question
about
that.
So
are
you
so
we
have
the
the
internal
subnet
slider,
which
is
like
the
the
subnet
assigned
to
the
environment?
Are
you
using
like?
Are
you
creating
a
subnet
within
that
slider?
Are
you
creating
are
using
that
citer,
as
the
subnet
like
are
using
that
full
subnet
for
the
servers.