►
From YouTube: Terraform State Changed diff - Design review with Matt
Description
Reviewing the first design of the Terraform State Changes tab with the team's BE engineer Matt Kasa. The review is focused on 3 problems: data grouping, display and interactions, information design and display and UI design choices, such as the design components, interaction patterns, iconography and colour use.
A
A
We
could
group
the
items
by
created,
updated
deleted
or
we
could
show
all
the
individual
resources
and
then
indicate
whether
they
have
been
updated,
created,
updated
or
deleted.
I'll.
Give
you
more
context
while
showing
this
is
problem
number
one
and
problem
number
two
is:
how
do
we
show
the
diff,
the
actual
diff
just
for
reference
for
the
team?
We've
been
having
a
discussion
in
the
issue
where
you
did
an
initial
poc
of
how
the
diffs
would
be
shown.
B
Right
so
this
would
be
more
of
a
line-by-line
diff
and
the
problem
I
really
found
with
it.
Was
it's
really
difficult
to
know
what
resource
this
change
is
actually
occurring
to,
because
you
don't
really
get
enough
context
lines
to
see
the
name
of
the
resource?
You
have
the
the
number
of
the
resource
in
the
in
the
state
file
like
the
index
in
the
array,
but
you
don't
have
the
name.
The
name
is
a
little
bit
higher
up.
B
A
And
the
primary
the
primary
use
case,
at
least
when
I
spoke
to
users-
was
that
they
want
to
see
changes.
Well,
they
want
to
see
for
specific
resources,
so
they
either
want
to
find
a
specific
resource
first
and
then
see
the
changes
or
types
of
resources.
So
it's
really
important
for
them
to
see.
So.
Your
second
suggestion
was
to
group
by
type
of
change
and
then
resource
name,
somehow
parse
it
from
the
file,
and
then
these
would
be
the
changes.
A
B
No,
so
I
was
kind
of
trying
to
stick
with
the
kind
of
the
diff
output
of
plus
means
it's
being
added
and
minus
means
it's
being
deleted
yeah.
So
this
was
intended
to
be
more
of
a
diffu.
I
just
kind
of
did
this
in
the
markdown
in
the
in
the
issue.
Comment.
We'd
probably
want
to
have
the
styling
to
be
more,
like
I
guess,
like
a
code
snippet
or
or
like
the
diff
view
on
mr,
but
you
would
just
have
a
rather
than
having
the
diff
view
split
out
by
file.
B
The
file
would
be
the
like.
The
file
name
would
be
the
resource
type
and
name,
and
then
we
could
like.
We
could
optionally
group
them
under
the
created,
updated
deleted,
I'm
not
sure
if
it's
it
might
be
sufficient
to
just
see
that
everything
about
a
resource
is
new
and
to
know
that
it's
being
created,
you
know
we,
we
kind
of
show
that,
with
in
the
in
the
mrdif
view
of
files,
we
kind
of
show
you
when
a
file
is
being
completely
added
or
completely
deleted.
B
B
B
B
A
A
A
A
A
B
A
A
A
A
A
One
is
to
I
have
not
applied
filtering
here
yet,
but
it
would
have
some
filtering
to
group
all
the
created
to
under
an
expandable
component,
and
then
you
would
see
the
resource
name
and
what
changed
resource
name
and
one
changed,
and
then
the
same
here.
But
I
wanted
to
speak
about
this
version
more,
so
this
is
kind
of
using
the
diff
of
vmr,
where
you
see
all
the
lines
of
code.
Basically,
you
see
only
the
changed
lines.
I
think
this
is
a
better
example.
A
A
B
B
Like
it's
not
something
that
I
have
control
over,
so
I
can't
really
affect
the
order,
since
terraform
is
the
one
that
serializes
to
json
so
like
I,
I,
as
a
user,
really
never
interact
with
that,
it's
useful
for
me
to
be
able
to
like
get
the
whole
json
raw.
Potentially
I
want
a
script.
You
know,
use
a
script
to
parse
it
or
do
something.
A
B
B
A
Yeah,
so
the
difference
is
in
the
first
one
and
the
second
one
the
resource
is
on
top
and
then
you
filter
by
created,
updated
and
deleted
in
the
third.
The
difference
is
that
you
view
them
grouped
by
type
of
change
here,
but
all
the
resources
that
belong
in
that
type
of
group.
This
could
be
expandable
and
collapsible
as
well
the
resource,
but
it's
like
two
levels
of
indentation
rather
than
filtering.
A
B
So
I
wonder
if
that's
maybe
like,
I
know
that
that's
kind
of
what
I
wanted
initially,
but
I'm
wondering
if
maybe
that's
not
the
right,
maybe
that's
too
much
like
indirection
before
you
get
to
the
information.
So
I
wonder,
if
is
it
your
first
one
that
they
they're
treated
like
files
more
yeah
this
one
so.
B
B
B
B
B
A
A
B
B
A
A
A
A
A
B
B
A
A
A
A
A
You
said
already
that
you
probably
don't
really
care
about
the
things
that
proceeded
and
follow
the
change,
and
you
don't
really
care
where
you
are
in
the
state
so
yeah
and
that's
why
you
proposed
this.
Actually
that
I
only
care
about
these
things
that
I
have
configured
for
this
new
resource
and
were
implemented.
B
B
B
A
A
A
A
A
B
B
A
A
A
A
A
A
A
A
A
B
A
B
B
Icon
wise,
it's,
it
would
be
a
nice
to
have
it's
probably
a
lot
to
implement
for
nice
to
have,
but
I
would
still
like
to
have
it
it's
just
like,
like
you
said
just
if
we
could
classify
changes
by
type
or
by
provider,
I
think
that
would
be
nice.
I
know
that
we
have
a
you
know.
We
display
a
little.
You
know
a
little
whale
icon
for
a
docker
file.
We
display
a
little
tanooki
for
get
lab,
ci
ammo,
so
we
kind
of
have
a
not
to
say
a.