►
From YouTube: UX Showcase - GitLab (Terraform) managed State design
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
A
Let
me
go
to
presenter
mode,
so
today
I'm
going
to
talk
about
the
terraform.
Let
me
go
back
so
the
therefore
managed
state
design,
so
terraform
falls
into
the
category
of
infrastructure
as
code,
which
is
managed
by
the
configure
state
and
before
I
start
talking
about
the
design,
I'm
going
to
briefly
talk
about
what
is
terraform.
A
So
terraform
is
a
tool
for
building
changing
and
burgeoning
infrastructure,
sorry
safely
and
efficiently.
So,
basically,
terraform
is
a
an
infrastructure
as
code
2,
where
the
devops
or
platform
engineer
so
devon
or
priyanka
can
describe
the
end
state
of
their
infrastructure
and
terraform
will
create
this
infrastructure
for
them.
A
So
what
is
a
terraform
state?
A
terraform
state
is
a
file
that
stores
the
infrastructure,
state
and
configuration.
So
every
time
terraform
runs
the
state
file
is
created
or
is
updated
into
a
new
version
if
it
already
exists
and
it
it's
essentially
connecting
the
configuration
to
the
real
world
resources.
A
A
I
will
discuss
later
so
we
did
introduce
a
back-end
storage,
but
we
haven't
provided
for
a
way
to
view
and
manage
the
state
files,
and
usually
users
are
actually
looking
for
the
state
files
in
kit
lab,
and
this
is
where
design
comes
in.
So
the
reason
for
providing
this
backend
in
gitlab
was
for
seamless,
terraform
management
through
one
tool
which
is
gitlab's
goal
anyway.
So
there
are
less
tool.
Integrations
users
don't
have
to
go
to
amazon
and
configure
their
remote
storage.
A
Finally,
there
is
some
cost
optimization,
so
the
users
can
avoid
the
extra
costs
of
paying
for
remote,
external
back-end
storage.
So
the
job
to
be
done
here
is,
if
I'm
managing
my
organization's
infrastructure
via
code.
I
need
to
view
and
manage
my
infrastructures,
state
and
versions
so
that
I
can
debug
and
fix
infrastructure
changes,
as
well
as
investigate
compliance
issues.
A
A
So
following
that,
I
prioritized
the
issues
based
on
what
made
sense
and
started
iterative
design
on
each
design,
nvc.
That
was
done
in
collaboration
with
the
engineering
team,
so
every
iteration
I
do.
I
involve
the
engineering
team
so
that
we
can
discuss
the
feasibility
and
also
whether
the
information
I
have
included
on
the
screen
is
what
the
users
would
be
looking
for,
some
sort
of
quick
user
feedback.
A
A
A
So
the
first
thing
is:
how
do
users
discover
the
state
files
the
first
place?
If
it's
a
terraform
project,
then
a
state
file
is
produced
automatically
through
a
commit.
A
So
an
idea
would
be
to
link
the
state
file
here
and
another
idea
was
to
add
it
here,
as
I've
commented
on
the
summary
of
the
project
following
that,
we
need
the
terraform
menu
in
the
left-hand
side,
navigation.
So
in
in
the
initial
explorations,
we
were
aiming
to
create
an
infrastructure
navigation
menu,
but
this
is
not
happening.
This
milestone
so
we're
gonna.
Add
therefore
many
two
operations.
A
I
don't
think,
and
then
the
state
file
details
page
very
high
level,
explorations
sorry
with
a
lot
of
questions
asked
here
and
I'm
going
back
here.
So
these
are
all
the
issues
I
have
linked
to
my
presentation
and
finally,
we
need
the
design
for
the
versions
of
the
state
file
which
would
be
in
the
details
page
as
well.
So
that
would
be
a
tab,
possibly
here.
A
So
after
that,
I
picked
up
each
issue
and
the
higher
fidelity
explorations,
so
the
first
one
is
to
introduce
a
project
stat
entry
for
a
project
when
a
project
has
a
state
file.
So
the
idea
behind
it
is
as
soon
as
we
know
that
there
is
a
state
file
within
a
project.
A
A
A
So
there
are
a
lot
of
ideas
here.
So
this
is
a
screen
with
a
lot
of
questions
and
then
the
evolution
of
the
screen,
based
on
the
based
on
the
feedback
where
we
have
added
pipeline
and
commit
information,
and
we
have
a
second
design
which
is
a
table
and
kind
of
splits.
The
information
we
want
to
do
solution,
validation
on
this
next
are
the
actions
that
we
want
to
allow
project
maintainers
to
perform
on
the
list.
So
I
introduced
actions
on
each
row
and
for
destructive
actions
like
remove.
A
A
I
just
have
two
low
fidelity
designs
here,
so
the
next
steps
is
to
finish
the
design
for
the
state
details,
page
and
version
support
and
do
solution,
validation
for
several
things
we
are
unsure
about,
and
the
file
state
listing
and
potentially
the
details.
Page
two
items
are
proposed
for
building
13.6,
which
is
going
to
be
at
the
same
time
as
solution
validation,
but
we'll
see
how
we
can
manage
that.
B
Thank
you
maria.
This
is.
This
is
an
amazing
presentation.
I
have
to
tell
I
love
the
approach
from
the
low
fidelity
to
the
high
fidelity,
with
those
amazing
hand
sketches.
I
haven't
seen
those
in
a
while
and
a
really
really
creative
approach,
and
I
also
like
how
you're
working
in
the
iterations
and
then
vcs
breaking
out
breaking
down
things.
So
thanks
for
showcasing
that
that's
a
that
was
a
great
process.
C
Have
a
question:
I
also
put
it
in
the
agenda.
I
also
wanted
to
say
I
really
enjoyed
seeing
your
low
fidelity
to
high
fidelity
transition.
That
was
awesome.
You
mentioned
that
you
had
a
hard
time
getting
internal
feedback
from
our
infrastructure
team,
which
I
know
is
actually
especially
important
for
configure,
because
those
are
not
easy
users
to
get
in
contact
with
easy
users
to
recruit,
so
we
need
their
feedback.
It's
really
important.
C
So
my
question
part
of
my
question
is
why
was
it
so
hard?
But
you
don't
have
to
answer
that
here,
but
then
the
other
part
of
my
question
is:
what
can
the
ux
leadership
team
do
to
help
you
get
that
that
response
from
our
internal
team,
great
questions.
A
So
I
don't
know
I
usually
ping
the
infrastructure
team
without
specifically
pinging
any
people.
I
don't
want
to
put
the
burden
of
the
specific
people.
I
need
your
feedback,
so
usually
my
message
doesn't
get
any
replies,
so
one
person
replied
and
I
asked
them.
Are
you
okay
to
keep
providing
feedback?
And
they
said
yes,
so
then
I
think
this
person
specifically,
I
think
so,
because
the
infrastructure
team,
I
guess
people-
do
different
jobs
depending
on
their
role.
C
Yeah,
we
can
absolutely
make
that
happen,
because
what
I
would
like
to
see
us
doing
is
treating
our
internal
users
the
same
way.
We
treat
our
external
users.
So
it's
beyond
just
here's
an
issue.
Can
you
give
me
feedback?
It's.
I
have
a
research
project
here.
Are
my
questions?
Here's
how
I'm
going
to
get
you
through
this,
so
I
can
get
my
answers
and
that
is
if,
if
you're
struggling
to
make
that
happen,
I
totally
understand
why
don't
feel
like
you
have
to
do
that
by
yourself.
You've
got
justin.
You've
got
valerie.