►
From YouTube: GitLab 13.2 Technical Showcase
Description
The GitLab 13.2 Technical Showcase includes:
Tye Davis, Senior Technical Marketing Manager- Agile, covering assigning issues to iterations and Jira issues in GitLab
William Galindez Arias, Technical Marketing Manager- SCM, and Michael Friewdrich, Developer Evangelist, covering GitLab Figma Plugin
Itzik Gan-Baruch, Technical Marketing Manager- Verify, covering dynamically generating Child Pipeline configurations with Jsonnet (part of CI Use)
Fernando Diaz, Technical Marketing Manager-DevSecOps, covering Container Host Monitoring and Blocking
Cesar Saavedra, Technical Marketing Manager- GitOps/ IaC, covering multiple Terraform plan support in merge requests and read-only access to Terraform state API
A
A
B
B
It's
not
just
technical
marketing
team,
though
we
also
have
the
technical,
evangelism
team.
We
worked
together
on
presenting
some
things
here,
and
so
you
guys
will
meet
the
folks
as
we
as
we
get
going,
but
we're
going
to
cover
a
series
of
things.
I've
told
each
team
they've
got
10
minutes
right
because
we
want
to.
B
We
got
a
lot
of
stuff
to
cover
here,
but
a
given
amount
of
time
so
we're
going
to
do
a
little
bit
of
q
a
at
the
end
when
we
can,
on
the
clock
any
other
q
a
that.
We
don't
have
time
for
that.
You
do
have
questions,
put
them
in
the
dock
and
I
think
chris.
If
we
have
time
at
the
end,
can
we
also
just
come
back
around
and
come
back
to
the
questions
that
we
don't
get
to
and.
B
Sure
we
answer
them,
you
know
asynchronously,
so
in
general,
each
team's
going
to
cover
what
is
it?
Why
does
it
matter
how
it
works,
either
through
a
screenshot
or
through
a
live
demo?
There's
a
learning
more
slide
with
links
and
then,
as
I
mentioned,
a
little
bit
of
q
a
if
we
have
time
for
each
group
with
that
I
am
going
to
stop
sharing.
That
was
all
I
want
to
share
and
turn
it
over
to
ty.
Who
has
the
first
couple
if
ty
is
on
the
call.
D
Presentation
all
right,
my
name,
is
ty
davis.
I
am
part
of
the
team
mm
team
that
focuses
on
manage
and
plan.
I'm
gonna
be
talking
about
just
there's
a
couple
things
that
came
out
more
than
two
things
that
came
out
for
plan,
but
I'm
going
to
talk
about
two
of
the
top
ones,
one
that
has
been
heavily
anticipated
for
a
long
time
is
assigning
issues
to
iterations.
D
So
something
that
has
you
know,
been
a
request
from
a
lot
of
customers,
a
lot
of
us
internally
as
well,
in
order
to
track
based
on
not
just
using
milestones
where
we
can
only
have
one
specific
milestone
for
an
issue
where
you
can
have
multiple
choices
of
having
maybe
a
milestone.
That
is
a
let's
say,
a
release.
D
D
D
Why
does
this
matter
this
matters,
because
we've
seen
many
many
requests
come
from
customers
where
they
are
deciding
against
another
project
management
tool
that
has
these
things
in
place.
Many
of
you
come
from
project
management
tools
that
long
have
had
this.
I'm
not
going
to
call
it
simple,
but
this
ability
to
identify
sprints
and
releases
and
group
that,
together
with
the
issues
that
you're
working
on
these
are
just
a
few
of
the
quotes
that
we've
seen
in
the
issue,
that's
open
to
the
public.
D
That's
been
being
worked
on,
and
so
from
an
agile
perspective.
This
will
help
teams
better
coordinate
their
efforts
if
they're
doing
scrum,
if
they're
having
sprints
that
are
part
of
that
scrum
in
the
long
run
we'll
be
able
to
have
metrics
around
those
those
iterations
or
if
they're
using
the
sprints,
you
can
pull
metrics
around
that
specific
work
being
done
in
those
iterations
and
that
helps
teams
who
are
doing
have
velocity
baked
into
the
work
that
they're
doing
or
they
are
trying
to.
D
D
It's
going
to
show
is
very
small
screenshots,
but
this
was
the
template
so
sprint
one
sprint.
Two
in
this
case
I
already
created
two
sprints
as
part
of
that
iteration.
It's
gonna
create
a
time
box.
You
choose
dates,
let's
say
we're
doing
two
week
sprints.
I
create
that
and
this
step
two
down
here.
If,
if
I
chose
a
date
that
overlapped
with
another
iteration
or
another
sprint,
it
would
throw
an
error,
so
you
can't
do
that.
There's
already
an
iteration,
that's
scheduled
for
this
time.
D
Step
three
is
once
you
begin
assigning
issues
to
that,
whatever
you
name
that
iteration
in
this
case
spirit
one
it's
going
to
show
that
percentage
complete,
how
many
are
open
and
progress
and
completed,
and
then
this
is
just
the
view
at
step.
Four,
on
the
right
of
an
issue.
You
can
now
see
on
the
right
side
that
there's
a
milestone
and
an
iteration
view,
so
you
can
see
that
this
is
part
of
pi1
and
sprint.
1,
maybe
someone's
doing
safe,
and
they
have
project
increments
and
sprints
within
those
pis.
D
D
D
D
D
Jira
is
one
of
the
top
three
integrations
that
are
requested
by
customers.
This
brings
an
additional
option
of
having
jira
integrative
gitlab,
and
I'm
going
to
kind
of
touch
on
that
here.
What
that
really
means,
because
there
are
multiple
options
right
now
of
integrating
with
jira.
This
is
now
another
one.
D
How
it
works
is
you're
going
to
go
to
the
integration
panel
on
the
left,
select
jira,
just
as
you
would,
if
you're
setting
up
that
basic
integration
at
the
very
bottom
of
what,
if
you
have
set
up
this
integration
before
you
will
now
see
that
there's
enabled
your
issues
and
you
need
to
pull
that
project
key
from
what's
found
when
where
it's
found
inside
of
jira.
So
in
this
case
I
had
a
mock
organization.
Health
care
provider
incorporated
hpi
was
the
key
inside
of
atlassian.
D
I
pulled
that
I
added
that
into
gitlab
and
then
it
and
then
it
starts
that
pulling
that
jira
issue
list
in
on
the
left,
you'll
see
in
the
left
panel
that
it'll
change
from
just.
If
you
have
a
basic
integration
setup
of
get
lab,
jira
it'll
now
say
jira
issues.
You
can
view
that
list
and
then
it'll
show
that
list.
D
Like
I
mentioned
a
minute
ago,
you
can
create
a
new
issue
in
jira
which
will
open
up
in
jira,
and
it's
not
creating
an
issue
in
gitlab
and
that's
important
to
know
that
there
is
a
separation
in
there,
so
you're
not
going
to
actually
get
to
create
that
issue
within
gitlab
a
couple
different
things:
resources
the
docs.
There's
a
video
on
how
to
set
this
up
as
well
the
epic
and
then
there's
also
a
a
epic
here
that
if
you
can
provide
feedback,
this
is
something
that
gabe
created.
D
This
is
going
to
get
feedback
on
aligning
basically
what
they've
done
with
the
juror
importer
and
now,
where
there's
this
jira
issue
list-
and
these
are
two
two
things
that
are
being
working
worked
on
separately
and
there's
an
epic
open
to
kind
of
bring
the
two
together
and
gabe
would
appreciate
it
and
me
as
well.
If
you
come
on,
go
to
this
epic
read
over
it
and
then
provide
your
feedback
as
well.
D
You
have
your
basic
gear
integration
that
is
can
be
set
up,
and
then
you
have
the
additional
jira
dev
panel
that
will
show
your
branch
your
commit
and
your
merge
request
within
jira
attached
to
an
issue
there's
also
a
git
lab
for
jira
app.
That
is
cloud
only
for
com.jira
cloud.
This
does
what
basic
jira
integration
and
jira
dev
panel
do
all
in
one,
but
it
is
cloud
only
we
have
jira
import,
which
is
you
can
import
the
ear
issues
from
jira.
D
This
is
something
that's
been
a
big
effort
in
the
last
few
months,
gabe's
leading
this,
and
they
continue
to
roll
out
new
capabilities
around
that
and
13.2.
I
didn't
touch
on
it,
but
you
can
now
map
users
inside
of
this
jira
import
and
then
recently
is
the
jira
issue
list,
which
is
still
separate
at
this
time
from
jira
import.
B
G
G
Why
does
this
specifically
matter?
Just
for
once,
we
want
to
integrate
figma
and
gitlab
even
more,
and
we
also
don't
want
to
like
waste
too
much
time
with
changing
the
browser,
tab
or
changing
the
applications.
It
should
just
work
in
one
go
and
the
other
side
can
rev
you
for
ourselves.
It
also
matters
in
a
way
that
our
design
teams
and
ux
teams
are
using
figma.
G
F
F
I
was
assigned
an
issue
in
which
I
am
required
to
upload
a
design
so
having
this
issue
existed
here
and
the
plugin
from
from
sigma.
What
I
can
do
is
just
right
click,
and
here
in
the
plugins
I
will
see
gitlab
and
if
I
just
right,
click
in
uploading
upload
designs
to
to
gitlab.
I
will
see,
for
example,
that
the
the
issues
that
were
assigned
to
me-
I
can
see
them
from
from
here
from
this
from
this
view.
F
So
in
this
case
this
was
the
issue
that
was
freely
created
here
and
assigned
to
me,
and
I
am
the
designer
so
now
I
can
just
select.
I
can
select,
select
sorry
select
this
one
and
upload
it.
So
in
this
case
this
is
the
magic
of
the
plugin,
because
what
we
are
doing
here
is
that
there
is
a
previous
integration
that
is
provided
by
this
plugin.
And
now,
when
I
come
to
the
to
the
issue,
we
can
see
that
now
it
is
on
in
gitlab
and
I
can
start
collaborating
on
it.
F
So
let's
say
that
I'm
gonna
switch
roles
now.
So
this
is
what
I
sent
from
figma
to
gitlab
and
if
I
were
the
developer
in
this
case
in
in
incognito
or
window-
and
I
say
I
don't
understand,
for
example,
what
type
of
color
is?
Is
this
one?
I
don't
know
a
scale
of
blue,
let's
say,
and
then,
if
I
let's
say
I
comment
on
this
in
a
specific
part
of
the
design
and
as
the
designer
then
I
can.
F
F
Yeah,
so
let's
say
that
when
I
do
this-
and
I
can
collaborate
in
here
and
if
I
am
asked
to
let's
say
change
this-
this
color
to
another
blue
or
orange,
just
as
an
example,
I
the
the
the
way
in
which
I
can
do
this
is
that
I
get
the
feedback
from
fro
from
gitlab
site
and
can
I
can
just
quickly
come
here.
Let's
say
that
I
change.
I
change
the
color
in
this.
F
In
this
view
from
sigma
and
once
I'm
happy
with
my
changes,
I
can
just
redo
again
the
plugin
and
upload
the
designs.
I
I
select
the
the
the
issue.
Sorry,
I
select
the
issue
that
we
were
working
and
once
I'm
done
and
the
design
was
uploaded.
This
is
where
we
will
start
having
here
that
there
will
be
a
version
control
and
I
will
I
will
be
able
to
see
that
there
are
different
versions.
F
So
as
if
you
recall
there
was
one
with
a
blue
button,
and
now
the
latest
was
with
this
change
that
I
that
I
just
made
with
the
orange
one.
So
what
we
are
doing
here
is
that
the
designers
are
first-class
citizens
in
gitlab
that
we
are
fostering
collaboration
in
which
you
can
interact
developer
designer
collect
feedback.
Here
you
can
resolve
the
threads,
have
conversations
around
designs
and
speed
up
any
development
that
requires
input
from
someone
that
is
creating
a
design
to
a
developer,
for
example,
that
is
implementing
this
design.
F
E
F
F
F
It
will
pop
up
asking
you
for
this
personal
token,
so
this
personal
token
will
will
enable
this
integration
and
therefore,
when
you
have
the
issues
assigned
to
your
user,
then
you
can
find
you
can
find
those
issues
from
here
when
you
click
here
and
all
of
this
comes
through
this
integration
cool.
Thank.
F
H
I
H
Is
just
an
example
of
how
to
use
a
jsonet
and
I
will
elaborate
what
is
jsonnet
and
a
little
bit
context?
It
start
from
the
multiple
multi
project,
pi
plan,
or
course
project
pipeline
that
released,
maybe
one
and
a
half
years
year
ago,
which
allows
you
to
trigger
from
one
pipeline.
You
can
trigger
a
course
project
pipeline
to
call
to
a
pipeline
to
another
in
another
project
via
a
bridge
job
and
in
your
you
are
in
your
project
and
in
your
pipeline
graph.
H
It
looks
like
when
you
call
to
a
course
project
pipeline
in
your
pipeline
graph.
You
will
see
the
the
downstream
pipeline,
although
it's
running
all
of
the
jobs
in
other
pipeline.
It
will
look
like
it's
the
same
pipeline,
so
this
was
released
one
and
a
half
years
ago,
and
it
was
called
the
multi
multi
child
pipeline
and
12.
H
In
12.7,
we
released
a
parent
child
pipeline,
which
is
a
again
a
way
to
form
a
pipeline
to
invoke
another
pipeline,
but
the
parent
child
pipeline
is
more
to
invoke
pipeline
in
your
project,
not
in
a
course
project
and
and
for
for
that
you
needed
to
trigger.
There
is
a
bridge
job
and
you
need
to
include
a
path
in
your
repository.
You
have
subfolders
with
the
for
each
child
pipeline.
H
You
need
another
yaml
file,
so
in
advance
you
create
those
subfolders
and
the
yaml
files
and
12.09
released
a
dynamic
child
pipelines,
which
is
another
iteration
on
that
which
you
don't
need
to
in
advance
to
create
those
emails.
You
can
at
run
time
with
the
script,
generate
the
mls
for
the
child
pipelines
and
you
can
call
trigger
pipeline
now.
We
don't
need
to
give
include
path.
You
can
include
artifact,
so
this
is
the
new
thing
that
released
on
12.9
the
the
challenge
with
that
or
the
difficulty
with.
H
Okay,
so
so
so
this
is
a.
What
released
on.
13.2
is
just
an
example,
so
why
why?
Why
does
it
matter
to
generate
a
pipeline
at
one
time
and
in
child
parenthood
pipeline?
So,
first
of
all
for
monorepos,
large
reapers
that
which
modern
ripples
become
very
popular
recently
and
in
monarch
it's
avoid
long
and
complex
pipeline.
You
have
for
each
model,
you
have
its
own
pipeline
and
one
parent
pipeline
for
the
entire
project.
But
this
way
it's
much
more
easy
to
manage
and
debug.
H
Another
great
use
case
is
to
build
a
matrix
of
target
or,
as
we
call
the
build
matrix,
and
for
that
I
will
have
a
I.
You
can
implement
a
matrix
build
and
I
will
have
a
demo
live
demo
for
that
and
and
the
the
last
reason
for
that
is
to
reduce
a
boilerplate
and
repetition
relating
to
the
right
script
that
generates
yaml
instead
of
hand
typing
and
typing
it
at
all.
H
H
From
this
is
my
project
and
then
I
will
start
from
the
yaml
file,
and
I
have
here
two
jobs.
This
is
the
third
job,
jsonnet
call
it
and
it
used
the
alpine
image
and
in
the
script
we
download
jsonnet
and
then,
when
we
have
the
jsonnet,
we
call
the
json
script
that
I
created.
I
will
show
you
and
the
output
of
running
of
this
jsonnet.
It
will
generate
the
cml
and
I
will
store
it
in
the
artifact.
H
H
H
H
I
I
wrote
this
a
three-dimensional
loop
that
it
will
run
and
create
a
job
for
me,
and
this
will
be
the
job
name
and
it
will
call
this
function
with
the
parameters
and
the
function
will
create
a
job
and
each
job
will
be
do
the
same.
We'll
use
this
image
we'll
run
this
script.
So
it's
very
simple,
and
now
I
will
show
you
how
it
looks
like
so
I
will
run
the
pipeline.
H
And
this
is
all
of
the
jobs
that
is
created
there
for
each
combination,
android
with
home
a
android
home
b
and
with
home
c
under
the
firefox,
a
pc.
So
I
have
here
it
helped
me
to
generate
all
of
this
and
of
course
now,
if
I
go
back
to
the
pipeline,
it
also
run
it.
So
I
go
back
to
the
pipeline
and
this
is
the
trigger
job,
and
this
is
the
downstream
project
the
child
pipeline.
H
So
this
is
it
how
you
can
implement
build
matrix
for
complex
environments
that
you
have
to
test
you
don't
ever
need
it.
No
more!
They
need
to
write
everything
in
in
the
ml.
You
can
have
script,
json
script,
all
other
languages.
You
draw
other
languages
like
jsonnet
that
you
can
use
to
create
on
runtime
your
yaml,
so
going
back
to
the
slides,
and
if
you
want
some
resources
here
are
the
resources
and
questions.
I
H
You're
right
totally
right,
the
gesture
net
is
just.
There
is
no
any
relationship
between
gitlab
and
json.
It
is
just
an
example,
and,
as
I
said,
there
is
other
languages
like
similar
to
json
and
that
you
can
use,
and
the
only
relation
is
the
relation
is
that
now
out
of
the
box,
we
have
a
project
template
that
uses
json
out
of
the
box.
So
if
you
go.
H
Yeah,
so
if
I
go
here
to
the,
let
me
show
you
on
this
template
but,
as
I
said,
it's
not
you
see
jsonnet
for
dynamic
pipeline
and
let's
do
preview,
it's
it's
similar
to
my,
but
it's
a
very
simple.
I
this
is
the
template
that
exists.
It
just
created
two
jobs.
I
added
some
logic
to
show
to
implement
the
build
metrics.
H
But
again
it's
it's
a
the
only
thing
that
gitlab
brings
here
is
the
way
to
trigger
a
child
pipeline
with
the
an
artifact
versus
what
was
before
that
you
needed
to
define
a
path
for
that.
So
this
is
the
new
thing
which
is
powerful,
because
now
you
can
or
you,
if
you
want
to
you
to
write
your
own
script
or
you
want
to
use
languages
like
like
jsonnet.
B
C
C
Okay,
perfect
all
right,
so
let
me
present
and
okay-
I
don't
know,
what's
going
on
there,
but
okay,
so
just
to
give
a
little
bit
of
information
on
container
host
monitoring
and
blocking
there's
two
tools
that
we
use
for
this.
We
use
falco
and
we
use
app
armor
falco
is
for
monitoring
and
app.
Armor
is
for
blocking
and
essentially
what
these
tools
do.
C
Is
they
monitor
the
linux
kernel
and
look
for
certain
system
calls,
and
then
they
assert
those
calls
against
the
rules
engine
and
if
those
calls
meet
the
rules,
then
we
can
go
ahead
and
send
different
alerts
to
different
applications
and
different
endpoints.
And
what
this
does
is.
It
helps
us
add
any
additional
logic
to
be
able
to
handle
whenever
an
event
has
occurred,
so
pretty
much.
C
C
That's
unaffected
so
there's
a
lot
of
reasons
to
use
this
and
then
there's
blocking
which
what
it's
we're
still
monitoring.
Containers
for
different
system
calls,
for
example,
writing
a
file
or
accessing
the
network,
and
we
can
block
that
process
from
taking
effect.
So
essentially,
the
user
will
get
a
permission
denied
and
then
number
two.
We
can
implement
it
in
a
pod
security
policy,
where
pods
won't
even
be
able
to
run
on
the
system
if
they're
performing
a
certain
system
call.
C
So
let
me
show
you
some
a
few
examples
here,
so
I've
put
together.
This
is
a
sample
rule
within
falco
and
what
this
rule
does
is
if
it
detects
bash
being
run
within
a
container
it'll
output.
Shell,
spawned
in
a
container
other
than
entry
point,
so
it'll
show
you
that
someone
is
in
a
container
and
they're
running
they're
running
a
shell
script,
meaning
that
this
is
something
that
shouldn't
be
done.
C
The
second
example
that
I'm
going
to
show
you
is
host
blocking,
so
what
we
do
here
is
we
create
a
profile
within
app
armor
and
I'm
going
to
show
you
how
this
is
done
after
this,
after
showing
this.
But
what
you
do
essentially
is
create
a
profile
using
app
armor
rules,
and
this
profile
is
going
to
say
that
we're
going
to
deny
any
file
rights
within
the
containers.
C
C
So
this
is
how
you
would
deploy
the
actual
pod.
It
can
be
done
in
a
deployment.
Typically,
this
is
just
a
simple
pod
creation
where
it
creates
a
pod,
and
then
it
runs
hello,
app,
armor
and
just
runs
a
command
and
then
we'll
create
that
pod.
Now
this
image
that
didn't
show
was
just
an
image
of
a
pod,
but
I
don't
know
why
slides
is
acting
up
so
once
that's
created
and
assigned
the
app
armor
profile
that
we
created
up
up
here.
What
it'll
do
is
anytime.
C
C
So
why
does
any
of
this
even
matter
so
there's
a
few
reasons
why
it
matters
to
customers,
and
the
reasons
are
that
they
can
take
action
on
any
possible
malicious
activity
within
their
system,
or
maybe
it's
something
that
users
are
doing
and
they
can
go
ahead
and
change
their
security
policy
to
suit
their
needs.
They
can
see
like
hey
all
these.
These
permissions
are
commonly
being
run.
Maybe
we
should,
you
know,
expect
this
and
lacks
our
security
policy,
or
these
things
are
never
really
being
run,
we're
alerting
on
it.
C
Security
teams
can
be
alerted,
there's,
there's
lots
of
possibilities
for
using
container
host
monitoring
container
hosts
blocking
you
can
block
processes
and
prevent
intrusion
and
malicious
activity
within
the
containers.
So
if
you
want,
you
know
that
something's
really
bad
and
our
security
policy
says
hey.
This
container
is
a
critical
application
container
and
there
shouldn't
be
any
developers
directly
accessing
this
production
environment,
then
through
bash.
They
should
be
accessing
accessing
it
through
an
external
source.
C
So
then
what
will
happen
there
is
that
we
can
limit
that
and
we
can
prevent
that
from
happening
and
then
how
does?
How
does
git
lab
you
know?
These
are
just
tools
that
someone
can
just
their
open
source
tools,
falco
and
app
armor
that
anyone
can
implement.
But
the
thing
is
that
they're
not
easy
to
implement
into
your
system.
It
takes
some
time
to
add
them
to
your
deployment
and
what
gitlab
does
is
it
makes
it
easy.
You
just
add
the
deployments
to
a
yaml
file
and
then
it'll
go
ahead
and
deploy
app.
C
C
C
Pod
security
policies
were
not
even
letting
the
pod
run
on
the
system
if
certain
criteria
is
not
met,
so
you
can
go
and
look
at
that.
I
don't
have
time
to
show
that
in
depth,
but
I'm
left
some
resources
there
for
y'all
to
look
at
after
this
session
and
just
to
show
you
how
easy
it
is
to
add
these
tools
within
the
gitlab
managed
apps.
C
C
Then,
if
you
want
to
configure
them,
for
example,
you
want
to
add
rules
to
app
armor,
you
can
go
ahead
and
add
a
profile
and
each
has
its
specific
syntax.
This
is
just
helm
values,
so
there's
specific
syntax
to
each
one.
So
you'll
have
to
dig
in
and
see
exactly
how
you
want
to
set
up
your
system,
but
this
is
an
example
of
denying
file
rights
so
to
create
a
profile
named
profile,
one
and
not
allow
far
rights
within
the
container
system.
C
So
and
that's
as
simple
as
it
is,
and
if
you
want
to
apply
it
to
your
to
your
pods
when
they're
deployed
what
you
can
do
is
you
can
edit
your
helm,
template
and
then
all
you
need
to
do
is
add
this
annotation
saying
that
any
pod
named
hello,
which
this
is
or
any
container
names
hello.
This
is
a
container
named
hello,
it's
gonna
run
with
profile,
one
meaning.
C
C
Is
set
as
a
cluster
management
project,
so
you
can
go
ahead
and
look
at
simply
simple
notes
and
see
how
it's
configured
and
then
play
around
with
it
yourself
and
if
you
have,
if
you
want
another
session
that
goes
into
live
demo,
examples
and
and
showcases
these
features
live
I'd
be
happy
to
do
that,
just
for
the
sake
of
time.
Yeah!
That's
that's
where
it
is
and
I'd
be
happy
to
answer
any
questions.
B
A
J
J
J
This
command
is
is
a
convenient
way
to
check
whether
the
execution
plan
for
a
set
of
changes
matches
your
expectations,
and
this
is,
you
know,
you're
supposed
to
run
terraform
plan
before
committing
any
changes
to
version
control.
So
in
our
case
a
merge
request
is
the
place
to
run
the
terraform
plan
command.
J
J
J
J
So
why
does
it
matter
for
customers
and
prospects?
You
know
customers
when
they're
managing
infrastructures
code,
you
know,
usually
they
have
many
environments.
You
know
staging
production,
for
example,
with
this
new
feature,
they
can
now
review
what
infrastructure
changes
will
take
place
across
multiple
environments
in
a
merge
request,
and
obviously
this
will
lower
the
risk
of
introducing
erroneous
infrastructure
configurations
into
production,
diminishing
risk
and
eliminated
unexpected
down
times.
What
is
it,
what
is
what's
in
it
for
us,
this
new
feature
helps
us
better
to
better
position.
Our
integration
points
with
terraform.
J
So,
let's
go
to
the
demo
real
quick.
I
have
six
minutes
so
I've
put
together
a
project.
I've
provided
a
link
to
this
project
in
the
presentation,
so
you
can,
you
have
access
to
it
and
I've
documented
it.
The
other
thing
you
know
with
the
variables
that
you
need
to
to
define
enable
in
order
to
be
able
to
execute
this
project,
basically
just
quickly.
This
project
contains
a
directory
per
environment.
In
this
case,
the
assumption
is,
there
is
a
staging
environment.
J
J
You
know
and
you
get
to
deploy
an
instance
per
environment.
So
let's
see
quickly
to
get
this
working
within
this
environment,
we
can
quickly
just
create
an
issue.
So
we'll
just
call
this
and
the
debug
statements
from
I
just
let's
just
call
it
that
and
then
we're
going
to
I'll,
assign
that
to
myself
and
then
we'll
go
into
that
issue,
we'll
create
the
mr.
J
J
J
J
J
The
next
okay,
so
I
put
some
slides
here
with
the
steps
that
I
just
showed
you
once
the
pipeline
completes,
you
will
get
the
the
last
stage
to
actually
deploy.
Do
the
terraform
apply
and
deploy
the
instantiate
the
machines
on
ec2
for
learning
more
about
this.
Here's
the
link
that
this
demo
project,
this
here's
a
link
to
the
project
you
just
show
you
just
saw
there's
also
three
other
projects
that
I
found
that
were
very
interesting
and
I'm
sharing
the
links
to
them
here.
J
J
J
So
what
does
it
matter
for
customers?
You
know
developers
are
able
to
run
our
terraform
plan
to
see
infrastructure
configuration
changes
and
developers.
Our
github
stakeholders
can
effectively
collaborate
on
infrastructure,
configuration
updates
and
for
us
again
like
before
it
enriches
our
infrastructure's
code
story
and
it
enhances
our
github's
positioning
of
taking
devops
best
practices
to
infrastructure
automation.