►
From YouTube: March 17, 2021 Ortelius and Cloudbuild
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
If
you
want,
whatever
you
use,
whichever.
A
A
I
think
cloud
that'll
be
easier,
especially
since
I
just
did
it
in
my
google
sierra.
Oh
perfect,
google
cloud
yeah.
I
just
did
the
sre
certification
on.
A
B
Yep,
so
let
me
get
us
started
here,
so
we're
going
to
work
with
so
with
artelias.
All
of
our
repos
that
deliver
a
container
are
hooked
up
with
a
cloud
build.
We
also
do
some
github
actions
on
the
back
end
for
security
scanning
of
the
containers,
but
we'll
put
that
aside
for
now
and
just
look
at
the
the
repos
themselves
that
are
that
are
focusing
on
cloud
build,
so
just
a
a
quick
breakdown.
B
So
we're
looking
at
the
website
repo-
and
this
is
the
hugo
server
that
we
go
and
build
the
a
static
version
of
our
markdown.
That
is
contained
in
like
the
content
directory
here.
So
some
of
the
important
directories
around
the
google
cloud
build
piece
that
we
have.
We
have
the
cloud
build
directory,
obviously,
and
that
has
the
yaml
file
we'll
dive
into
that
here
in
a
second
and
then
we
have
our
to
do
the
deployment
we
use
a
helm
chart.
B
B
As
part
of
our
process
and
then
finally,
we
have
our
docker
file.
B
It
gets
well,
it
gets
a
little
more
our
process,
so
the
azure
pipelines
are
a
little
more
difficult
to
set
up,
and
so
I
just
use
the
the
google
cloud
build.
There's
a
really
simple
way
to
set
up
your
process.
Another
one
we
could
have
used
would
have
been
like
the
github
actions
are
gonna,
be
something
similar
get
lab
is
gonna,
be
similar,
the
concept's
the
same,
but
the
first
simplicity
state.
B
I
just
use
google
cloud
build
because
it
seems
to
be
the
most
flexible
and
the
easiest
to
configure
out
of
all
the
ci
tools
we
could
have
brought
in
something
like
captain,
which
is
more
event
driven
techton,
but
for
those
you
need
to
stand
up
a
a
whole
ci.
B
You
know
product
inside
of
your
kubernetes
cluster,
and
that
seemed
like
overkill
for
what
we're
doing
so.
The
the
goal
that
I
set
for
our
cloud,
our
our
build
process
for
atelies,
was
to
check
in
once.
We
check
in.
We
want
to
go
ahead
in
and
create
the
docker
image,
so
we're
going
to
do
a
a
build,
a
basically
a
docker,
build
with
a
tag
and
then
we'll
take
that
image
that's
been
built
and
push
it
to
our
quay
registry
docker
registry.
B
The
reason
why
I
use
quay
is
because
it's
more
stable
and
it
doesn't
have
restrictions
than
docker
hub
docker
hub.
We
used
to
get
into
problems
with
timeouts
and
security
things
you
know,
rate
limiting
and
quay
is
much
more
stable
and
reliable.
C
B
After
we
get
the
image
pushed
to
to
quay,
then
we
want
to
grab
the
image
digest
and
some
other
information
and
we're
we're
going
to
record
all
that
metadata
back
with
basically
artelia's
team,
that's
running
on
the
sas
version
that
deploy
hub
host.
B
So
in
after
we
do
the
the
registration
of
the
new
the
new
image
with
deploy
hub.
We
then
go
ahead
and
tell
deploy
hub,
go
ahead
and
deploy
this
out
to
azure
for
us.
So
that's
like
the
high
level
that
we
have
going
on
and
let
me
bring
up
the
docker
file.
A
Okay,
so
it
sounds
like
something
like
a
diagram
would
be
quite
cool
to
have
as
well.
A
Yeah
got
a
lot
cheaper,
okay,
so
let
me
just
try
and
review
like
we
gonna
get
back
to
you.
So
it
starts
off.
Obviously
with
your
yaml
file,
which
is
your
cloud
build
yaml
file
using
cloud
build.
Do
you
just
go
into
the?
Do
you
just
go
into
the
cloud
shell?
Do
you
just
do
it
by
like
that.
B
Yeah
there's,
let
me
show
you
the
docker
file
first
and
then
we'll
go.
B
A
A
A
B
B
Yeah,
the
compilers,
all
that
stuff
is
going
to
be
at
the
down
on
the
build
layer,
and
so
in
this
process
we
set
our
working
directory
to
build.
We
set
the
a
hugo
environment
just
so
we
turn
on
what
they
call
production
mode
which
allows
us
to
do
like
follow
links,
and
then
this
is
running
in
the
context
of
our
git
repo.
B
Into
this
build
layer,
so
that's
what
that's
doing
is
copying
the
whole
website
in
there,
and
then
we
do
our
mpm
install.
We
install
hugo
and
then
we'd
run
hugo
itself,
which
is
this
last
line,
and
that
actually
takes
the
markdown
and
converts
it
into
a
static
site
and
what
ends
up
happening.
The
static
site
ends
up
in
this
public
directory
underneath
build.
B
So
when
we're
at
the
build
in
this
in
this
build
layer,
all
the
output
is
going
to
be
underneath
build
and
the
directory
that
we're
interested
in
is
just
the
public
directory.
That's
where
all
the
the
translated
static,
content's
been
kind
of
moved
to
for
hugo,
so
that
takes
care
of
our
build
layer,
and
then
we
get
into
our
runtime
layer,
like
you,
said
the
application
layer
and
we're
pulling
this.
This
is
actually
coming
from
docker
hub,
not
my
favorite.
B
C
B
Little
tight,
it
doesn't
have
too
many
cves
in
it.
A
B
A
Of
a
very
small,
what
do
you
call
it?
A
zone
for
attack
yeah
in
terms
of
yeah.
B
Yeah,
so
that's
gonna,
give
us
and
and
we're
gonna
be
hosting
the
static
website
through
nginx
and
with
the
page
speed
module
we
could
have
gone
apache
apache
is
a
little
bit.
Bigger.
Nginx
is
easy
to
configure.
I
love
nginx
yeah.
C
B
Going
to
be
the
that
layer
and
what
we
do
is
this
next
part
the
copy
from
is
saying,
I
want
to
copy
files
from
the
previous
layers,
the
previous
build
steps,
and
so
I'm
copying
the
public
directory
that
was
generated
by
the
hugo
into
the
html
directory
of
nginx.
So
this
is
the
default
directory
for
static
content
for
this
nginx
install.
B
B
Yeah,
so
this
one,
this
one
could
actually
this
one
could
actually
be
technically.
You
could
technically
change
this
to.
B
B
So
I'm
copying
it
from
the
build
layer.
I
could
copy
it
from
the
the
the
git
repo,
but
I'm
just
just
by
chance.
I'm
just
copying
from
the
the
build
layer,
because
the
build
earlier
already
copied
it
into
itself.
So
it's
like
it
works.
So
we're
copying.
C
B
A
couple
of
configuration
files
putting
them
in
the
right
places,
and
then
this
guy
has
a
weird
bug
in
it
that
we
need
to
and
based
on
our
page
speed
configuration.
We
need
to
go.
Do
some
final,
clean
up
on
permissions.
A
A
C
I've
got
one,
I've
got
a
chair,
I
had
I've
got
a
chair,
I've
got
a
chair.
Let
me
let
me
just
share
it
quickly.
Yeah
just
to
see.
A
What
you
think,
sorry,
let
me
just
look
for
it.
I
saved
it
today.
I
found
it
today
because
I
was
reading
an.
C
Article,
it
was
in
my
studies
or
they've
got
their
own
amazing,
github
page
man
with
all
this
awesome
images
and
stuff,
multi-stage
images
with
this
kind
of
stuff
in
and
I
swear,
I
saw
a
page
container
already
like
perfect.
C
B
Where
is
it
okay?
So
one
of
the
things,
even
though
this
is
running
on
google
cloud,
we're
gonna
push
it
to
quay,
because
if
we
were
to
push
it
to
gcr,
we'd
have
to
go
in
and
set
up
a
bunch
of
permissions
and
stuff
like
that
inside.
C
C
C
B
And
you
should
be
able
to
get
to
this
the
the
output
here,
so
you
should
I
I
I
gave
access
to
everybody,
ortelius
team
to
get
to
our
cloud
build
account.
A
B
So
basically,
like
I
said,
we
have
a
few
steps
because
of
the
way
we
need
to
access
our
our
github
repo.
B
So
one
of
the
first
things
that
we
do
is
we
grab
I've
stored
an
ssh
key
in
google
cloud
underneath
their
secrets
and
I
go
ahead
and
basically
copy
that
secret
into
the
root
home
directory
and
set
the
permissions
as
part
of
that
process.
B
So
that
allows
me
to
have
full
ssh
access
to
any
of
my
git
repos.
It
just
avoids.
You
know
security.
Things
like
that.
I
have
a
the
ssh
key
is
is
stored
on.
I
can't
remember
if
it's
organizational
or
on
my
personal
level,
but
basically
it's
a
high
enough
permissions
to
do
whatever
we
need
to
do
on
the
the
the
github
side.
B
Yeah,
it
just
simplifies
the
whole
world
instead
of
trying
to
do
https
with
user
id
passwords
headache,
I
never
use
that.
I
always
use
keys
the
next.
C
B
Yeah
then,
the
next
step
we
do
and
I'll
dig
into
this
in
when
we
get
into
the
yaml
file
is
we
need
to
set
up
some
additional
environment
variables?
We
need
to
expose
new
environment
variables
and
values
to
the
whole
build
process.
B
Then
we
go
ahead
and
log
in
to
quay
and
the
user
id
password
are
also
stored
as
secrets
to
the
google
and
then
finally,
we
do
our
build.
This
is
kind
of
linked
together.
Basically,
we
do
the
build
with
the
tag.
We
do
a
push
and
then
there's
another
special
command
that
we
oh
here.
It
is
where
we
go
and
grab
the
digest.
B
There's
this
crazy
shell
scripting.
You
got
to
do
to
figure
out
the
digest.
One
of
the
weird
things
is:
you
can't
get
a
digest
for
an
image
until
it's
pushed
to
a
container
registry,
it
doesn't
exist
locally.
It
only
exists
when
it's
in
a
registry,
so
after
the
push
you
can
go,
grab
the
digest
and
then
finally,
we
tell
deploy
hub
in
arterius.
C
B
Yeah
so
the
name
description
whenever
we
push
to
a
a
branch,
we're
going
to
go
ahead
and
evoke
the
trigger
there's
the
repo
that
we're
monitoring.
So
this
is
the
link
between
our
commit.
B
B
Now
we
will
be
changing
this
down
the
road
to
look
at
any
branch
and
depending
which
branch
it's
coming
from.
If
it's
main,
we
will
go
ahead
and
push
it
to
the
production
version
of
the
of
the
azure
cluster
and
if
it's
any
other
branch
we'll
actually
push
it
to
a
dev
site.
So
we're
going
to
be
down
the
road
using
istio
to
build
once
and
do
routing
between
a
dev
version
and
a
production
version
to
give
us
that
preview
look,
but
that's
down
the
road.
B
I
always
set
the
the
configuration
I
always
market
this
one.
I
don't
trust
the
auto
detect
just
because
if
somebody
moves
something
around,
I
want
to
be
sure
that
I'm
not
building
something
I
don't
want.
So
I
always.
B
Pick
the
yaml
file,
it's
gonna.
C
C
B
I've
never
had
the
need
to
use
variables,
but
you
can
add
in.
A
Are
you
in
the
ortillius
dub
dub
dub
dub
trigger
you
are
in
that
trigger?
Oh
okay,
that's
one
of
my
shells
on
the
right
trigger
yep.
B
And
you'll
see
you'll
you'll
see
pretty
much
all
the
triggers
are
going
to
be
very
similar.
If
we
look
at
the
like
the
doc
one
doc
again
is
another
hugo
server
dock
we're
pulling
any
branch,
whether
it's
a
maintenance
branch
or
a
main.
It
doesn't
matter
for
this
one
to
push
it
out,
but
the
same
thing.
Looking
at
the
repository
specific
directory,
okay,
now,
the
one
thing
that's
that's
kind
of
a
drag
on
most
of
these
ci
tools
is
because
I
have
everything
you
know
like
the
website
and
pretty
much
all
these.
B
B
B
So
that's
one
of
the
drawbacks.
With
with
pretty
much
all
the
ci
tools.
I've
I've
been
around.
There's
there's
they're
kind
of
difficult.
B
Yeah,
so
this
is
the
the
the
kms
is
to
decrypt
the
clay
user
id
and
password.
A
Yeah
for
the
query,
by
registering
to
log
in
there.
A
B
B
B
B
A
B
Nobody
can
ever
decrypt
it.
A
B
B
B
So
we'll
kind
of,
if
you're
ready,
we
could
start
at
the
top
and
kind
of
walk
through
the
different.
A
Steps,
so
let
me
try
and
you
can
you
can
just
stop
me
where
I'm
going
wrong?
Okay,
so
so,
basically,
obviously
I
would
have
climbed
the
repo
down
onto
my
machine
right.
I'd
make
my
changes
whatever
they
would
need
to
be
yep,
whether
that
be
in
the
cloud
yammer
file
or
the
dockerfile
I'd
assume
you
never
need
to
change
the
home
file
right
because
that's
a
template.
It's
a
template
that
you're
using.
B
Yeah
or
somebody
went
and
changed
your
content,
yeah.
A
A
Start
with
your
change,
you
plan
you've
planned
the
repo
I'm
just
going
to
type
this
faster
speed
cleaner
onto
your
machine.
You've
made
the
changes
made.
Whatever
changes
you
wanted
to
make,
then
you
push
them
up.
You
guess
you,
I
guess
you
kind
of
create
a
merge
request
and.
B
A
A
Yes,
sorry,
your
pull
request
comes
through,
then
it
gets
merged
and
then
cloud
will
should
kick
off
right.
B
Yep
and
because
the
way
we
have
the
the
branch,
we're
monitoring
for
the
trigger
is
main
when
somebody
does
a
push
to
any
other
branch
it'll
get
ignored.
But
when
we
do
the
pr
merge
from
like
another
fork
that
gets
merged
onto
main
and
that
causes
a
new
commit
and
that's
that's
what
will
trigger
it?.
C
A
A
B
So
it's
going
to
start
it's
going
to
start
running
the
steps
in
the
cloud.yaml
file.
A
Yeah
so
it'll
be
exactly
cloudcore.yaml,
it's
kicked
up
and
then
that
creates
a
new
and
you've
got
a
new,
a
new
image
from
the
container
right
to
the
container
registry.
Is
it
going
to
get
pushed
to
key
now.
B
So
what
will
happen
is
we'll
just
kind
of
walk
through
the
individual
steps.
First,
we're
going
to
get
the
ssh
key
for
us
to
talk
to
github
and
then
we're
going
to
set
up
environment
variables
now,
one
of
the
weird
things
with
with
cloud
build
and-
and
it
happens
with
a
lot
of
these
tools-
there's
no
way
to
pass
parameters
or
environment
variables.
From
from
like,
I
can't
set
an
environment
variable
like
at
the
job
level.
B
B
So
this
step
cloud
build
sh
has
all
these
environment
variables
that
are.
I
wanted
to
find,
and
one
of
the
things
like
I'm
doing
here
is
getting
the
last
the
number
of
commits
to
the
repo.
So
I
can
use
that
as
like
a
build
number,
because
cloud
bill
gives
you
this
weird
build
id.
It's
like
a
hex
s.
My
id
is
kind
of
worthless,
so
we
go
and
count
the
number
of
commits
to
the
repo.
So
we
use
that
as
the
build
number
and
we
that's
gonna,
help
us
create
our
image
tag.
B
So
one
of
the
tricks
I
did
was,
I
took
all
of
the
let's
see
here,
so
I'm
gonna
go
clean
up.
One
of
the
things
I
need
to
do
is
the
one
of
the
problems
is
in
order
for
me
to
get
the
count
of
the
commits
in
the
repo
google
initially
gives
me
what
they
call
a.
B
I
want
to
show
you
it's
like
a
short
or
a
small.
It's
like
the
very
just
the
branch
it
gives
you.
It
doesn't
give
us
any
of
the
history.
So
it's
like
a
quick
clone
that
it
does
and
that
quick
clone
is
pretty
much
worthless
because
you
can't
get
any
get
information
out
of
it.
It's
literally
just
like
copy
the
tip
of
all
the
files
and
give
me
no
history.
B
B
B
And
then
what
I
do
is
I
go
ahead
and
prepend
the
word
export
in
front
of
all
those
variables
and
what
ends
up
happening
is
I
create
a
sh
file
that
will
have
export
component
application
equals
blah
blah
blah,
and
so
this
gives
me
a
way
to
define
any
variables
that
I
want
in
an
sh
file
and
what
ends
up
happening
then,
is
when
we
go
on
to
the
next
step.
B
Is
one
of
the
first
things
I
do?
Is
I
source
that
in
I
do
the
period
in
front
of
the
the
period
space
in
front
of
it,
and
what
that
does
is
when
I
run
that
that
shell
script
any
environment
variables
that
are
contained
in
that
shell
script
are
end
up
in
the
current
shell.
So
what
that
does
is
allow
the
doctor
login
to
have
access
to
all
those
environment
variables.
B
B
So
one
of
the
things
we're
going
to
do
here
is
we're
going
to
log
into
quay
and
we're
going
to
set
up
by
default.
The
login
wants
to
put
it
in
your
slash
root
like
docker
directory
or
something
like
that,
and
I
told
it
to
put
it
in
a
different
directory.
B
I
want
it
in
the
workspace
root
where
my
docker
config
is
going
to
be
used
just
as
a
convenience,
so
I
can
keep
track
of
because
what
ends
up
happening
between
one
step
to
the
next
step,
things
get
lost,
but
workspace
is
persisted
across
the
steps.
So
that's
why
I
had
to
take
the
output
of
the
docker
login
for
the
docker
config
put
in
the
workspace.
B
B
So
that's
going
to
get
it
up
to
the
registry,
because
we've
already
done
our
login
and
then
we
again
we
grab
our
our
environment
variables
and
we
want
to
add
the
export
digest,
append
it
to
the
cloud
build
as
well.
So
this
is
going
to
go
ahead
in
and
query
the
docker
registry
and
get
us
our
digest
number
and
that's
going
to
export
that
as
the
the
digest
in
our
sh
file.
B
So
this
allows
us
to
manipulate
our
environment
variables
that
are
getting
passed
along
from
step
to
step,
and
then
we
get
into
arterius
deploy
hub
where
we're
going
to
tell
the
sas
version.
The
ortiz
team
that
we
have
a
new
component
that
we're
updating
and
all
the
parameters
that
go
with
that
word
wrap
that
so
things
like
like
the
the
component.
That's
coming
up
from
the
top
here
that
we've
defined
as
you'll
see.
A
B
And
one
of
the
things
that
I've
turned
on
here
is
I've,
given
it
a
deployment
environment
and
when
we
give
the
this
python
script.
Basically
a
parameter
says
deploy
to
this
environment:
we're
going
to
actually
update,
create
a
new
version
of
the
component
and
then
create
a
new
version
of
the
application
with
that
that's
consuming
that
component
and
then,
once
all
that's
done
we're
going
to
deploy
it
out
to
our
environment
and
that
all
happens
in
that
one
giant
and
there's
other
things
that
we're
doing
we're.
B
Recording
like
the
git
repo,
the
git
tag,
the
branch,
the
docker
tag,
all
that
ends
up.
C
B
Actually
doing
the
deployment
and
because
we
have
that
helm
chart
deploy
hub,
is
using
the
helm
chart
to
go
ahead
and
execute
the
deployment
it.
Actually
we
wrapper
the
helm
with
ansible
says:
how
can
we
see
some
as
ansible
stuff
it?
So?
Basically,
we've
logged
into
our
our
client
deployable
is
connected
to
has
information
about
how
to
connect
to
the
cluster.
A
B
B
And
there's
like
all
the
information
that
we
have
available
and
that
ends
up
pushing
it
out
to
our
our
azure
cluster.
And
if
we
look
at
our
components.
B
We'll
see
this
is
the
cloud
build
url
like
I
said,
there's
that
funky
build
number
from
cloud
bill
totally
worthless,
yeah.
B
That's
just
how
they
refer
to
it.
There's
the
home
chart
that
we're
going
to
use.
This
is
the
quay
registry
that
we
pushed
to
there's
the
digest
the
tag
that
was
used,
the
git
commit
where
the
repo
is
and
how
we're
referencing.
You
know
which
tag
we're
working
off
of
main
or
a
brand,
a
feature
branch.
C
B
We're
able
to
go
ahead
and
get
that
ex.
You
know
the
all
that
information
now
is
available
in
basically
artelias.
A
A
B
Actually,
because
this
is
a
we're
running
the
the
sas
version
of
of
deploy
hub,
I
actually
have
a
reverse
proxy,
that's
running
on
one
of
our
local
machines
here
that
allows
me
to
do
the
deployments,
so
the
reverse
proxy
I'll
show
you
what
happens.
B
B
There's
the
resource
group,
the
tenant
id
the
context
that
we
want
to
use.
So
all
this
is
allows
me
to
go
ahead
and
connect
up
to
azure.
If
we
go
back
to
this
guy.
B
A
B
Yeah
we
were
given
25
grand
worth
of
credits
in
azure.
B
I
need
this,
I
need
to
set
it
up,
so
deploy
hub,
got
those
credits,
and
I
need
to
reapply
for
ortelius
as
an
open
source
to
get
the
credits.
A
I
see:
okay,
that's
smart,
okay,
but
and
the
cdf
so
now
that
we
folded
the
city
up.
How
does
that
affect
us?
Do
we
will
we
move
out
of
the
zero
ever?
Do
they
have
their
own
setup?
Can
do
they
give
us
anything?
I.
B
Think
so
I
that's
what
I
gotta
check.
I
think
google
has
given
the
cdf
credits.
C
B
B
And
because
of
the
way
at
this
level,
with
the
ploy
hub
doing
the
deployment
and
we
can
actually
go
and
change
cloud
providers
just
at
the
deploy
hub
level.
Basically.
B
Yeah,
so
all
you
have
to
do
is
go
in
and
change
instead
of
aks
credentials.
I.
B
B
I
can
just
literally
change
it
to
eks
or
whatever
cluster
I
want
to
deploy
to
and
all
the
everything
everything
under
the
covers
will
be
handled
automatically.
B
So,
even
at
this
level,
this
is
still
you
still
end
up
with
a
cloud
build
diamol
for
every
repo.
B
Like
way
to
template
this,
you
know
so
that's
one
of
the
drawbacks.
With
these,
like,
I
said
the
ci
tools,
you
have
to
have
what.
A
B
Understanding
correctly
yeah
exactly
so,
if
you
look
at
so
some
of
the
like
some
of
the
microservice
repos
and
some
of
the
samples
you'll
see
like
a
dot
circle,
ci
directory,
so
instead
of
cloud
build,
I've
enabled
I
did.
I
had
to
do
some
demos,
so
I
had
a
circle
ci
directory
that
has
a
very
similar
yaml
file
within
the
the
concept
of
steps
and
things
like
that,
pretty
much
all
of
them.
You
have
to
do
this
work
around
with
pushing
to
a
sh
file.
A
Yeah,
it's
complex
man
chief,
just
what
you've
done
is
incredible.
Yes,
it's
definitely
beyond
my
I've
learned
a
whole
bunch
from
you
know
how
you
do
things
no
seriously.
It's
incredible
man.
B
So
this
is
just
some
of
the
tricks.
I
found
every
every
ci
tool,
whether
it's
me
circle,
ci
or
cloud
build
or
I'm
trying
to
think
like
tekton
or
nebula.
A
B
Nebula,
they
all
have
a
concept
of
a
workspace
and
that's
going
to
be
persistent
from
one
step
to
the
next
step.
And
that's
where
you
just
get
to
save
stuff.
B
C
A
A
A
Oh
cool
cloud:
buildbot
awesome!
Oh
yes,.
A
B
That's
under
billbot
results
and
that
will
take
you
right
to
the
console
with
the
log.
A
B
A
Okay,
so
wow,
I
learned
a
huge
amount
now
and
now
I
actually
understand
how
ortillius,
like
the
higher
the
whole
process
fits
together.
I've
got
a
picture
in
my
head
now,
which
makes
it
help
me
a
little
bit.
B
Can't
remember,
which
way
exactly
where
how
I
thought
it
was
on
the
claw
belt
side,
maybe
in
settings.
A
Be
a
there
might
be
a
separate.
I
can't
remember
now
on
google,
where
you
do
that
there
is
probably
a
there
is
yeah.
There
is
a
place
where
you
set
up
all
this
notification.
Stuff
yeah
might
be
under
monitoring.
Maybe
I
remember
doing
stuff
in
monitoring
where
you
can
set
up
different
types
of
notifications
for
slack
email
cheapest
way.
Was
it
no?
Let
me
just
type
it
in.
A
A
Okay,
so
in
terms
of
the
blog,
do
you
want
me
to
would
you
prefer
me
to
draw
a
diagram
with
like
a
talk,
have
a
diagram
or
have
because
I'm
very
visual,
so
I.
A
A
diagram
with
words,
you
know
what
I
mean
like
talking
with
the
diagram
like
writing,
so
I'm
going
to
put
something
together
and
then
I'll
share
it
with
you
and
then
you
and
tracy
can
like
say:
okay,
like
change
this
change
that
or
whatever
you
know
make
it
look
like
this.
I
mean.
I
know
you
guys
have
probably
got
people
that
can
make
it
look
better,
but
I
actually
really
love
doing
this
kind
of
stuff
yeah.
B
Yeah,
so
do
do
a
diagram
with
some
wording
around
it.
You
know-
and
I
think
that
would
be
you
know,
kind
of
explaining
each
step
and
why
why
we
did
it.
A
Exactly
exactly
and
then,
if
I'm,
if
I'm,
if
I'm
a
bit
gray
on
some
stuff,
you
can
just
help
fill
me
in
where
I've
need
to
be
used.
I
don't
know
the
correct
the
correct
terms.
You
know
I
don't
so
I
don't
confuse
people
because,
like
I'm
just
on
one
thing,
it's
like
the
term
of
devops
everyone's
like
in
south
africa,
is
called
devops
a
role,
but
it's
not
a
role.
It's
actually
a
culture
right.
C
A
C
A
A
A
Just
go
to
your
search
bar
at
the
top
here.
I
just
type
it
in
there
every
time,
because
I
couldn't
be
bothered
to
look
on
the
left
because
I
always
get
always
get
so
lost.
I
know.
A
C
A
A
A
little
simple
and
then
you've
got
your
there.
You've
got
your
dependencies,
okay,
very
cool,
so.
B
Literally
one
of
the
things
that
was
weird
was
some
of
the
json
data
that
you
got
didn't
give
me
everything
I
needed
and
there
was
like
no
way
to
to.
A
A
B
As
part
of
the
data
that
was
coming
in
so
basically,
you
know
we're
gonna
take
the
data
coming
in
from
the
cloud
build.
We
change
it
from
base64
to
a
string
and
then
we
can
take.
B
So
there
are
some
things
like
that.
Didn't
exist
like
that.
I
wanted
like
some
of
the
environment
variables
like
I,
they
were
they
weren't
exposed.
I
had
to
make
it
generic.
C
B
And
then
that's
all
I
put
out
there
was
so.
This
is
how
I
hooked
in
once.
Everything
was
done
that
the
that
cloud
build
was
completed,
that
we
went
and
poked
discord
through
that
web
hook
with
the
update.
B
That
wants
to
do
a
slack
poke.
You
could
do
do
that
and
there's
examples
instead
of
discord.
A
B
Is
you
end
up
passing
a
a
certain
format
of
the
you
know,
basically,
a
certain
json
payload
over
to
the
web
hook,
and
this
is
the
the
format
for
discord.
You
know,
content
embeds,
title
description:
color
slack
has
a
couple
different
parameters.
A
Sorry,
do
you
can
I
ask
you
a
question
yeah,
not
just
kind
of
it's
not
kind
of
this.
Is
these
guys
where's,
my
this
flipping
lost
zoom.