►
From YouTube: Terraform registry walktrhough and user requirements
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
So
this
is
our
infrastructure,
repo
that
really
this
is
how
gitlab
is
deployed
to
various
to
staging
to
production.
C
A
Gitlab
doesn't
offer
module
registry
and
gitlab
doesn't
have
a
third
party
module
register
to
be
used,
so
we
have
to
use
git
or
we
could
use
as
well.
If
the
module
would
be
in
the
same
directory
in
the
same
git
project,
then
it
could
be
just
the
file
path
to
the
to
where
the
module
can
be
found,
but
this
is
a
different
one.
So
actually
I
could
even
open
this
traffic
modules
thing,
which
I
want
to
speak
about
later
anyway.
So
I'm
going
to
open
that
as
well.
So
it's
under
under
this.
B
And
they
manage
permissions
and
access
via
the
group,
permissions
and
access.
A
A
B
If
I'm
a
developer-
and
I
want
to
spin
up
an
ephemeral
staging
environment,
I
cannot
access
this
repo
necessarily.
So
I
cannot
not.
A
B
A
Yeah,
are
you
taking
a
note
about
this
or
I
to
forget.
A
I
mean
you
can
even
add
a
comment
there,
so
what
I
wanted
to
highlight
that
at
gitlab
use
git
as
a
module
source,
or
sometimes
you
might
use
a
simple
file
path
if
it's
on
the,
if
it's
in
the
same
directory,
then
same
git
project,
then
than
this
one,
because
I
could
use
even
just
dot
dot,
slash,
dot,
dot,
slash
modules,
slash
whatever
and
together
with
git.
One
thing
that
we
have
is
this
ref
at
the
very
end,
which
is
like
a
version
as
you
can
see,.
A
B
B
A
A
A
A
Uses
where
you
have
modules
in
their
own
projects
and
you
can
reference
it
via
git
by
git
tags,
and
the
third
option
is
that
you
are
using
a
module
registry
where
you
can
have
more
elaborate
versioning
scheme
and
version
support
than
simple
git
tags.
This
is
what's
called
sember
versioning.
That
basically
means
that
this
is
a
typical
assembler.
You
have
a
major
miner
and
the
patch
version.
A
No,
it's
not
that,
so
you
can
specify
version
that.
Actually
I
want
to
use
version
1.x
or
I
want
to
use
version
1.1.x
and
then,
whenever
I
change
the
modules
as
I
want
to
as
long
as
I'm
just
updating
the
patch
version,
for
example
this
one,
then
when
I
run
trafform
again,
it
will
immediately
pick
my
most
recent
version,
because
I
want
to
choose
everything
under
one.x.
A
A
A
Let's
look
at
it
again.
I
hope
it
was
here
yep.
So
here
I'm
referencing
a
specific
version,
and
there
I
would
reference
not
exactly
but
kind
of.
I
would
say
that
I
want
reference:
one
dot
x,
right,
one
reference,
one
dot,
one
dot,
x,
yeah
and
then
the
reg
when
I,
when
the
registry,
when
transform,
runs
and
ask
the
register,
give
me
the
most
recent
version
that
satisfies
1.1.x.
B
Question
to
understand
why
they
would
use
what
changes
between
1.1.0.
So
what
are
the
small
changes
that.
A
C
C
A
Yeah
and
and
with
the
mojo
registry,
we
can
support
december
semantic
versioning,
which
would
mean
that
gitlab
doesn't
have
to
update
its
code
every
time
when
they
release
a
new
version,
because
they
could
simply
specify
here
that
it's
they
want
to
dot
x.
And
then
it
goes.
B
B
A
So
this
is
how
gitlab
uses
currently
the
modules-
and
this
is-
you
are
just
saying-
the
module-
that's
really
in
in
live,
how
it's
done.
These
are
the
three
ways
how
you
can
use
modules,
so
you
can
have
it
either
in
the
same
repository
in
a
subdirectory
and
don't
have
any
kind
of
versioning,
you
can
have
it
in
git
and
then
you
have
a
static
versioning
so
that
you
can
just
reference
a
specific
ref
or
you
can
have
a
registry
and
there
you
can
have
more
dynamic
version.
A
I
haven't
done
it
yet,
so
this
is
the
terraform
registry.
B
So
it's
just
to
help
you
get
started
with
connecting
to.
A
C
A
Yeah,
okay,
so
basically
public
modules
exist.
It's
transform,
provides
a
module
registry
for
that
that
integrates
with
github
not
with
github,
unfortunately,
but
it
exists.
If
you
want
private
modules,
then
transform
provides
private
modules
as
well,
but
this
is
what
gitlab
could
offer
to
and
having
it
integrated
with
gitlab.
That's
a
nice
feature.
B
A
Not
really
so
it's
like
telephone
cloud
works
in
a
way
that,
after
five
engineers,
you
can
use
it
for
free
and
you
have
to
pay
if
you
want
more
than
that.
So
it's
not
the
paid
version,
but
quite
often.
A
Instead
of
writing
this,
you
write
the
git
rapport
for
that
for
the
external
module
or
you
just
write
as
we
had
it
here.
You
just
write
this.
If
it's
really
a
private
module
from
detail
from
register,
you
just
say:
keep
calm,
slash,
stackdriver
logs
exclusion,.
B
Is
there
an
authentication
involved.
A
There
is
it's
totally
documented
and
I've
created
an
issue
about
that.
A
There's
no
ux
around
that!
Actually,
so
it's
because
terraform,
so
there's
a
terraform
login
command.
That
needs
to
be
run
in
this
case
and
it's
documented
by
terraform
how
how
to
do
all
those
things.
B
A
A
A
C
A
Yes,
but
as
it's
stored
in
a
file,
you
can
actually
store.
A
Already
figured
out
by
traffic,
so
we
don't
have
much
to
be.
B
A
It's
it's
not
there's
no
example
here.
So
the
only
thing
here
is
that,
instead
of
source
kv,
whatever
you
have
to
write,
gitlab.com
slash,
qbcom,
slash
whatever,
so
that's
how
you
can
reference
our
modules
and
that's
how?
Therefore,
we
know
that
he
should
look.
He
should
find
the
registry
at
gitlab.com
and
not
at
register
from
the
tile.
B
B
B
A
What
would
be
important
is
the
module
providers
point
of
view,
so
that
which
you
unfortunately
cannot
track
so
that
it
would
be
interesting
to
know
that.
Okay,
I
have
these
10
modules
and
I
would
like
to
know
how
many
of
my
colleagues
use
one
of
these
modules,
because
I
want
to
introduce
a
breaking
change
exactly.
A
Thinking
that
would
be
important,
but
this
is
okay.
This
is
different,
I
think,
than
what
what
I
understood
before.
So
this
is
the
feature
of
the
registry.
It's
not
the
feature
of
your
project.
B
A
B
A
B
A
B
A
B
A
A
A
B
A
A
C
C
A
C
A
It
okay,
I
will.
I
will
show
my
pet
project
where
we
use
the
the
registry.
B
A
It's
semi-automatic,
I
have
to
say
so.
Basically,
you
have
to
set
up
your
repository
with
the
in
the
ci
cd,
for
example.
The
thing
is,
I
don't
know
for
all
of
them.
I
know
only
for
npm,
because
that's
the
only
one
I
use.
A
Exactly
registries
like
in
the
I
know
that,
for
example,
for
npm,
it's
actually
a
zip
file,
that's
uploaded
to
the
registry.
While
for
go
by
for
go
it's
a
it's
a
directory
in
your
repository.
Go
is
just
being
developed
for
go
it's
it's
a
specific
directory
like
a
modules
directory
in
the
case
of
terraform.
A
A
B
C
C
A
A
C
B
A
We
will
have
to
be
clear
on
this
again.
I
think
the
best
we
can
we
should
do
is
to
follow
terraforms
setup,
publishing
modules.
A
C
B
Have
a
registry
gitlab.
B
Too
okay,
so
they
have
a
separate
repo,
sorry
and
they're
referencing
that,
but
it's
not
links
anywhere
in
from
one
project
to
the
other.
Besides,
in
the
code.
C
B
A
B
A
Yes,
we
have
many
examples.
Actually
one
of
them
is
the
register
itself.
A
This
is
one
of
the
examples.
It
basically
gives
you
the
name,
the
provider
name,
let's
create
on
it.
There
are
even
number
of
downloads
here
that
tells
you
how
to
to
the
provisions.
Yes,.
A
Sorry,
it
would
be
good
if
you
would
know
this,
but
we
don't
know
it,
unfortunately,
because
the
registry
is
not
aware
of
this
information.
B
A
A
Probably
not
at
first
probably
would
just
start
with
you
probably
just
start
with
your
own
modules,
because
that's
what
you
need
otherwise,
for
public
modules
you
can
use
star
from
registry.
You
don't
need
a
different
tool
for
that.
C
A
B
B
Okay,
I
have
that
version.
C
C
A
It
is,
it
is
because
this
is
a
restriction
from
car
form.
We
have
to
follow
this
scheme.
A
It
would
be
google
or
whatever.
I
don't
really
know
why
it
exists
all
the
time,
so
limits
modules
to
spec.
Actually
it's
optional,
but
it's
in
the
last.
It's
only
in
the
list.
Modules
query
is
optional,
otherwise
it's
not
so
it
has
to
have
a
provider.
I
don't
know
really
what
it
is
for
in
this
case,
because
it
doesn't
make
much
sense
to
me.
C
B
B
I
guess
path
is
a
better
thing.
This
kiwi
source.
A
A
A
A
I
understand
and
that's
totally
correct
that
we
should
edit
there
as
a
copy,
but
still
I
might.
I
might
go
this
way
because,
okay,
this
is
name
I'm
just
copying
that
it's
both
of
them
might
work.
B
A
B
A
B
A
B
B
What
we
discussed
before
so
you
said,
sometimes
it's
a
manual
upload.
Sometimes
you
name
a
folder.
A
C
C
B
A
B
A
B
A
B
A
B
A
B
A
New,
which
is
actually
another
bad
idea,
so
I'm
going
to
take
a
create
a
new
issue
about
that.
Definitely
for
for
the
future,
not
for
the
mvc.
C
A
B
A
Here
in
the
case
of
npm,
as
I
told
you,
it's
a
it's
a
zip
file-
that's
that's
stored
in
the
registry,
so
this
is
that
zip
file,
but
for
for
other
kinds
of
modules
it
wouldn't
be
as
fine.
Okay,.
B
B
B
B
B
C
C
B
A
C
A
A
B
B
C
C
B
A
B
Maybe,
as
a
template
to
use
the
instructions
within
the
template,
if
you
want
to
reference
a
module.
B
C
C
A
A
A
A
B
C
A
Okay-
so
I
just
found
this
that
it's
this
is
this
is
in
the
nicer
here.
It
has
even
examples
and
everything-
and
this
is
really
for-
for
public
use.
C
A
B
I
want
to
see
how
other
tools
would
do
this
flow.
Would
they
save
it
as
registry?
Would
they
save
it
in
a
separate
place
if
you're
using
github
instead
of
git
lab
with
terraform?
How
do
you
do
it?
That's
my.
A
Github,
so
github
no
tranform
has
integration
only
with
github
today
and,
as
I
told
you,
you
can
have
private
registries
there
as
well
for
free
on
the
transform
cloud
using
github
repos,
and
the
only
thing
you
have
to
do
for
that
is
basically
what
you
described
until
now.
You
have
to
set
up
a
gig
project.
A
It
has
to
has
at
least
one
terraform
file
in
the
main
repository.
It's
described
pretty
much
here.
A
B
B
A
Yeah,
you
could,
you
could
use
gitlab
as
well
for
that
actually,
but
it
has
some
limitations.
It's
written
somewhere.
A
B
A
A
Okay,
do
you
need
any
more
information
or
or
how
to
how
shall
we
proceed
with
this.
B
A
Docs,
hopefully,
because.
B
A
Yeah
this
is
this,
is
this
tagging
is
actually
a
super
good
developer
experience,
because
developers
know
how
to
tag
git
commits
and
that's
what
they
need
and
from
there.
What's,
where
the
connection
should
be.
Is
that
basically
we
can
easily
so
from
the
repository
we
should
link
back
to
the
project
to
the
git
project,
as
it's
done
in
our
currently
as
well.
B
C
B
A
A
A
A
You
can
say
it
has
a
main
tier
but
doesn't
have
a
back-end
tf
file
or
something
like
that.
So
because
you
can
use
a
telephone
project
to
deploy
your
infrastructure
and
you
can
use
the
term
from
project
to
to
describe
the
module
and
we
have
to
be
able
to
differentiate
between
the
two.
But
basically
it
there's
probably
a
simple
logic
like.
If
you
have
a
backend
tf
file,
then
you
want
to
deploy
to
that
using
that
back-end
state
file
and
if
you
don't
have
a
back-end
tf
file,
then
it's
a
module.