►
Description
Looking for part 2 of this demo?
https://youtu.be/GN8HhGbliw8
What is Ansible?
Ansible is an amazingly flexible tool to manage your infrastructure. It's a simple IT automation engine that automates cloud provisioning, configuration management, application deployment, intra-service orchestration, and many other IT needs. Ansible allows you configure and manage many computers at once, with ease.
If you have never touched Ansible, fear not, because this two part video series covers all the major pieces of Ansible. This first video is an intro that will cover how to get started and what are the important pieces to understand. Part 2 covers more of the advanced features and customized code you can create for Ansible.
Our guest speaker for this talk is Jeremy Murrah, a sysadmin who uses Ansible daily to configure and maintain hundreds of nodes for his employer. Jeremy skillfully shows off the basic features of Ansible, how they work and then highlights some useful modules to extend Ansible even further.
If you like this content, be sure to join RTPSUG in person!
The Research Triangle PowerShell Users Group (RTPSUG) is the largest PowerShell group in the world! We meet twice a month to discuss all topics related to PowerShell and automation. Our topics cover beginner to advanced concepts and offer people a chance to learn new skills and ask questions. Our mission is to create a space for all attendees to feel welcome, have a chance to ask questions and be part of a community.
For more information on our group, please visit any of following links:
WEB: https://rtpsug.com
MEETUP: https://www.meetup.com/Research-Triangle-PowerShell-Users-Group
LINKEDIN: https://www.linkedin.com/company/rtpsug/
TWITTER: https://twitter.com/rtpsug
GITHUB: https://github.com/rtpsug
A
Hey
everybody
thanks
for
joining
us
tonight.
This
is
another
meeting
of
the
research
triangle:
powershell
users
group.
My
name
is
mike
canakis
and
on
behalf
of
myself
and
phil
bossman
we'd
like
to
welcome
you
all
here
this
evening.
Tonight
we're
going
to
be
talking
about
ansible
with
mr
jeremy
mara.
So,
let's
get
to
it.
First
I'd
like
to
introduce
our
speaker
for
tonight:
hey.
A
B
So
I've
been
a
a
strictly
windows
sysadmin
for
almost
as
long
as
there's
been
windows,
and
I
had
a
coworker
of
mine
who
was
a
strict
linux
admin.
You
know
during
the
os
wars
when
we
didn't
talk,
and
we
would
you
know,
throw
throw
stuff
over
the
over
the
wall
at
each
other
and
we
started
talking
and
he
kept
trying
to
tell
me
about
this
thing
called
ansible
for
a
long
time.
Really.
You
know
when
I
was.
I
was
actually
already
starting
to
do
configuration
management
with
dsc.
B
You
know
keeping
it
keeping
it
windows,
keeping
the
powershell
keeping
true
to
my
roots
and
he
kept
being
like
hey
man,
come
check
this
out
and
he
he'd
bring
me
over
his
desk
and
he'd
open
up
his
little
linux
terminal
with
his
80
characters
and
he'd.
You
know,
vi
a
file
and
he's
like
check
this
man,
I'm
not
looking
at
that.
I
don't
know
what
you're
trying
to
show
me.
B
Yeah,
so
I
you
know,
I
don't
even
remember
he's
something
he
said
because
he
he
was
persistent,
something
he
said
clicked
for
me
and,
and
I
started
started
messing
with
ansible
in
it,
and
it
was
just
like
a
like
a
light
bulb
like
as
soon
as
it
hit,
and
I
just
ran
with
it,
because
ansible
is
one
of
its
great
things.
It's
so
accessible
once
you
kind
of
get
going
with
it.
B
B
B
A
B
B
Windows
yeah,
I'm
I'm
strictly
doing
windows
and
trying
to
get
into
mostly
lately
I've
just
kind
of
been
evangelizing
automation,
be
ansible
to
the
rest
of
the
company
trying
to
drag
us
out
of
the
dark
ages,
but
yeah.
I
still
do
strictly
windows.
So
most
of
this
talk
is
kind
of
from
a
windows
bent
a
lot
of
it
applies
to
either
direction,
but
most
of
the
stuff
that's
specific
to
one
or
the
other
is
going
to
be
from
a
windows
angle.
So
in
this.
C
A
So
I
know
you
have
a
a
ton
of
information
you
want
to
share
tonight.
I
want
to
let
you
get
into
that.
I
just
wanted
to
ask
before
you
get
to
that
someone
who's
thinking
about
ansible
like
what
are
some
good
skill
sets
to
sort
of
have
some
mastery
over
to
work
with
ansible.
Like
can
you
jump
from
like
just
a
help,
just
job
to
like
an
automation,
tool
and
ansible,
or
do
you
need
some
like
core
skill
sets
to
work
with.
B
I
would
say
that
you
need
enough
experience
to
know
why
you
would
want
to
use
it
because
it
solves
a
set
of
problems
that
you
have
to
like
understand
the
problem
before
you
can
kind
of
grock
the
answer
you
know
just
from
a
higher
architectural
sort
of
concept,
but
as
far
as
the
specific
requirements,
I
mean
it's
all
yaml
and
json
and
and
text
parsing
it
it's
strength,
is
that
it
doesn't
require
a
lot
of
previous
programming.
You
know
cool
cool.
A
Well,
I
know
you
have
a
ton
of
information
I
want
to
let
you
get
at
it,
so
we're
going
to
turn
the
floor
over
to
you
and
we
want
to
say
you
know
thanks
for
spending
some
time
with
us
tonight
and
looking
forward
to
this.
So,
ladies
and
gentlemen,
please
welcome
jeremy
and
it's
the
show
is
yours,
mr
all,
right
let
me.
B
C
B
Together,
this
was
actually
something
I
put
together
last
year.
The
reason
I
did
this
was
I
mentioned.
You
know
I
come
to
this
from
a
windows
background
and
there's
a
lot
of
benefits
to
it.
I
was
talking
to
my
my
linux
admin
cohorts
who
have
been
using
it
for
a
bunch
of
stuff
and
and
a
lot
of
the
when
I
started
digging
into
it
and
researching
it
and
googling
finding
information
about
it.
There
was
so
much
about
ansible
from
a
linux
perspective
or
from
like
a
networking
perspective.
B
So
I
thought
that
I
would
put
something
together
that
kind
of
addressed
that
so
my
goal
being
to
try
to
get
more
windows,
people
to
at
least
you
know
not
discount
it
offhand
at
least
look
at
it
and
evaluate
it
as
as
as
a
relevant
product.
So
that
is
what
I
wanted
to
do
this
from.
So
I
will
start
with
the
basics
of
what
ansible
is.
In
my
order
of
important
preference,
ansible
is
agentless,
there's
nothing
to
install
on
your
system.
B
That
was
a
big.
That
was
a
big
selling
point
for
me.
The
the
sort
of
theme
here
with
ansible
for
me
anyway,
is
accessibility
right
everything
with
ansible.
It's
very
easy,
not
to
say
easy
right.
I
don't
like
it
work,
because
everything
we
do
is
hard.
That's
why
we
get
paid
to
do
it,
but
it's
very
accessible.
There's
not
a
lot
of
pre
knowledge
to
get
going,
and
the
agentless
part
is
a
lot
of
that.
B
B
That
is
familiar
with
your
language
of
choice.
To
read.
It
is
for
better
or
for
worse
with
the
use
of
yaml,
very
human
readable.
So
someone
who
doesn't
necessarily
know
the
intricacies
of
ansible
can
look
at
what
you're
doing
and
probably
have
a
pretty
good
idea
of
what's
going
on,
and
that
can
be
helpful.
I
like
to
think
of
it
like
the
boss
test
right,
your
boss
can
come
up
and
look
at
what
you're
doing
and
kind
of
have
a
potentially
have
a
good
idea
of
what
you're
doing.
B
That's
very
useful
and
it's
agentless,
so
this
is
super
important,
which
is
why
I
listed
it
twice.
The
larger
your
environment,
you
know.
For
me,
a
lot
of
stuff
that
I
looked
at
was
a
no
go
and
I
thought
oh,
I
want
to
evaluate
this
product,
but
I've
got
to
install
an
agent
on
you
know:
4
000
servers
and
go
through
months
of
change,
approval
boards
and
and
fighting
with
people
to
get
that
done
so
not
having
to
deal
with
that
kind
of
helps,
ease
the
transition
and
along
those
lines.
B
That
same
sort
of
theme
of
accessibility
is
that
it's
serverless
not
in
the
fancy
buzzword
cloud
serverless
way,
but
in
that
there
is
no
sort
of
central
management
master
server
that
you
have
to
sort
of
spend
a
bunch
of
time
building
infrastructure.
In
order
to
run
it
you
can
it,
you
can
run
it
from
anywhere
right.
So
it's
a
linux
program
and
with
python
scripts.
So
anywhere
you
can
install
linux.
You
can
run
anywhere
that
you're
on
your
network
and
you
can
connect
to
your
machines.
You
can
run
it
and
that's
really
nice.
B
B
There's
a
lot
of
reasons
probably,
but
I
so
I
thought
I
would
write
down
a
few
that
I
had.
These
are
sort
of
my
reasons
for
ignoring
it
for
a
long
time
when
I
had
my
linux
buddy
kind
of
telling
me
about
it,
so
the
first
one
is
the
the
perception
that
it's
just
for
limits-
and
this
say
two
three
years
ago,
was
kind
of
when
I
first
started
messing
with
this,
and
that
was
almost
valid.
It
was
very
difficult
to
do
things
with
windows
as
compared
to
now.
B
So,
if
you
looked
at
this,
you
know
a
while
back
and
decided
this
wasn't
a
fit
for.
You
there's
been
a
lot
of
improvements
over
the
last
several
versions.
I
think
I
started
using
this
around
version
2.2
and
it's
a
210
now
so
there's
been
a
huge
increase
in
a
lot
of
work
done
around
around
windows,
integration
and
sort
of
easing
that
that
work
and
in
that
environment.
So.
B
I
knew
powershell,
which
is
why
I
used
dsc,
because
dse
was
in
powershell,
and
so
I
had
the
impression
that
you
know
ansible
was
written
in
python,
so
I
needed
to
know
python,
and
that
is
not
the
case.
In
fact,
I
still
don't
know
python
and
I'm
like
four
years
into
this
sneaking
thing,
and
I
I
still
don't
haven't
learned
any
python.
Well,
I
mean
I
can
read
it.
You
know
I
can
read
a
script
here
there,
but
it
is
not
a
requirement.
It's
probably
helpful
for
some
of
the
more
advanced
things.
B
If
you
start
writing
some
really
advanced
customization,
it
would
certainly
be
helpful,
but
as
far
as
basic
use
for
95
of
the
product,
let's
say
you
don't
need
to
know
python.
So
don't
let
that
stop
you
now.
If
you
want
to
go,
learn
python,
you
know,
that's
probably
a
good
idea,
more
languages,
you
know
the
better,
but
it's
not
a
requirement
by
any
means
so
and
the
other
big
one
for
me
was
like
I
mentioned.
B
I
was
already
using
dsc,
so
I
had
I
had
this
huge
investment
over
my
career
in
windows
and
powershell
and
dsc.
So
at
that
point,
what
was
the
benefit
to
me
in
throwing
all
that
away
and
starting
over
on
this
entirely
new
branch
down
this
new
technology,
but
it
turns
out,
there
is
not
a
need
to
throw
any
of
that
away.
B
Your
powershell
knowledge
is
still
valuable
when
using
ansible
your
dsc
knowledge
is
still
valuable
when
using
ansel.
In
fact,
they
they
have
a
great
interplay,
the
interaction
between
dsc
and
ansible.
They
really
sort
of
focus
on
on
their
strengths
right,
so
the
things
that
dsc
are
good
at.
It's
still
good
at
the
things
that
dsc
isn't
so
great
at
ansible's,
really
good
at
so
they
they
work
really
well
together.
So
if,
if
you're
in
that
boat
and
you've
invested
a
lot
of
time
in
that
technology,
don't
think
you
need
to
you're
starting
over.
B
You
know
what
I
mean
and
then
so
this
is
valid,
and
this
is
still
real
case.
Sensitive
programming
is
hard
and
if
you're
like
me-
and
you
have
decades
of
bad
bad
habits
around
it,
not
mattering
it
matters
now,
but
it
matters
for
everything
now
right,
the
whole
os
wars
are
over
and
I
don't
know
that
anybody
won.
So
everything
is
sort
of
intermingled
and
cross-platform
and
case
sensitivity.
B
The
terms
that
people
use
are
important
to
understand
so
just
to
kind
of
do
a
quick
rundown
of
this
a
task
so
that's
sort
of
the
immutable
unit
within
of
execution
within
it
within
within
ansible.
So
a
task
is
sort
of
the
instructions
for
what
you're
going
to
run
right
so
whether
that
task
me
to
install
a
piece
of
software
or
make
a
registry
change
or
copy
a
file.
The
task
is
sort
of
that
and
we'll
get
into
in
the
demo
kind
of
talking
about
a
lot
of
the
specifics.
B
Of
those
a
play
is
the
terminology
that
ansible
uses
when
they,
when
you
combine
a
sequence
of
tasks
with
a
set
of
machines
to
run
those
tasks
against,
and
this
is
all
in
the
declarative
format
right.
So
you
have
a
list
of
tasks
that
describe
your
environment
and
then
you
have
a
set
of
hosts
that
you
want
to
execute
that
upon
a
play
is
sort
of
that
combination.
B
B
Rarely
do
you
run
a
task
on
its
own.
It's
generally,
a
playbook
is
sort
of
the
the
thing
you
fire
off.
It's
the
file.
You
interact
with
it's
what
you
execute.
It's
sort
of
your
encapsulation
of
your
entire
intent
when
you're
running
things
so
within
that
I
mentioned
hosts
as
being
part
of
a
play.
So
interchangeable
terms
you
have
hosts
and
inventory,
and
those
are
those
are
really
just
two
aliases
for
the
same
same
thing:
they're
used
interchangeably,
that's
basically
just
a
file,
a
text
file,
because
again
this
is
linux,
so
everything's
a
file
right.
B
So
this
is
just
a
file
with
a
list
of
machines
in
it,
and
this
is
we'll
see
in
the
demo
here
when
we
get
into
it.
This
is
typically
in
an
ini
file
format,
so
any
of
you
old
dogs
that
messed
with
windows
pre-95
way
back
in
the
day,
you
might
be
familiar
with
ini
files,
it's
that
format
for
organizing
hosts
and
putting
them
in
groups
and
relating
those
groups
to
other
groups,
and
it
can
be
as
simple
or
you
know
advanced
as
you
want
it
to
be.
B
The
next
sort
of
set
of
terms
are
vars
variables,
vars
a
lot
of
times.
They
call
it
or
facts.
Vars
and
facts
are
basically
the
same
thing.
Those
are
just
variables
and
they're
used
for
different.
There
might
be
a
subtle
nuance
in
how
people
use
those,
but
those
are
basically
the
same
thing
those
can
be
stored
in
a
file.
Those
can
be
retrieved
from
a
host.
Those
can
be
input
at
runtime.
There's
a
there's,
a
ton
of
ways
to
interact
with
this,
but
that's
what
that
means.
B
That
just
means
a
piece
of
data
stored
in
a
variable.
These
last
two
are
not
strictly
ansible.
But
for
me,
when
I
first
started
messing
with
ansible
was
my
first
introduction
to
json
and
yaml.
I
had
been
doing
powershell,
so
everything
was
just
powershell
and
powershell
data
files
and
powershell
script
files.
So
I
was
very
confused
by
the
term
by
lists
and
dictionaries
like
what
are
those
so
if
you're
familiar
a
list
is
just
an
array,
it's
just
a
grouping
of
multiple
items
of
any
kind.
B
It's
just
a
set
of
key
value
pairs,
so
it's
really
comparable
to
like
a
hash
table
in
in
in
powershell.
It's
the
simplest
term
right
you're,
a
powershell
object
with
all
with
all
the
stuff
taken
off.
So
it's
just
key
value
pairs,
so
lists
can
be
comprised
of
multiple
dictionaries.
A
dictionary
can
have
a
list
in
it.
So
but
that's
what
those
terms
mean.
So
that's
just
sort
of
data
structures
for
for
json
and
yaml.
B
So
let's
talk
about
yaml,
because
the
ammo
is
our
sort
of
primary
interface
into
ansible.
A
lot
of
the
stuff
we're
going
to
write
is
yaml,
and
so
the
internet
suggests
that
one
of
the
things
yaml
stands
for
is
a
yamalaina
markup
language,
which
is
that's
my
favorite
term,
and
I
like
that,
because
yemeline
a
programming
language
either,
which
is
important
to
remember,
but
it's
close,
so
ansible
basically
took
yemel
added
a
bunch
of
extra
features
on
top
of
it
and
got
it
pretty
close
to
an
actual
programming
language
you
can
set.
B
You
can
input
data,
you
can
retrieve
data
back,
you
can
store
it
in
a
variable.
You
can
do
loops,
you
can
do
conditionals.
You
can
make
decision
logic
about
when
to
run
certain
things.
So
if
you
combine
all
those
together,
you
almost
have
a
programming
language,
but
you
can
see
from
this
little
embedded
image.
I
have
here
the
you
can
get
away
from
the
primary
tenet
of
being
human
readable
in
a
hurry.
B
So
I
won't
give
a
lot
of
best
practices
here,
because
that's
you
know
not
really
something
I
do,
but
I
would
say,
try
to
avoid
doing
a
lot
of
really
complex,
yaml
programming
in
the
same
way
that
you
would
avoid
what
they
call
powershell
golf
right
like
yeah,
you
can
write
a
script,
that's
as
short
as
possible
and
completely
unreadable,
but
that's
usually
not
the
goal
right,
a
powershell.
You
want
things
to
be
readable.
Six
months
from
now
at
two
am
same
kind
of
thing
with
with
ansible,
you
want
it
to
be
readable.
B
B
That
is
an
executable
that
you
run
on
your
linux
machine
where
ansible
is
installed
and
you
give
it
potentially
a
sequence
of
options
at
the
very
most
at
the
most
basic
level,
you
give
it
a
playbook
to
run
so
your
big
yaml
file
that
you've
you've
created
with
all
your
hosts
and
your
tasks,
you
give
it
that
file
to
run
and
there's
options.
We
have
a
couple
listed
here.
You
can
specify
verbosity
levels.
B
You
can
do
things
which
is
really
helpful.
Like
step
say,
you
know,
walk
through
each
task,
one
at
a
time
and
and
prompt
if
you
want
to
run
the
next
task,
because
that's
very
handy
but
there's
things
like
the
the
check
mode,
which
is
kind
of
like
the.
What,
if,
in
powershell,
which
is
the
idea
of
run
this
playbook,
don't
actually
change
change,
anything
to
sort
of
tell
me
what
you
would
do
and
there's
a
lot
of
other
options
here.
Extra
vars
is
a
way
to
pat
one
of
those
from
the
slide
before.
B
A
B
What
we're
going
to
run
and
we're
going
to
get
to
the
demo
and
we're
going
to
run
that
in
fact
we're
going
to
get
to
the
demo
now
so
for
the
demo
before
I
launch
it
I'll
try
to
talk
for
a
minute
about
what
what
I'm
doing.
I
have
three
vms
on
my
my
poor
little
laptop
here
that
are
windows.
I
am
going
to
use
ansible
to
build
a
domain,
so
I'm
gonna
build
a
domain
controller,
promote
it
and
then
add
a
machine
to
the
domain
and
do
some
kerberos
stuff.
B
So
that's
that's
kind
of
what
we're
doing
here.
I've
got
vms
aside
from
that
I
have
sort
of
for
bonus
points.
I
have
a
demo
limited
demo,
that
being
that
this
entire
presentation
is
also
being
run
inside
of
a
playbook.
So
I'm
going
to
close
my
powerpoint
and
let
my
ansible
demo
launch
my
code
editor
here
so
so
this
you
can
do
dumb
things
with
ansible
two,
not
just
like
super
productive
things.
B
A
I
mean
this
is
for
you
yeah,
because
my
problem
is:
I'm
actually
using
jordan's
images
through
vagrant
to
pull
down
and
spin
up
vms,
but
they're
not
domain
joined,
and
even
if
I
do,
I
just
feel
like
there's
a
ton
of
post
scripting.
That
has
to
be
done
and
I
just
I
don't
really
feel
see
the
benefit
of
the
tools
if
I
could
just
write
powershell
scripts
and
launch
them
from
within
the
vms
and
join
domain
and
do
all
that
stuff.
So
I'm
super
curious
to
see
where
this
goes
now.
B
Well,
cool,
so
I
am
actually
using
vagrant.
I
don't
know
if
I'm
using
jordan's
images
or
not
that's
something
I
found
a
while
back
but
yeah,
so
I've
got
is
basically
three
three
windows
server,
20
16,
probably
images
that
are
yeah
that
I
pulled
vegan.
So
I
got
three
machines
with
vega
running
on
my
machine
here:
yeah,
so
we'll
walk
through
that
those
are
all
just
freshly
freshly
built
non-modified
machines.
So
let
me
close
this
file
because
we're
not
already
talking
about
that
yet
so
I
wanted
to
start
with
vsco.
B
This
is
this
is
how
I
mentioned
my
my
co-worker
when
he
tried
to
talk
me
into
using.
It
was
all
about
like
ssh
into
some
terminal
and
then
vi
and
a
bunch
of
file
that
way
and
that
didn't
work
for
me.
What
worked
for
me
was
vs
code
and
the
windows
subsystem
for
linux.
So
I
want.
I
have
a
windows
box
and
I
want
to
do
my
execution
of
things
on
my
windows.
Machine
and
vs
code
is
my
editor
of
choice.
So
what
I'm
going
to
show?
B
You
is
kind
of
how
to
get
started
with
that
which
step
one,
of
course,
is
installed
vs
code,
although
everyone
probably
has
it
at
this
point,
and
if
you
don't,
you
probably
should
the
reason
I
like
vs
code.
So
much
is
because
of
well
for
all
the
reasons
that
vs
code
is
great,
but
specifically
for
all
the
different
file
types
that
are
involved
in
ansible
right.
You
have
just
plain
text
files.
You
have
yaml,
you
have
json,
you
have
powershell,
you
have
the
ini
files.
B
You
might
have
some
python
you
want
to
edit
vs
code
can,
of
course
parse
all
of
those.
So
you
don't
need
all
the
different
programs
for
all
the
different
file
types.
You
can
do
everything
right
in
here
and,
of
course,
vs
code
likes
the
to
do
the
folder
structure,
where
you
pick
a
folder
to
open
and
then
browse
all
the
files
there,
which
works
with
source
control
and
all
that
ansible
in
the
same
way
works
with
that.
A
A
Good
breaking
point
here,
so
let's
just
do
a
level
set
here,
so
we
covered
some
of
the
basics
about
you
know
the
pieces
of
ansible
that
are
important
and
we're
going
to
start
hitting
demos.
Anybody
have
any
questions
they
want
to
surface
up
to
jeremy
or
anything
that
he
talked
about.
That
maybe
doesn't
seem
clear.
C
B
A
B
Yes,
it
is
money.
It
is
quite
a
bit
of
money
that
red
hat
will
take
from
you
very
happily,
but
they
might
give
you
swag
for
it.
So
it's
probably
worth
it.
No
so
ansible
tower
basically
provides
a
web
interface
and
more
for
for
executing
those
playbooks.
So
all
along
the
way
I've
been
I've
been
thinking
about.
It
is
sort
of
extending
that
accessibility.
B
So
this
is
pretty
accessible
right.
You
just
install
a
linux
program
and
then
you
edit
some
yaml
files,
and
then
you
run
your
command
line,
but
that's
not
accessible
for
everyone.
What
is
accessible
for
everyone
is
logging
into
a
website
and
clicking
a
couple
of
buttons.
So
what
tower
or
awx
the
open
source
version
of
it,
it
does
is
sort
of
wraps
all
that
up
into
a
web
interface.
So
it
gives
you
a
graphical
method
for
running
playbooks
and
defining
inventory
and
access
and
editing
these
files
with
storing
the
output
and
job
history.
B
B
B
B
It
at
your
folder
and
you're
ready
to
go,
and
you
can
already
parse
all
your
files.
You
can
see
it
already
reads
all
these
different
things.
One
addition
I
would
so
a
year
ago
I
would
have
enthusiastically
recommended
the
ansible
vs
code
extension,
which
provides
code
snippets
and
some
editing
and
some
advanced
features
for
executing
stuff.
I
will
say
honestly
today
it's
kind
of
in
the
same
state.
It
was
a
year
ago
and
it
doesn't
seem
to
have
been
updated
very
well.
So
there's
some
weird
bugs
the
code.
Snippets
are
great.
B
I
don't
it's
kind
of
the
only
value
I
get
out
of
it
anymore.
So
I
included
that
because
you
know,
like
I
said
a
year
ago,
I
would
have
enthusiastically
recommended
you
install
it
today.
It's
it's
neat.
I
mean
I
don't
know,
I'm
disappointed
that
it
hasn't
been
maintained,
as
you
know
like
it
should
have
been.
So
that's
just
my
opinion
on
it,
but
it's
probably
still
worth
installing.
I
mean
it's
worth
the
cost,
which
is
free
for
sure
so
and
it's
a
quick
download
and
it
does
a
bunch
of
stuff.
B
B
So
a
couple
of
things
with
the
files
associations
you
can
do
in
in
vs
code
right
where
you
can
say
you
can
sort
of
pre-define
the
the
type
of
editing
to
use
with
different
files,
so
the
typical
sort
of
common
behaviors
for
your
host
file,
which
is
where
you
specify
your
inventory
and
that's
my
bedtime
war.
That's
going
on
in
the
background,
though,
so
sorry
about
that.
B
It
doesn't
typically
yeah
somebody
some
money
yeah,
so
it
doesn't
typically
have
an
extension
because
the
linux
they
don't
like
extensions
for
some
reason.
I
don't
know
that's
the
thing
apparently,
but
so
what
I
like
to
do
is
I
like
to
define
that
here
as
an
ini
file
format?
Just
so
when
I
look
at
it,
it's
not
just
a
blob
of
text,
it
does
some
color
coding
and
makes
it
pretty
so.
B
You
can
parse
it
as
ansible
and
it
changes
the
colors
a
little
bit
and
it
probably
provides
some
extra
capabilities.
I
haven't
actually
done
an
ap
comparison,
so,
but
you
know
the
extension
says
it's
helpful.
I
believed
it.
You
know
a
year
ago,
so
that's
that's,
potentially
an
option.
You
can
kind
of
tell
it
hey
by
default,
and
this
and
this
other
option
is
by
default,
just
set
everything
ansible,
because
I'm
probably
going
to
be
editing
an
ansible
file,
a
yaml
file.
B
Shell,
which,
by
default
with
vs
code,
is
powershell,
so
what
I'm
going
to
do,
because
everything
I'm
going
to
run
here
is
going
to
be
a
linux
program,
I'm
just
going
to
default
my
integrated
shell
to
bash,
so
that
when
I
do
my
hotkey
and
I
open
up
my
terminal,
it
goes
straight
into
straight
into
my
windows,
subsystem
for
linux
environment,
which
brings
me
to
the
second
part
of
this
section,
which
is
configuring.
Your
windows
subsystem
for
linux,
for
executing
of
all
your
playbooks
right,
because
you
need
a
this
is
a
requirement.
B
You
need
a
linux
environment
to
run
ansible
on
that's
just
the
way
it
is,
and
you
can.
You
can
connect
to
a
remote
machine
and
do
that.
But
then
you've
got
to
deal
with
getting
files
across
and
can
be
hairy.
There's
a
lot
of
options
with
remote,
wsl
and
remote
windows,
and
but
still
you've
got
to
you've
got
to
deal
with
that.
So
for
my
purposes
I
installed
wsl
locally
and
then
I
just
run
everything
through
there.
B
So
let
me
open
up
my
cheat
sheet
here,
because
there
are
some
things
you
got
to
do,
and
this
is
all
in
the
repository
which
will
be
available
we'll
get
a
link
somewhere
at
some
point
at
the
end
of
that
slide,
and
you
can
post
it
on
the
on
the
video,
so
you
can
download
all
these
files
and
run
through
it.
I
opted
to
not
walk
through
and
make
you
watch
me
run
in
a
bunch
of
apt-get
updates,
because
it's
not
very
exciting
and
it
takes
forever
and
my
internet
can
be
weird
sometimes
so.
B
Basically
this.
What
I
have
here
is
a
list
of
all
the
different
ways,
the
things
that
are
prerequisites
you
need
for
this
particular
demo.
Some
of
the
things
you'll
need
in
any
windows
environment
are
going
to
be
obviously
ansible.
This
pi
1
rm,
is
how
you
make
winrm
connections
to
your
machines,
which
is
the
spoiler.
That's.
How
ansible
connects
to
your
machines
is
over
the
windows
when
rm,
powershell
remoting
and
then
there's
things
like
kerberos,
which
might
come
in
handy
depending
upon
your
environment.
B
So
if
you
are
familiar
with
the
intricacies
of
installing
software
in
linux,
you
might
have
a
strong
opinion
about
some
of
these
commands.
I
don't
have
a
strong
opinion,
so
you
may
want
to
install
stuff
different
ways.
I
kind
of
have
apt-get,
which
is,
is
the
method
for
installing
packages
with
ubuntu,
and
I
also
have
some
commands
through
pip,
which
is
the
python
installer.
B
You
can
install
some
of
this
with
alternate
methods.
What
I
have
found
it
seems
like
in
my
experience,
is
it
that
the
versions
that
are
available
when
you
use
pip
are
a
little
newer
than
what's
out
on
the
various
repositories
that
are
native
to
ubuntu
for
the
app
to
get
so
you
might
get
newer
stuff
using
pip,
but
again
so,
if
you're
just
following
along-
and
you
just
want
to
have
your
own
machine-
and
you
just
want
ansible,
then
just
run
these
commands
and
you'll
be
good
to
go.
And
again.
B
If
you
have
an
opinion,
then
you
know
you
can
install
software
whatever
makes
sense
for
your
linux
environment,
and
I
have
a
link
here
which
you
can
read
for
more
details
about
the
next
thing.
But
there
is
an
issue,
in
fact,
let
me
run
the
command
and
I'll
show
you
kind
of
this
is
sort
of
going
to
be
the
first
sort
of
must
do
prerequisite
for
building
your
environment.
So
I'm
going
to
run
our
ansible
playbook
command
that
we
saw
on
that
slide
right.
Let's
say
I'm
ready
to
go.
I've
got
wssl
installed.
B
I
want
to
run
my
playbook
right,
so
the
first
error
warning
ansible
is
being
run
in
a
worldwideable
directory,
ignoring
it
as
an
ansible.cfg
source,
and
here
in
a
second,
it's
going
to
say:
there's
no
files
and
it's
going
to
fail
so
well
not
fail.
It's
going
to
skip
so
basically,
what's
happening.
Is
it's
not
reading
my
comp
because
my
folder
permissions
in
linux
land
are
wide
open?
So
if
I
run
sort
of
this
first
of
secure
linux
command
and
look
at
a
directory
listing?
B
B
Ansible
doesn't
like
that
probably
for
security
reasons,
which
is
smart
right,
because
ansible
config
can
be
used
for
defining
where
files
are
downloaded
from
and
executed
to,
and
all
that.
So
in
this
case,
you
need
to
change
these
permissions
so
that
they
are
not
wide
open
right.
This
is
sort
of
the
linux
version
of
everyone,
full
control
on
your
files,
yeah
777,
just
yeah.
Let's
go
so
that's
not
cool,
so
we
run
it
so,
which
is
fine
right.
B
If
you
look
at
what
I
have
here,
my
path
is
actually
what
I'm
doing
here
is
kind
of
tricky.
This
is
actually
a
windows
volume
right.
This
is
my
windows.
C
drive
mounted
inside
linux
for
executing
files,
so
these
are
my
windows
files
that
I'm
running
in
linux
and
the
problem
is
that
by
default,
so
the
file
interaction
between
windows
and
linux
works.
The
metadata
which
includes
file
permissions
does
not
translate.
Those
are
two
totally
windows
file,
permissions
and
linux
file.
B
Permissions
are
totally
separate
things
and
by
default,
linux
does
not
mount
windows
volumes
with
the
ability
to
edit
linux
metadata.
So
you
can't
set
linux
permissions
on
any
of
these
files.
So
what
we
have
to
do,
we
have
to
set
file
permissions
in
order
to
be
able
to
run
any
of
our
stuff,
so
we
have
a
file.
B
This
is
in
in
our
linux
implementation,
etsy
wsl.com.
This
is
a
file
that
can
control
a
lot
of
different
things
with
the
way
wsl
runs.
So
our
particular
thing.
What
we
care
about
is
this
auto
mouse
section.
So
we're
going
to
add
these
two
lines
in
in
this
file,
so
I'm
going
to
live
and
without
any
rehearsal.
B
B
We're
gonna
get
stuck
in
here
for,
like
an
hour
with
me,
rolling
my
face
across
my
keyboard,
trying
to
get
out
of
the
gym
that
worked
out.
So
that's
good,
okay,
so
normally
I
would
just
or
previously
I
would
just
exit
and
reload
it,
but
the
windows
developers
in
their
infinite
wisdom,
performance
reasons
or
something
they
would
leave
wsl
running
in
the
back,
do
that
it
doesn't
actually
close
it
sort
of
stays
open
for
a
little
while
so
for
some
indeterminate
amount
of
time.
I
don't
know
five
10
minutes
something
like
that.
B
C
A
C
C
C
B
I
actually
saw
jordan
had
a
mention
in
the
chat
about
wtsl2
and
I
just
want
to
mention
that
everything
I'm
doing
here
is
with
wso1
so
yeah.
If
the
behavior
is
different,
wsl
2-
I
I
couldn't
I
couldn't
say
so.
That
would
be.
That
would
be
interesting.
I
don't
know
I
haven't
gotten
into
the
details
of
what's
different,
but
yeah.
Everything
here
is
w01,
so
this
is
a
definitely
a
wsl
one
problem,
whether
it
is
with
two
or
not,
I'm
not
sure,
so
it
might
be
not
an
issue.
B
Where
was
I
okay?
So
now,
if
I
run
my
existing
command
again,
we
should
have
this
mounted
with
appropriate
permissions.
So
we
no
longer
have
right
access
right,
our
w
is
gone
and
that
will
make
ansible
happy
which
will
make
us
all
happy
and
everything
will
run
so
speaking,
of
which
let's
run
it
again
and
see
what
happens.
B
So,
let's
do
this,
I'm
gonna
do
like
a
cooking
show
and
I'm
gonna
run
my
playbook
and
then
hide
it
and
then
we're
gonna
go
talk
about
it
and
then
we'll
pull
it
out
of
the
oven
when
it's
done
so
let
me
run
my
playbook
and
this
is
super
basic
right,
we're
starting
at
the
beginning,
so
I'm
just
gonna
run
my
ansible
playbook
command
and
I'm
going
to
give
it
the
playbook
name,
which
I
creatively
named
playbook.yaml
and
start
running.
I
ignore
the
cryptography
error.
B
I
don't
know
that's
something
with
python3
and
I
haven't
dug
into
why
it
does
that.
So
everything
seems
to
works.
That's
a
new
one
for
me,
for
when
I
rebuild
my
machine.
So,
okay,
so
it's
running
and
I
don't
want
to
spoil
it.
So
I'm
going
to
close
that
and
let
it
run
in
the
background
and
we'll
talk
about
what
we're
doing
so.
Let's
look
at
our
playbook
file.
B
B
B
A
B
B
B
B
I
don't
have
that
yet
right,
I've
got
three
vms
with
no
dns
or
anything,
because
I
haven't
built
that
yet
so
what
I
can
do
is
cheat,
and
I
can
I
can
specify
that
name
here,
but
then
I
can
also
just
define
hard
code.
This
variable
name,
which
is
the
ansible
host,
is
sort
of
the
built-in
variable
used
to
connect
to
machines
and
I'm
just
going
to
hardcode
the
ip
address
in
here,
and
this
is
kind
of
how
I'm
getting
started
notice.
B
B
And
the
first
option
here
with
my
plays
is
gather
facts,
and
that
was
when
I
talked
about
vars
and
facts,
and
one
of
the
things
ansible
can
do
is
retrieve
data,
so
this
will
run
a
module.
It's
actually
called
a
setup
module
it'll
go
out
to
the
machine,
gather
a
bunch
of
data
and
it
gets
stuff
like
operating
system
version
and
a
bunch
of
weird
wmi
stuff
and
ip
address
and
manufacturer
and
environment
variables
disk
space
that
sort
of
stuff.
C
B
C
C
A
So,
jeremy,
I
got
a
question
for
you
here.
So
obviously
I
see
you
have
a
clear
text
password
here
and
you
know
just
for
the
demo
but
yeah.
So
you
mentioned
in
the
beginning
that
you
can
set
up
a
job
so
that
you
can
have
it
run,
but
less
privileged
users
can't
see
the
parameters.
Things
like
passwords
and
stuff
like
that.
A
B
Yeah,
so
what
I'm
going
to
show
on
the
second
demo
is
how
you
can
encrypt
these
secrets
in
your
files.
So
you
can
you
can
encrypt
them
and
separate
that
password
out
as
its
own
built-in
fault.
It
does
actually
interface
now,
there's
some
modules
for
interfacing
with
other
password,
vaults,
akashi,
corp
and
cyber
art
and
stuff
like
that,
but
for
this
demo
yeah,
so
that
next
demo,
I'm
going
to
show
is
how
to
encrypt
that
and
how
you
can
store
encrypted
secrets
and
then
vault
them
away
and
separate
that
password,
so
awesome
yeah.
B
So,
let's
see
okay,
so
this
is
still
going.
My
poor
machine
is
having
a
trouble
building
three
vms
and
a
team's
meeting
text.
All
the
same,
we'll
see
how
it
goes.
Okay,
so
yeah.
The
first
thing
I'm
doing
here
right,
I'm
using
my
win
user
task.
So
the
tasks
are
this:
it's
just
a
little.
I
mentioned
everything,
inansible
being
yaml
is
just
a
list
or
a
dictionary.
So
this
dash
here,
if
you're
not
familiar
with
yaml.
This
is
how
you
indicate
kind
of
the
beginning
of
a
dictionary
in
a
list.
B
So
this
is
an
item.
The
first
item
in
my
list-
this
is
the
second
item,
so
if
this
were
an
array,
this
would
be
zero.
This
would
be
one.
This
would
be
two.
I
have
these
spaces
here.
Just
for
my
visibility.
Those
are
totally
optional.
You
can
kind
of
do
them
all
like
that.
What
matters
with
yaml
is
the
indentation,
so
you
can
see.
Vs
code
gives
me
these
little
helpful,
friendly
gutters
doing
this
in
notepad
would
just
be
like
a
horrible,
painful
misery.
B
The
module
name
here
is
what
we're
referencing
and
that
is
sort
of
the.
This
is
our
execution
rate,
so
we're
going
to
make
a
change
to
a
user
account
on
a
windows
box,
so
it's
called
win
underscore
user,
I'm
using
the
name
here
this
technically.
This
name
property
is
optional,
highly
highly
highly
highly
recommended
that
you
put
a
name
property
on
everything.
In
fact,
you
can
even
put
a
name
property
on
your
place,
which
I
always
forget.
It's
very
useful,
but
we'll
see
when
we
get
to
our
output.
B
If
I
can
get
these
vms
to
come
back
up
that
this
name
is
what
comes
in
our
output,
so
it
shows
you
kind
of
what
it's
doing
as
it's
doing
it
and
tells
you
the
status.
So
without
a
name,
it's
not
really
as
useful.
So
super
super
preferred
to
use
a
name
property
plus.
This
is
what
part
of
what
makes
it
readable.
This
is
text
you
can
put
anything
you
want
in
here.
You
can
actually
do
variable
substitution
in
here.
B
If
you
want
to
get
really
fancy
but
anyway,
so
this
is
our
first
task
we're
going
to
create
a
user.
Well,
we
are
going
to
declare
that
we
want
a
user
named
administrator
to
have
this
password
if
that
password
is
already
set
to
that
it
won't
change
it.
If
it
needs
to
be
changed,
it
will
change
it.
If
there's
not
an
account
called
administrator
which
would
be
interesting
on
a
new
vm,
it
would
create
it
so
again
we're
not
telling
it
what
to
do.
B
We
are
declaring
what
state
we
would
like
it
to
be
in
likewise,
here
our
next
one.
Here
we
are
defining
declaring
that
our
windows
update
service
must
be
stopped
and
disabled
and
I
threw
this
in
there,
so
it
wouldn't
try
to
do
any
weird
things
with
the
internet.
While
I
was
building
up
my
first
vms,
so
I'm
saying
here's,
the
win
service
is
the
name
of
the
module
I
want
to
use
and
I'm
simply
declaring
my
state
right.
State
is
stopped.
My
start
mode
should
be
disabled.
If
it's
already
in
that
state,
that's
fine.
B
It
won't
make
any
changes.
You
can
do
comments
in
yaml,
so
this
is
a
property
is
force
dependent
services.
This
is
like
the
dash
force
on
a
start
service
or
a
stop
service,
or
something
like
that.
That
is
a
property
of
the
wind
service
module
that
you
could
reference.
I
have
commented
out
so
comments
are
supported.
I
don't
even
remember
why
I
commented
that
I
think
probably
just
to
show
that
it
was
a
comment,
so
we'll
go
with
that,
but
and
then
as
we're
going
through.
So
this
is
this
is
mike.
B
This
is
the
part
of
the
beginning
of
the
secret
sauce
here,
I'm
going
to
use
the
win,
feature,
module
and
install
the
ad
domain
services
feature,
and
you
might
recognize
some
of
these
properties
here
as
parameters
for
our
install
windows,
feature
powershell
command,
right
management
tools,
sub
features
all
that,
so
I
like
to
think
of
ansible
tasks,
sort
of
as
as
function
calls
right
because
you're
defining
the
name
of
the
thing
when
feature
and
then
you're
passing
in
the
defined
parameters
as
properties.
So
it's
very
similar
to
that
now,
I'm
doing
something
fancy
here.
B
I
have
these
keywords,
which
again
yaml
is
important
with
the
indentation
so
notice
how
these
are
indented
out.
These
are
properties
of
the
ansible
execution
of
this
task.
These
are
not
properties
of
the
task
itself.
So
what
I'm
doing
here,
two
things
I'll
start
with
this
register,
so
a
register
is
a
way
to
say.
Whatever
comes
back
when
you
execute
this
task,
whatever
comes
back
from
it,
put
that
in
a
variable-
and
that
includes
things
like
whether
or
not
it
succeeded
whether
or
not
it
actually
changed
anything
and
some
other
some
properties.
B
If
it
actually
returned
data,
it'll
put
that
in
this
variable,
so
now
this
is
where
you
create
a
variable
or
a
fact,
whatever
you're
going
to
call
it,
I'm
calling
it
adds
underscore
install.
So
that's
the
first
kind
of
fancy
thing
I'm
doing
here.
The
other
thing
I'm
doing
is
this
win,
and
this
is
where
you
get
into
the
condition.
This
is
a
conditional
for
a
task.
This
is
where
we
get
into
kind
of
programmer
jive
and
where
I'm
saying
in
this
case
I'm
saying
this-
I'm
referencing
a
variable
right.
B
So
one
of
those
properties
of
this
giant
variable
is
called
memtotalmb.
So
I'm
saying
here
when
my
m
total
mb
property
on
my
machine
is
equal
to
40.
96
run
this
task
and
the
reason
I
did
that
is
so.
This
is
basically
four
gig
of
ram
right.
So
what
I
did
is
I
gave
my
two
dc's
four
gig
of
ram
and
my
member
server
2
gigaherm,
so
I
have
something
to
just
differentiate,
but
the
idea
here
is
that
this
is
only
going
to
run
on
my
dc's
because
of
this
nomenclature.
B
Now
I
could
have
done
some
conditional
and
said
like
where
the
group
name
is
dc's
or
where
the
host
name
has
the
letters
d
and
c
in
it,
or
something
like
that.
So
you
can
do
any
kind
of
conditionals
here,
but
I
wanted
to
kind
of
illustrate
that
you
can
use
this
data.
You
gather
either
from
here
or
from
any
other
task
and
use
that
to
determine
whether
or
not
you
run
another
task.
B
Likewise
after
I
install
ad
domain
services,
this
is
windows.
After
all,
so
we
need
a
reboot
right.
Reboot
early
reboot
often
is
the
mantra.
So
after
I
install
my
windows
feature,
I'm
going
to
reboot
my
boxes,
but
I
only
want
to
reboot
if
adds
was
actually
installed
right.
The
idea
here
is:
is
the
fancy
term
item
potency,
where
I
can
run
this
multiple
times
and
I
will
always
get
the
same
ultimate
result.
So
I
want
to
install
my
adds
windows
feature,
but
the
second
time.
B
I
would
run
this
if
I
ran
this
a
second
time
it's
already
installed.
It
wouldn't
do
anything
right.
So
what
I'm
saying
here
is
is
when
the
changed
property
of
my
previous
task,
which
is
why
I
registered
stuck
that
in
a
variable.
So
if
the
change
property
is
equal
to
true
that
that
means
it
actually
made
a
change
and
that's
something
ansible
keeps
track
of
whether
or
not
it
actually
made
a
change
or
not.
B
So
if
it
actually
changed
it
then
do
a
reboot.
So
the
first
time
I
run
this,
it's
going
to
actually
do
the
install
and
then
it's
going
to
reboot
the
second
time.
I
run
this.
It's
not
going
to
do
anything
here
because
it's
already
installed,
so
it's
going
to
also
skip
the
reboot,
we'll
see
that
in
when
we
run
this
and
then
as
part
of
building
my
lab,
I'm
referencing
this
task
here,
the
wind
dns
client.
So
I'm
going
to
set
my
dns
client
settings
to
point
to
my
new
domain
controller.
C
So
the
question
there
with
for
those
who
kind
of
didn't
understand
I
didn't
understand
initially,
is
that
this
same
playbook
is
running
for
every
single
one
of
those
hosts
on
the
right
is:
yes,
it's
going
to
run
the
same,
and
so
it
will
still
run
this
and
kind
of
like
you.
You
did
some
magic
or
you
know
I
had
to
click
for
me
as
far
as
the
light
bulb
going
off
is
that
this
is
the
same
playbook
that's
going
to
run
for
each
one
of
them.
B
Yeah,
so
definitely
right,
so
this
is
going
to
run
three
concurrent
executions
of
all
of
these
tasks.
On
my
three
machines,
if
there
were
more
machines,
it
would
run
it
would
run
against
all
of
them
and
that's
defined
by
my
use
of
the
word
all
here.
If
I
had
a
set
of
tasks
or
just
for
my
dc's,
I
could
have
a
play
here
and
I
could
say,
hosts
dc's
and
just
run.
Those
on
on
this
inventory
group
is
one
way
of
grouping
this
up
right.
C
B
B
And
run
some
other
stuff.
Okay,
I
got
you
now
right,
so
you
can
do-
and
this
is
kind
of
in
my
second
demo-
I
kind
of
get
into
more
advanced
stuff,
but
this
is
kind
of
how
you
ansible
gets
into
like
sequenced
orchestration
right,
so
you
can
be
like
run
this
stuff
on
this
machine
and
then
go
run.
This
thing
on
this
api
call
to
some
other
system
and
then
come
back
and
run
this
task
on
these
machines
right
in
the
order.
It
would
run
it
in
that
order.
B
B
B
This
is
this
task
here
right
now
to
see
that
see
the
output
rate
set
administrator
password.
So
that's
why
the
name
is
so
important
because
it
will.
It
will
tell
you
on
the
output
what
it's
doing
as
it's
going
based
on,
if
you,
if
you
leave
this
off
it'll,
just
say
task:
when
user
right
it'll
just
tell
you
the
name
of
the
module,
so
so
assuming
these
colors
are
coming
through
right
here,
let's
we
got
some
some
different
things
going
on
gather.
B
Facts
came
back
green
with
a
version
status
of
okay
right
for
our
three
machines.
This
is
where
I
was
talking
about
the
concurrent
right,
it's
running
on
each
machine
independently,
and
it
returns
that
status
so
gather.
Facts
didn't
change
anything
right
because
it's
just
getting
data.
So
of
course
it's
going
to
say:
okay,
oh
I
mean
it
could
have
said
failed.
Luckily
it
didn't.
It
said.
Okay,
our
administrator
password,
however,
needed
to
be
changed.
So
that's
why
it's
yellow
and
it
has
a
property
of
change,
so
it
ansible
keeps
track
of
the
difference
between.
B
Yes,
it
is
in
the
state
I
wanted
it
to
be
in,
but
I
had
to
make.
I
had
to
do
something
to
make
it
that
way
and
those
are
potentially
differentials
the
when
this
update
service
was
already
stopped
and
disabled.
So
that
came
back.
Okay,
my
windows
feature
notice.
It
says
it's
blue
there.
It
says
skipping,
so
it
skipped
server
3,
because
server
3
didn't
meet
the
condition.
B
B
No,
that's
a
good
question,
so
what
ansible
will
do
is
on
a
failure
by
default.
It
will
halt
execution
of
for
that
machine.
Any
failure
will
cause
that
machine
to
just
be
done
right
and
whatever
task
it
is.
It
won't
try
to
run
anything
else
for
the
machine
so
yeah
if
one
of
them
failed
they'd
be
like
the
two
left
that
didn't
fail,
we'll
keep
going
and
if
one
of
them
fails,
the
one
left
will
keep
going.
B
B
C
So
it's
also
a
good
practice
to
actually
have
some
prerequisites
and,
like
you
know,
hey
only
run
this.
If
this
doesn't
happen
or
a
suit,
like
I
don't
know,
if
you're
doing
some
ad
stuff
and
like
if
it
successfully
installed
this.
So
if
it
somehow
got
past
a
step
that
failed
you'd
do
some
logic
to
figure
out.
Did
it
get
there
right.
B
B
B
Yeah
so
ansible
facts
is
sort
of
a
default
defined
variable
name,
which
is
mentioned
several
times
in
the
in
the
sort
of
the
documentation.
As
far
as
how
you
know
to
what's
in
it
I'll
get
into
the
next
demo.
I
mentioned
some
extra
tasks,
but
there's
my
favorite
task,
which
is
the
debug
task,
and
you
can
use
that
to
output
the
value
of
any
variable.
B
So
if
you're
thinking-
oh,
I
heard
about
this
variable,
let's
see,
what's
an
ansible
facts,
I'll
just
do
a
dash,
debug
task
and
say
the
variable.
Is
this
and
spit
out
and
it'll
spit
out
in
the
output
that
data?
And
so
you
can
look
at
it
and
see
all
the
gory
details.
You
can
use
that
for
more
complex
things,
string,
manipulation
and
variable
substitution
testing,
but
debug
is
a
good
way
to
kind
of
see
all
that.
B
Okay,
so
there
we
go,
our
dc
feature
was
installed
on
dc
one
and
two.
Those
came
back
has
changed
and
because
of
our
condition,
reboot
was
done
only
on
dc
one
and
two,
the
server
three
skipped
it,
because
again
it
didn't
install
anything.
So
it
doesn't
need
a
reboot
and
then
it's
doing
our
dns
clients.
Now.
C
B
C
B
Would
just
be
skipped
because
it
would
well,
it
would
come
back
green
and
then
it
would
skip
all
the
reboots,
because
we
didn't
actually
install
anything
so,
and
you
can
see
you
get
a
nice
summary
here.
At
the
end,
it
tells
you
kind
of
the
number
of
number
of
tasks
and
kind
of
what
happened
and
you
can
see
on
server
three.
It
skipped
two
of
the
tasks
so,
and
this
is
part
of
like
if
you,
if
you
ignored
a
failure,
it
would
still
show
up
in
here
as
a
failure.
B
B
So
can
you
log
the
output
of
ansible,
so
by
default
it
just
comes
out
of
the
screen
like
this.
There
are
a
whole
lot
of
ways
to
modify
that
which
are
with
some.
I
think
they
call
them
callback
plugins.
If
I
remember
right
where
you
can
say,
instead
of
sticking
it
out
like
this
dump
it
out
as
yeah,
yeml
or
json,
or
stick
it
out
to
a
file,
there's
a
bunch
of
ways
to
modify
that
behavior.
B
B
C
B
B
B
All
yours
all
right,
okay,
so
mike
you
asked
the
question
a
very
mvp
type
of
question.
I
might,
I
might
add
about
in
doing
something
about
that
plain
text
password
which
is
is
important
to
not
include
in
any
of
our
files,
especially
because
as
good
dev
sys
admins,
whatever
we
call
ourselves
now
we're
putting
all
of
this
in
source
control,
which
means
that
plain
text
password
is
out
there
forever.
B
So
we
don't
want
to
do
that.
So
what
we're
going
to
show
here
is
sort
of
the
built-in
vaulting
mechanism
of
ansible,
and
I
want
to
list
this
first.
I
am
listing
this
as
a
beginner
topic,
because
I
think
it's
important
to
ever
for
for
everyone
to
encrypt
their
secrets
that
whole.
Oh,
this
is
just
a
demo.
It's
okay!
I
I
don't
think
that
flies
and
ansible
vault
is
super
easy
to
use.
So
I
say:
there's
no
excuse
for
not
encrypting
all
your
secrets
so
and
I'm
gonna
stick
by
it.
B
So
I've
opened
up
this
file
here,
and
this
has
a
password
in
it,
as
evidenced
by
the
name
being
ansible
password
and
I'll
talk
later
about
the
what
this
file
is
in
the
specifics
of
it.
But
anyway,
as
you
can
see
here,
this
is
a
password.
Passwords
are
bad.
We
want
to
do
something
about
this,
so
I'm
going
to
run
this
ansible
vault
command
and
I'm
going
to
pass
the
encryption
option
here.
The
encrypt
option
I'm
going
to
tell
the
file.
I
want
to
encrypt
there's
a
lot
of
options
for
this
ansible
vault.
B
You
can
look
up
the
details,
I'm
just
going
to
run
it
and
it'll
be
relatively
apparent.
What
it's
doing
and
there's
that
cryptography
error
ignore
that,
hopefully
it
won't
do
it
on
your
machine.
I
don't
know
why
this
popped
up
but
anyway.
So
it's
asking
me
for
my
password
that
I
want
to
set
for
encrypting
my
password.
B
Okay,
so
I'm
going
to
confirm
so
I'm
encrypting
it
with
a
new
password,
but
this
password
is
not
going
to
be
stored
in
a
file
in
my
source
control
so
boom.
I
just
just
encrypted
it.
That's
my
file.
It's
encrypted.
It
says
it's
aes256
encryption.
I
believe
it
because
I
don't
know
any
better.
It's
a
lot
of
numbers
and
I
can
take.
I
can
now
take
this
file
and
I
can
put
that
in
source
control.
I
can
leave
this
in
my
folder.
I
can
commit
that
and
I'm
I
can
be
safe.
B
It
is
presumably
unhackable
unless
you've
got
a
quantum
computer
which
any
day
now
we're
all
going
to
get.
I
think
the
new
xbox
probably
has
quantum
capabilities
or
something
I
don't
know,
but
so
this
is
my
encrypted
file
and
that's
great
before
saving
that,
if
we
ever
need
to
make
a
change,
we
simply
decrypt
the
file
with
our
decrypt
command.
B
And
it
decrypts
it
puts
it
right
back
to
the
way
it
was
in
fact.
Even
you
know
the
source
control
agencies
there's
no
changes
to
it,
so
it
identical
the
way
it
was
so
that's
great.
But
what
if?
Let's
just
say
what?
If-
and
this
is
hypothetical-
this
totally
didn't
happen
to
me
in
production
on
a
on
a
super
important
project
or
anything?
B
What,
if
you've
encrypted
your
file
and
then
several
months
later,
you
forgot
your
vault
password
right,
because
you
stored
that,
presumably
somewhere
else,
you
know
on
your
password
thing
like
cyber
arc
or
the
sticky
note
under
your
keyboard,
but
then
the
cleaning
crew
came
and
stole
it
or
something.
So
you
lost
your
password,
so
you
can't
decrypt
that
file
anything.
Well,
that's
fine!
The
actual
password
in
there
I
know,
or
I
can
go
and
get
so.
I
can
just
recreate
that
file.
B
B
In
fact,
we
might
want
the
rest
of
the
file
to
be
readable,
for
people
to
see
those
values
to
help
kind
of
understand.
What's
going
on.
So
if
we
want
to
just
encrypt
this
one
string,
we
can
do
that
also
with
ansible
vault,
with
the
encrypt
stream
option,
and
so
we're
going
to
tell
it
encrypt
the
string,
vagrant
and
output
that
so,
let's
run
this
command
and
same
kind
of
deal,
you're
going
to
give
it
a
vault
password.
B
B
And
it's
going
to
now
in
this
case
it
didn't
encrypt
the
file
it
just
it:
output,
the
string
so
notice
the
pattern
here
right,
ansible,
password,
colon
and
then
a
bunch
of
stuff.
So
we're
going
to
very
carefully
copy
this
careful
not
to
get
the
new
line
at
the
end
or
you'll
get
problems
and
we're
going
to
replace
this
line.
Here
with
that.
B
So
now
we
have
our
file
with
all
our
details
that
we
can
still
read,
but
our
one
thing
that
we
care
about
encrypting
is
encrypted,
so
we
kind
of
get
it
both
ways
and
if
you
you
know,
if
you
had
a
problem
with
that
password,
you
could
go
and
just
recreate
this.
You
know
if
you
had
to
without
losing
the
entire
file.
B
C
B
That
and
then
we
can
now
run
our
playbook,
but
we
might
have
a
surprise
error.
Well,
not
that
one
that
one's
fine,
the
cryptography
error,
is
fine
or
that
this
error
is
important.
So
in
this
case
on
all
three
machines,
we
got
an
error
that
it
was
attempting
to
decrypt,
but
no
vault
secrets
were
found.
So
we're
passing
in
that
file,
trying
to
read
that
file,
but
ansible
sees
that
it's
vaulted
because
of
that
tag
there,
but
it
doesn't
have
any
password
so
that
password
that
we
used
to
encrypt
the
file
or
that
stream.
B
B
So,
let's
see
I'm
going
to
run
this
and
that
should
work
and
it's
going
to
ask
us
our
vault
password,
so
we
can
decrypt
that
file
at
run
time,
all
in
memory
super
secure,
presumably,
and
it's
going
to
run
so
now
it's
going
to
run
the
step
option
is
is
what's
what's
now
prompting
us
and
it's
asking
us
if
we
want
to
run
the
next
task,
so
I'm
going
to
use
that
as
an
option
to
talk
about
our
next
playbook.
So
any
questions
on
the
vault
stuff
before
I
get
into
some
more
fun
tasks.
A
This
is
a
question
that
maybe
might
not
be
for
jeremy,
but
does
azure
keyboard
require
a
vault
password
to
access
it.
I
don't
think
it
does,
because
the
question
I
was
going
to
ask
was
what,
if
you
wanted
to
run
these
at
automated
tasks,
it
seems
like
it
has
to
be
interactive
because
you
have
to
put
in
that
master
password
vault,
I'm
just
wondering.
Is
there
a
way
around
that.
B
Yeah
so
ansible
vault
itself.
Now
I
don't
know
about
the
azure
keyboard
stuff,
but
ansible
vault
itself
has
also
has
the
option
you
could
put
the
password
that
I
typed
in
you
could
put
it
in
a
file.
I
just
have
it
not
in
your
source,
control
directory.
You
know,
have
it
in
like
a
system
file
that
you
can
only
access
on
that
host
or
something
like
that.
B
I
have
it
secured
some
other
way
and
then
you
can
pass
in
and
say
the
parameter,
I
believe,
is
like
dash
dash,
vault
pass
fault
password
file,
or
something
like
that,
you
can
say,
go,
look
up
the
password
of
this
file
at
runtime.
So
that
would
be
how
you
would
do
this
interact.
Non-Interactively,
okay,
yeah.
So
then.
C
Sorry,
I
just
thought
it'd
be
good
to
mention
that
file
can
also
be
an
executable
script
to
retrieve
that
password
from
another
source.
So
if
you
don't
want
a
plain
text
file
with
that
one
in
there,
you
can
have
that
reach
out
to
a
separate
surface.
But
it's
probably
a
bit
of
a
moot
point,
because
if
angel
can
run
that
script,
then
you
can
run
that
script
right.
C
B
Okay,
when
I
did
just
a
string,
okay,
yeah
so
so
vagrant
was
the
string
that
I
wanted
to
encrypt.
That's
my
that's
my
machine
password.
That
is
my
secret
right,
and
so,
when
I
run
this
command,
I'm
saying
encrypt
this
string.
What
the
vault
pass
that
it's
asking
me
is.
That
is
the
password
that
I'm
using
to
encrypt
this
stream.
B
B
B
C
C
So
really,
I
think
what
at
that
point
is
that
that
encrypt
string
part
of
key
ansible
vault?
Basically
it
creates
that
that
set
of
strings
there
and
that's
what
it
builds.
So
then
he
copied
that
and
put
it
into
the
file.
So
it's
just
to
build
that
section
of
that
code
of
that
file,
and
so
that's
really
what
it's
doing
so,
instead
of
using
the
yaml
itself-
and
you
saw
them-
write
it
up-
it's
it's
building
that
string.
So
then
you
copy
and
paste
that
in
there.
C
So
you
could
it's
just
a
way
to
encrypt
that
section:
okay!
Well,
it
was
it
wasn't
clear
since,
since
we
had
done
vote
since
he
had
shown
us
both
a
vault
password
and
the
string
encrypted
string,
how
how
ansible
was
differentiating
between
those
prompts
because
it
because
it
seemed
like
ansible
vault
password-
was
the
prompt
for
both
passwords.
C
C
So
with
that,
I
guess
how
would
it
interact
like
with
rsa
or
so
in
my
environment?
We
got
rsa
tokens,
that's
used
to
or
your
user
token
to
access
into
your
cyborg
to
get
your
cred.
Oh
the
the
guy
with
the
spinning
fan
is
back
now,
so
I
was
just
wondering:
will
ansible
you
know,
interact
with
rsa,
just
fine
when
reaching
into
like
cyber
arc
or
something
like
that,
and
this
fan
keeps
freezing.
C
I
see
with
ants
for
you've
got
the
concept
of
look
up
plugins,
which
can
look
up
values
from
separate
services,
so
I
know
we
have
ones
for
cyber
arc,
I'm
pretty
sure
there's
an
azure
key
vault
one
which
can
be
used
to
get
secrets
from
those
services,
and
you
can
use
that
to
actually
set
something
like
your
answer
password
to
connect
to
a
host
with
that
one
there.
So
it's
definitely
possible
to
do
it.
C
B
A
B
Okay,
so
let
me
walk
through
some
of
this
here,
so
this
next
section
here,
this
doesn't
have
anything
to
do
specifically
with
building
out
the
domain.
I
just
I
wanted
to
have
a
playbook
that
was
a
list
of
a
bunch
of
other
common
and
what
I
think
are
very
useful
tasks
for
doing
different
things.
So
I'm
going
to
walk
through
some
of
these
and
talk
about
some
of
the
interaction
and
dealing
with
with
text,
because
linux
likes
text.
B
Okay,
so
again
I'm
running
this,
so
I'm
going
to
run
I'm
going
to
say
yes,
I
want
to
run
my
gather,
fax
here,
I'm
going
to
let
that
run,
and
so
this
is
this,
this
step
option
which
is
really
cool
when
you're
testing
stuff
out,
because
it's
going
to
ask
you
for
every
task
and
the
first
task,
it's
going
to
run
gather
facts
here.
The
first
task
is
useful:
is
this
one
win
ping
and
it
looks
weird
because
there
are
no
actual
properties?
B
B
B
B
Okay,
okay,
I
thought
that
was
pretty
clever
but
anyway,
so
the
the
importance
of
that
is
that
it
tests
sort
of
everything,
so
it
tells
you
dns,
is
is
working.
It
tells
you
you
have
ip
connectivity,
it
tells
you
your
credentials
are
working,
it
tells
you
remoting
is
enabled
on
your
endpoint
correctly
and
that
the
firewall
is
set
up
correctly
and
that
you
can
connect
and
run
stuff.
So
the
idea
being
is
that
if
windping
works,
your
other
tasks
should
work.
At
least
you
don't
have
a
connection
issue
right.
B
So
that's
a
good
way
of
telling
if
anything,
if
everything
is
working
right.
In
this
case
it
comes
back
okay,
so
all
my
other
tasks
would
work
so
the
next
one
here
this
is
what
I
mentioned
earlier
when
someone
asking
about
ansible
facts.
In
fact,
this
is
the
example
I'm
using
is
a
debug,
and
this
is
just
a
way
to
say
in
this
pl
in
this
case
output
the
contents
to
this
variable
and
that's
it
I
like
to
use
it
with
the
pause
module
in
that.
B
Let's
say
this:
wasn't
at
the
beginning
of
your
script:
let's
say
you
had
like
20
tasks
and
then
a
debug
and
then
a
bunch
of
other
tasks
and
if
it
just
went
through
and
scroll
off
your
screen,
you
never
see
the
output.
So
let's
say
you
you're
testing
and
so
you'll
say
you
know
what
I
want
to
output.
B
My
variable
check
it
before
I
run
the
next
task
and
see
if
it's
okay,
so
I'm
going
to
throw
a
pause
in
here
and
so
I'm
going
to
say:
yes
run
that
and
we'll
scroll
through
this
in
just
a
second,
it's
going
to
scroll
and
spew
all
my
stuff
and
if
I
didn't
have
a
pause,
it
would
just
keep
going
and
I'd
never
be
able
to
see
any
of
it,
and
then
it
would
come
to
a
pause.
So
my
pause
task,
the
the
the
part
up
here
where
I
said
yes,
that's
the
step
module.
B
So
that's
not
pause.
Pause
is
right
here.
So
it's
pausing
for
the
time
that
I
specified
in
this
case
five
minutes,
and
so
this
is.
This
is
great
with
diba,
because
now
I
can
say
all
right.
Let
me
look
at
my.
Let
me
look
at
my
stuff
here
and
see.
If
you
know
this
is
whatever
I'm
doing
is
correct
or
what
I'm
expecting
it
right.
If
I'm
building
a
variable
or
getting
some
information,
you
know.
Oh
okay,
I
want
to
reference.
B
The
os
is
the
name
of
the
property
or
whatever,
so
you
can
run
that
and
you
can,
you
can
then
decide
you
can
either.
We
can
either
sit
here
and
stare
at
each
other
for
300
seconds,
which
we
might
do
if
my
internet
comes
out
again,
but
otherwise
we
can
end
this
early.
So
let's
say
that
I
looked
at
this
and
it
was.
It
was
well,
it
was
terribly
wrong
and
it
had
the
wrong
machine
and
my
next
task
was
like.
I
delete
everything
right,
so
I
don't
want
to
run
the
next
task.
B
I
can
do
a
control
c
and
then
I
give
it
the
a
and
say
abort
and
it
would
end
completely
or
the
entire
playbook
would
just
stop
execution
in
this
case.
I
want
to
continue
early.
This
is
all
fine
for
me,
so
I'm
going
to
say
control
c
and
I'm
going
to
say
c
for
continue
and
it's
going
to
go
on
so
those
I
find
those
I
use
those
two
together
all
the
time.
B
B
There's
also
to
that
is
the
win
underscore
command,
which
will
just
run
a
command.
So
you
know,
sometimes
you
get
a
weird
command
or
an
executable.
You
want
to
run
and
it's
kind
of
funky
in
powershell,
because
you
got
to
like
run
cmd
inside
a
powershell
and
then
do
a
bunch
of
weird
escaping.
So,
if
you
have
a
scenario
like
that,
you
can
use
win
command
instead
and
it'll
just
run
the
command
directly
instead
of
a
shell,
but
sometimes
you
need
an
actual
shell.
B
So
those
are
two
options:
yeah
so
and
it's
very
basic
you
can
just
run
a
run.
Powershell
right
and
it'll
run
the
run
that
command
and
just
tell
you
that
it
ran
it
so
notice.
It
says
changed
here
now
we
know
get
child
item
doesn't
change.
Anything
right.
Ansible
doesn't
know
that
it
doesn't
know
what
you're
in
all
it
knows
is
it
ran
windshell
and
it's
configured
by
default
to
just
assume
that
something
changed
right.
So
there's
some
options
you
can
do
to
modify.
I
like
to
define
market
has
changed
if
the
output
was
this.
B
So
I'll
show
you
here
kind
of
what
you
can
do
about
that,
so
the
other
thing
you
can
do
is
it
can
be
a
multi-line
script.
So
if
you
have,
if
you
have
multiple
a
larger
script
that
you
want
to
run,
you
don't
have
to
put
it
all
on
one
line.
You
can
use
this
pipe
character
and
then
anything
after
the
and
then
on
the
next
line.
B
Anything
after
that
that
is
indented,
because
yaml
will
be
your
script,
so
you
can
have
an
entire
powershell
script
in
here
as
long
and
the
indentions
extra
indentions,
don't
matter
as
long
as
it's
indented
in
from
the
module
name.
That's
the
important
part!
It
will
run
that
script
notice
that
I'm
doing
this
this
right
here,
which
is
the
ginger
substitution,
not
to
be
confused
with
jinya
that
fancy
ramen
restaurant
that
opened
up
there.
I
just
love
that
place
so
jinja
substitution.
B
This
is
how
you
do
variables
in
ansible,
so
the
two
curly
braces
encapsulating
something
everything
that's
in
there
will
get
processed
and
then
substituted.
So
ansible
hostname
is
a
pre-existing
variable
for
my
hostname.
So
it's
going
to
go.
Look
that
up
substitute
that
and
then
that
string
and
then
run
this
entire
command
on
the
machine.
So,
let's
see
we'll
walk
through
these
tasks
now
also.
B
C
B
B
Like
we
didn't
get
the
output
from
child
item,
if
we
want
to
get
the
actual
output
from
this
in
this
case
we're
creating
a
directory,
we
use
a
register
same
as
we
did
before.
Right,
take
the
output,
the
the
state
of
the
task
and
the
output
and
put
it
in
a
variable
and
then
we're
going
to
say
change
when-
and
this
is
where
I
was
talking
about-
we
can
say
mark
this.
This
will
be
yellow
as
unchanged
when
it,
the
standard
out
is
not
equal
to
empty
string.
B
So
if
there
is
output
in
this
case,
this
is
defined
right
in
this
case,
if
I
created
a
if
I
created
a
folder,
it's
going
to
have
you
know
when
you
create
a
directory
in
powershell,
it's
going
to.
You
know,
output,
the
the
details
of
it
and
that'll,
so
that
won't
be
empty
right,
and
so
it
will
be
changed
when
there's
output
and
if
it
doesn't
create
the
directory
because
it
already
exists,
then
it'll
just
come
back
and
it
would
say:
okay
notice.
B
All
that
item
potency
like
I
have
to
define
that,
because
one
shell
is
just
going
to
run
it
right.
So
I
have
to
say
you
know
if
it
exists
to
run
it,
it's
not
doing
any
magic
for
me,
that's
where
the
modules
come
in,
so
so,
let's,
let's
look
a
little
further
at
our
output
and
this
sort
of
gives
away
the
next
task.
But
the
output
of
this
is
kind
of
sucks.
I'll
show
you
what
I
mean:
isn't
that
beautiful?
B
So
what
ansible's
doing
is
it
basically
took
the
output
of
that
line
by
line
right,
like
here's,
our
standard
out
carriage
return,
new
line
character
in
a
new
line,
our
info
there's
a
new
line.
There's
there's
some
tabs
in
there.
Probably
so
now
it
gave
us
the
standard
outlines
where
it
it
scraped
that
into
a
list.
B
Yeah.
The
ammo
callback
plug-in
is
one
option
to
make
that
a
little
prettier,
but
this
is
by
default.
This
is
what
you
get,
which
is
I
mean
it's
whatever
text
right
and
if
you're
used
to
doing
text
like
linux,
guys
like
text,
I
guess
I
don't
like
text,
I
like
objects
and
properties
and
all
that
sort
of
stuff,
because
I'm
spoiled
so
here's
an
option.
B
The
the
best
way
it
seems
to
represent
complex
objects
via
text
or
at
least
transport
them
via
text,
without
them
getting
completely
obliterated
as
json.
So
we
can
represent
a
complex
object
with
properties
in
that
whole
hierarchy
and
json,
and
then
turn
it
back
when
we
when
we
come
back.
So
let's
do
that,
so
we're
going
to
run
our
get
child
item
script
again.
But
this
time
we're
going
to
convert
the
output
to
json,
put
that
in
an
output
variable
and
then
run
our
debug
command
to
look
at
the
output.
B
Then
we're
going
to
use
this
to
this
from
json
filter
to
turn
it
back
from
json
into
objects
which
are
going
to
be
dictionaries
and
lists
right.
So
turning
it
into
json
to
transport,
it
back
and
then
sort
of
reinflating
it
not
really
because
you're
not
getting.
You
know
mod
methods
and
all
that
fancy
powershell
stuff,
but
you
are
getting
the
hierarchy.
So,
let's,
let's
take
a
look
at
what
that
looks
like
so
I
run
it
get
child
item.
B
B
So,
but
we
assume
it
finishes
right,
we've
got,
we've
got
objects
with
properties.
I
mean
it
looks
like
structured
data
right.
So,
let's,
let's
find
out,
if
it
actually
is,
let's
do
some
of
that
yaml
programming.
I
said
you
shouldn't
do
so.
This
is
where
we
are
right,
we're
in
our
debug
output.
So
let's
use
this
is
a
help.
This
is
actually
a
pretty
helpful
module
set
fact.
This
is
how
you
can
create
a
variable.
B
Basically,
if
it's
empty
we're
going
to
set
it
to
a
default
list,
this
is
just
a
way
to
do
a
loop,
we're
going
to
get
the
full
name
property
of
each
item
we're
going
to.
I
don't
think
I
showed
an
example
of
this.
This
is
how
you
would
run
this
task
multiple
times,
so
our
output
being
a
child
item
right,
is
going
to
be
a
list
of
items
in
our
c
drive
right,
it's
going
to
be
more
than
one.
B
So
for
each
one
of
those
files
or
directories
or
things
in
our
list,
it's
going
to
run
this,
and
so
what
we're
doing
is
we're
adding
to
our
list
the
full
name
property
of
the
item.
An
item
is
the
variable
name
for
your
loop
element,
so
you're
not
going
to
do
a
pipe
before
each
object
in
powershell.
You
use
the
dollar
underscore
to
represent,
like
the
current
iterating
thing
in
your
loop
item.
Is
that
an
ansible?
So
whatever
you
are
your
loop?
That
you're
looping
through
item
is
the
variable
of
that
current
iteration.
B
The
current
thing
item
so
anyway
build
a
list
here
of
just
our
file
names
and
then
we're
going
to
do
a
debug
of
our
variable
to
see
if
that
worked
now
see
how
much
time
I
spent
explaining
what
this
does
like
this
should
have
like.
This
is
not
very
readable
right.
It
works
and
it's
cool
and
it's
powerful
as
soon
as
you
do
stuff
like
this,
but
you
can
see
in
a
in
a
hurry.
I
didn't
kind
of
know
state
where
this
is
not
very
readable.
So
keep
that
in
mind.
B
So
we're
going
to
say,
let's
set
our
fact
and
then
you
can
ignore
all
this,
because
this
is
like
building
and
parsing
and
running
through
the
loop
and
let's
look
at
our
debug
and
there
we
go
so
for
each
server.
Because
again,
this
is
all
still
running
on
each
of
the
three
machines
or,
however
many
machines.
B
We
have
a
just
names
on
each
one
of
those
it's
different.
Well,
it's
probably
all
the
same,
because
these
are
all
built
from
the
same
image,
but
could
potentially
be
different,
they're,
independent,
so
so
yeah,
that's
that's
one
potential
option
for
dealing
with
property
or
when
you,
when
you
are
trying
to
get
complex
objects
back
from
a
windows
machine
if
you're
just
using
windows
shell,
if
you're
running
like
a
a
module
like
all
the
modules
that
already
exist,
not
just
windshell
but
all
the
other
modules
that
exist.
B
They'll
return
back
complex
objects,
it's
just
one
shell
that
can
get
a
little
weird.
So
I
want
to
include
that
because
that's
a
useful
way
of
kind
of
dealing
with
that,
if
you're
running
stuff,
so
let's
see
yeah.
So
that
is
the
end
of
this
play.
So
this
particular
playbook
has
two
plays
any
questions
on
any
of
that
before
I
show
you
this
next
one
little
thing.
B
B
Okay,
so
hopefully
this
is
all
useful.
So
let's
talk
about
this
next
thing-
and
this
is
this-
is
the
last
little
bit
before
I
we
go
into
kind
of
phase
two.
I
guess
I
don't
know
what
we're
gonna
call
it
so
again,
I'm
I'm
creating
a
new
play
here
right.
This
was
the
end
and
you
can
tell
it's
a
new
play
because
it's
yaml
because
of
the
indentation
right.
This
goes
all
the
way
out
so
and
it's
and
it
says,
hosts
and
that's
really
something
you
do
with
a
play.
B
B
B
So,
let's
and
let's
look
at
this
uri
module,
which
is
a
very
useful
one,
this
is
kind
of
uri
is
what
you're
going
to
use
when
you
want
to
run
a
rest
api
call,
which
I
hear
all
the
kids
like
these
days.
It's
it's.
The
newfangled
thing
is
rest
api.
So
let's
look
at
the
uri
module.
Mostly
I
just
want
to
use.
I
have
a
note
here
to
myself.
I
want
to
show
you
the
code
snippets.
B
This
is
the
one
the
one
best
useful
feature
of
the
ansible
extension
so
for
anyone
who's
done
a
rest
api.
This
would
be
like
invoke
rest
method
in
powershell.
Basically,
what
we're
doing
this
is
that
kind
of
a
thing
or
curl
in
linux
land.
This
is
kind
of
basically
that
right,
there's
a
lot
of
options.
B
If
you're
familiar
with
that
right,
you
can
do
posts
and
puts
and
gets
an
authentication
of
a
million
different
kinds
and
what
to
do
with
data
and
how
to
do
certificates
so
there's
a
ton
of
options
and
they
may
be
hard
to
remember
now.
The
ansible
documentation
is
really
good
and
I
was
super
stoked
when
I
first
started
googling
stuff
because
it
just
comes
up
bam
and
it's
got.
B
Every
module
has
just
amazing
documentation,
it's
pretty
awesome,
but
if
you
don't
want
to
go
out
to
another
open
up
another
window
because
you
already
got
like
18,
000,
tabs
and
it'll
just
get
lost,
you
can
just
do
the
code
snippets.
So
if
I
start
typing
uri,
you
can
see
it
it.
I
can
do
uri
and
I
can
just
click
that
or
I
can.
I
have
to
snip
it.
So,
let's
look
at
what
that
is,
so
that
filled
out
holy
moly
that
filled
out
a
ton
of
things.
B
C
C
C
C
C
C
Technically,
it
would
like,
if
you
were
to
say,
choco
installed
this
custom
source
being
pip,
but
that
would
require
that
you've
got
chocolatey
on
your
windows,
host
and
python
on
your
windows
host
and
you're,
trying
to
and
install
a
python
package
onto
that
windows
host.
It's
not
going
to
do
anything
to
help
you
manage
your
linux
stuff
or
your
actual
ansible
implementation.
No,
I
was
thinking
for
windows
side,
because
the
the
pip
module
for
ansible
is
linux.
Only
yeah.
A
C
B
B
So
where
was
I
I
was
talking
about
uri,
so
yeah,
it's
a
code
snippet.
It
has
all
the
documentation
for
the
module.
So
you
can
read
the
comments
here,
and
this
is
all
just
from
the
from
the
native
modules.
So
that's
pretty
handy,
so
I'm
not
actually
going
to
fill
this
out
because
it's
not
exciting,
but
I
just
kind
of
wanted
to
show
you
what
a
code
snippet
looks
like
and
how
those
might
be
useful.
B
Now
I
don't
know
how
that
works
with
the
fancy
new
collection
stuff,
where
previously
with
ansible
all
these
modules
were
built
in.
So
when
you
download
an
answer,
you
got
all
these
modules
they're
separating
that
out
now
so
be
more
like
kind
of
like
the
powershell
modules,
where
you
go
and
get
them
when
you
need
them
or
reference
them
externally.
I
suspect
that
this
is
the
way
this
works.
Is
this
only
works
for
the
built-in
stuff?
B
C
As
far
as
I'm
aware,
it
just
uses
ansible
dock
in
the
background
and
we
still
have
the
kitchen
sink
ansible
package,
which
includes
all
the
previous
modules
that
are
now
in
collections.
So
if
you're
doing
some
lance
ball
or
just
your
generic
answer,
then
this
should
work
but
yeah
yeah,
just
straight
back.
C
B
Well,
wonderful,
yeah!
I
don't
know
so
yeah.
Somebody
should
test
that.
I
guess
I
might
test
that
tomorrow.
I'm
curious,
okay!
So
any
questions
on
any
of
this
next
up,
I
was
going
to
go
back
to
some
slides
and
talk
about
some
of
the
specifics
of
connecting
to
windows
systems,
because
it's
a
little
different
than
connecting
to
linux
and
some
of
the
challenges
there
and
then
get
into
some
dsc
stuff.
So
this
would
be
the
medium
level
intermediate
complexity,
part
of
the
the
session.
C
A
This
it's
a
good
job
tonight,
so
I
think
what
we're
gonna
do
here
is
we're
going
to
say
thank
you
to
jeremy
for
all
the
content
he's
presented
so
far.
If
you're,
following
along
at
home,
there's
going
to
be
a
little
bit
more
of
a
deeper
dive
that
comes
up
we'll
put
those
post
on
youtube,
so
look
to
the
youtube
channel
to
pick
up
where
this
continues
on
further
thanks
for
listening
and
we'll
see
on
the
other
side,.