►
From YouTube: CD Foundation Twitch Stream 2020-07-28
Description
Adam, Dewan, and JJ attempt to get a slack webhook added to their original pipeline.
Spoiler: they do, but it's a journey, to say the least. :)
https://twitch.tv/cdfoundation
B
Awesome
and
hi,
I'm
jj,
I'm
a
developer
advocate
for
the
ibm
cloud
2..
I
do
want
to
say
it
was
complete
coincidence
that
we
were
all
part
of
ibm
and
who
have
taken
up
running
this.
This
is
not
an
ibm
thing.
This
is
a
cd
foundation
thing
and
we
just
have
all
very,
very
coincidentally,
are
part
of
the
ibm
company.
B
But
yes,
a
developer
advocate
for
the
ibm
cloud,
and
I
I'm
here
to
kind
of
ask
these
the
questions
of
someone
who
is
not
to
fully
understand
tecton
in
the
grand
scheme
of
things
I'm
very
early
in
my
my
learnings
of
it
and
dewan
and
adam
have
significantly
more
experience
using
techton.
So
hopefully
I
can
be
a
good
conduit
for
people
watching
this.
B
A
A
C
B
I
think
it's
my
ability
to
continue
like
this
cheesy
sounds
to
retain
and
retain
things
one
of
the
one
of
the
one
of
the
one
to
have
a
super
memory.
Basically,
because
the
one
thing
I
just
can't
do
is
remember
things
I
genuinely
can't
do
that,
and
I
would
love
to
have
that
superpower
to
be
able
to
remember
things
in
super
good
detail.
B
That's
a
good
question.
So
so,
if
you
didn't
catch
our
last
stream,
we
built
a
pipeline
using
something
called
the
cat
app
from
from
adam's
repo.
We
were
able
to
get
it
built
and
pulled
in
everything
from
the
catalog
and
then
uploaded
it
into
a
brand
new,
vanilla,
kubernetes
cluster,
on
the
ibm
cloud,
and
then
we
ran
it.
We
didn't
actually
deploy
it
to
or
we
couldn't
pull
it
down.
B
We
couldn't
do
the
actual
integration
test
at
the
end,
but
it
was
a
very
basic
off-the-shelf
pipeline
and
this
this
time
around
dewan,
is
going
to
be
adding
slack
notifications,
because
what
is
something
very
useful
but
to
get
knowledge
of
your
your
pipeline
programmatically,
so
you
don't
have
to
like
you
detect
on
looking
at
the
the
gui
or
anything
you
just
get
the
notices
inside
of
slack,
and
there
was
one
other
thing
we
wanted
to
do.
It
was
kind
of
a
stretch
goal.
What
was
that
red
hooks?
B
That's
right,
web
hooks,
which
is
one
of
the
conversations
we
find
that
most
people
have
is
that
they
want
to
they
get
techcon.
Finally,
up
and
running
they
can
kick
things
off,
but
they
always
want
a
web
hook
from
from
something
like
github.
So
when
something
changes,
it
tickles
the
api,
but
that
requires
ingress
and
a
few
more
advanced
topics
inside
of
kubernetes
and
from
there
we'll
we
can
manipulate
tech
time
now.
There
is
not
an
officially
opinionated
way
to
do.
B
C
B
So
so
dewan
would
you
like
to
share
your
screen
then
from
there
you
can
walk
us
through
what
you're
doing
with
the
web
hooks
and
how
you're
changing
the
things
and
then
we'll
come
to
share
with
my
screen.
So
we
can
use
the
same
the
same,
build.
We
had
last
time
to
start
playing
around
with
web
books
that
seem
reasonable.
C
A
There
we
go,
is
it
okay,
yep
all
right?
So
what
I
was
thinking
is
at
first,
I
can
run
the
the
previous
demo
that
we
did
is
that
well
pushed
up
and
because
we
had
some
room
binding
at
the
end,
which
which
are
probably
I
need
to
fix
on
my
end,
so
once
we
have
that
running,
then
we
can
add,
add
the
slack
piece
and
take
it
from
there
is
that
that
sounds
good
okay.
So,
first
let
me
clone
the
kata.
B
C
Yeah
and
the
interesting
thing
is:
we've
got
a
tecton
pipeline
for
that
under
the
tecton
folder
and
that
basically
contains
off-the-shelf
things
from
texan
catalog.
The
protection
catalog
contains
loads
and
loads
of
little
pre-built
pipelines
and
tasks,
which
you
can
basically
put
together
into
your
own
pipeline
and
do
cool
things
with.
So
I
think
it's
actually
only
tasks,
not
pipelines,
and
we
built
a
pipeline
based
on
all
the
tasks
that
were
in
there.
It
will
basically
clone
the
repository.
C
A
Yep
and
one
of
one
of
the
prerequisite
is
having
a
cool
vendor's
cluster,
any
kubernetes
cluster
might,
in
my
case,
I'm
connected
to
ibm
cluster,
I'm
using
the
the
free
option.
Not
an
open
chip
is
just
a
vanilla,
kubernetes
cluster,
so
I
connect
it
to
that
cluster
just
to
check
if
I
am
indeed
connected
to
the
cluster,
so
this
command
shows
the
version
so
should
be.
A
C
A
B
Right
now,
I'd
like
to
say
to
our
audience,
who
are
who
might
be
watching
at
home
in
the
future
or
or
listening
that
we
just
did
this
to
make
sure
that
we
got
the
exact
same
repeatable
way
of
doing
it.
As
you
can
see
here
in
the
script
here,
we
we
pull
and
we
actually
pinned
it
against
a
very
specific
sha
for
for
the
catalog
repo,
the
catalog
repo
does
move
relatively
quickly,
because
we
have
quite
a
few
different
opportunities
and
enhancement
enhancements
going
in.
B
A
To
make
sure
that's
clear,
yeah,
and
then
I
open
up
the
actual
script
to
see
like
which
of
these
tasks.
We
actually
installed
the
black
message
currently
mechanical,
which
is
our
build
tool
in
this
case,
all
right,
so
the
dependency
is
done
doing
starts
with
the
secrets.
Now
I
I
don't
have
dashboard
installed
here,
but
I
think
on
this
machine.
From
the
previous
run,
we
do
have
the
controllers
yeah.
I
can
see
the
tekken
cli,
so
everything
seems
to
be
installed
here
on
this
machine
right.
Did
you.
A
Right
right,
right:
okay
and
this
being
a
public
github
repository,
I
don't
need
to
worry
about
the
secrets
for
the
github
but
for
pushing
to
the
docker
okay.
So
let
me
add
the
docker
credentials,
so
we
have
so
we
don't
have
the
the
ammo
for
the
docker
secret.
Shall
I
go
there
and
grab
and
create
a
docker
secret.
C
So
these
are
the
tech
time
secrets
right.
This
is
where
you
need
to
use
that
techton.dev
annotation
and
basically
give
it
a
basic
defaulting,
username
and
password
pass
it
to
a
surface
account
and
that's
the
whole
authentication
story
at
the
moment.
I
think
this
may
be
changing
in
future
tech
time
versions,
but
right
now,
this
is
what
we're
going
to
use
to
push
the
docker.
B
C
A
B
And
yes,
that
is
sgc
or
stargate
sg1
or
stargate
atlantis
top
secrets.
If
you
are
a
nerd
like
me,
I'm
in
the
process
of
doing
a
re-watch
of
it,
so
I
thought
it
was
only
appropriate.
It's
my
secret
blocker,
if
you
will,
by
the
way,
if
you
don't
know
just
real
quick,
I
learned
this
the
hard
way
all
of
stargate
used
to
be
on
amazon,
but
as
of
july
20th,
the
licensing
expired,
so
they
removed
it
all
right.
B
They
removed
all
of
stargate
the
whole
series,
all
that
jazz
from
amazon,
and
they
didn't
really
announce
it.
They
just
was
saying
sorry
video
not
available
and
had
to
google
it,
and
it
turns
out
once
again
we
don't
actually
own
anything
anymore
in
this
world.
We
only
license
it
and
because
that's
what
amazon
was
doing
is
licensing
the
videos
so
buy
physical
media.
That's
the
the
lesson
learned
right.
There.
A
B
A
Okay,
okay,
all
right
all
good
all
right!
So
now
I
know
I
know
you
I
know
set
paste.
I
know
I
and
then
oh
wow,
nice,
nice,
nice,
okay.
So
since
I
didn't
change
the
name
of
the
secret,
so
now
we
have
captain
sa
as
the
name
of
the
service
account.
So
if
I
go
ahead
and
apply
dash
f
service
account
dot,
t
demo
now
click
on
that
sa
is
created,
which
has
my
docker
credentials
attached
to
it
all
righty.
So
we
have
the
secrets
created.
We
have
the
service
account
created.
A
A
A
A
C
C
C
B
No
well
wait.
No,
we
did
we
did
didn't.
We
have
to
yeah
the
host
path.
We
just
changed
the
host
path,
because
that
was
something
you
could
do.
We
had
the
local
kind
cluster
that
it
worked.
Fine
on
your
laptop,
but
as
soon
as
we
did
it
for
the
ibm
cloud
because
of
the
default
storage
class,
there
was
not
the
default
storage
class
that
needed
the
host
path
or
something
in
that
effect.
B
Hey
hang
on
hang
on
dewan.
Is
this
a
free
cluster?
Yes,
that's
probably
why
it's
not
doing
it
because
they
wouldn't
attach
pvcs
to
a
free
cluster,
because
then
we're
just
we'd
have
as
big
as
called
yeah
exactly
you
would
you
wouldn't
be
charged
for
the
the
the
pvc
which
could
be
insanely,
expensive.
A
C
B
C
A
Yeah
yeah,
so
let
me
share
my
the
repo
I
have
okay,
so
so
before
before
actually
integrating
slack.
So
this
is
an
independent
piece
that
sends
slack
message
to
your
preferred
slack
channel.
So
this
is
the
the
task
you
you
run
send
to
web
books
like
task,
and
you
have
to
have
your
webhook
secret
in
a
file
and
then
this
will
send
the
message,
the
idea
being
in
our
pipeline
file.
So
if
we
look
at
a
pipeline
file,
so
if
we
scroll
down,
we
have
some
tasks
right.
A
A
C
A
So
this
is
a
typical
example,
so
you
have
your
task
run.
You
give
it
a
name.
You
have
to
refer
the
the
task
rep.
So
in
our
case,
the
the
one
from
the
grab
dependency
that
has
got
to
refer
that
the
the
parameters
are
webhook
secret
is
the
previous
yaml
file,
where
you
actually
add
your
clack
webhook
url,
and
then
in
the
message.
You
can
specify
that
this
is
your
technical
webhook,
but
in
the
in
the
other
file,
webhook
secret.yml.
A
You
have
it
just
a
string
data,
so
one
thing
one
thing
that
is
interesting
is
we
don't
specify
the
exact
slack
channel
with
channel
we're
sending
the
data,
because
that
is
embedded
in
your
slack
web
of
url.
So
when
you
create
a
webhook
url
it
it
asks
that
which
channel
is
it
for?
So
so
you
don't
need
to
pass
that
channel
info.
C
A
C
B
C
A
A
A
Sending
message
to
incoming
web
group
all
right
so
first
one
is
data,
stack
app
and
then
you
enable
the
web
hook
and
then
once
you
enable
the
web
book,
it's
going
to
ask
you
for
which
slack
workspace,
which
slack
channel
and
then
those
are
all
drop
down.
So
once
you
select,
which
one
create
webhook,
it's
gonna
generate
a
stream,
and
that
is
kind
of
your
password,
because
all
you
need
is
that
web
url
stream
to
send
a
post
data
on
your
on
your
channel.
So
we
have
to
treat
that
as
a
password.
C
C
B
A
Yeah
yeah,
so
it's
just
similar
to
like
town
fire,
though
the
boss
seems
that
there's
a
new
result
posted
yeah.
I
created
the
techno,
build
channel
and
then
see
here
whenever
I
added
integration
to
this
channel.
It
sends
a
notification
that
billboard
is
integrated
to
this
channel
and
then
every
time
this
is
a
manual
run
right.
Every
time,
I'm
basically
calling
address
endpoints
every
time.
I'm
posting
that
message.
A
B
B
A
A
B
A
A
A
B
C
B
Well,
it
might
be
ugly,
but
it
is
yaml
and
as
long
as
you
reference
the
task
correctly
like
yeah,
it's
not
it's
like
yeah
you're
gonna
have
to
stare
at
it
like.
As
soon
as
you
get
your
test
built
to
tell
you
the
messages
that
you
want
right
right,
then
you
can
just
kind
of
reference
it
and
know
that
it's
always
at
the
end
of
it
or
something.
I
don't
know.
C
C
A
C
B
Yeah
that
that
that
that
brings
in
an
interesting
question,
where
being
that
this
secret
has
has
obviously
or
this
well,
this
secret
is
a
secret.
You
wouldn't
want
to
push
this
up
into
your
code
because
then
you're
having
secrets
there
is
there
a
way
to
pull
environmental
variables
or
something
like
that,
where
you
can
do
this.
A
Absolutely
so
one
example
is
what
we
do
currently
in
our
build
tool.
Is
we
have
on
ibm
cloud?
We
have
a
service
called
key
protect
so
in
key
product.
You
can
add
any
this
kind
of
api
keys
or
keys
or
secrets,
and
then
your
build
tool,
there's
actually
a
button
is
it
looks
like
a
key
on
ibm
cloud
under
devops,
full
chain
service
click,
and
it
shows
you
all
the
available
keys
within
that
three
product
service
and
you
can
reference
slack
webhook
url.
So.
B
A
C
A
All
right
so
now
that
we
have
the
the
webhook
secret
created
next
step
is
we
need
to
add
that
enough
in
our
pipeline?
So
just
like
we,
so
we
already
have
the
task
now
just
similar
to
what
we
have
here
as
part
of
past
one
within
within
the
pipeline.
We
need
to
add
a
task
and
add
up
a
pams
of
message:
the
name
of
the
web
of
secret
and
the
message.
A
A
B
A
A
B
B
A
C
A
B
C
C
C
C
C
A
C
C
C
C
C
A
A
C
C
C
A
C
C
A
A
C
A
A
B
C
C
A
C
B
C
C
A
A
C
C
C
C
C
A
C
C
B
C
A
C
C
A
A
C
A
C
C
I
think
you
only
had
five
last
time:
okay,
that's
better!
So
now
you
get
pending,
which
is
waiting
on
a
volume
and
you
get
click
container
configure
in
your
little
slack
thing.
So
we
know
about
the
pending:
that's
waiting
for
the
volume,
the
other
one
doesn't
run
after
it.
So
that's
trying
to
run
straight
away.
I
think,
first
of
all,
that's
a
logic
issue
in
our
pipeline,
but
secondly,
what's
this
can
contain
a
configuration?
Let's
describe
that
pod
doing.
A
A
C
C
C
B
I
I'd
go
ahead
and
open
up
the
secret
and
we'll
just
delete
whatever
is
associated
with
it
after
the
fact
right,
because
this
is
all
just
demo
stuff
anyway,
so
it's
not
like
in
the
real
world.
Never
do
this
right
in
the
real
world.
Never
do
this.
We
are
doing
this
because
this
is
demo
aware,
so
we're
trying
to
show
something
off.
A
C
C
B
A
A
C
C
C
A
C
C
A
A
A
A
A
C
A
A
C
A
C
C
C
C
C
C
B
C
B
C
C
C
A
B
C
A
A
C
A
So
re
using
incoming
webhooks.
No,
so
when
I
went
to
slack
selected
apps
I
search
for
webhooks,
this
is
the
first
one
that
comes
like
incoming
web
to
create
an
incoming
web
for
whichever
integration.
So
once
I
go
here,
we
send
data
to
slack
in
real
time.
It
asks
which,
of
course,
I'm
logged
into
to
the
workspace
switch
down
and
which
channel
like
it
needs
that
channel
in
order
to
generate
that
url.
C
C
Although
actually
I'll
tell
you
what,
if
we
put
one
after
here,
we've
then
got
to
fix
the
previous
task,
which
is
failing
so
now
what
I
just
keep
not
run
after
this
gate.
Clone
is
somehow
failing
you
see,
so
keep
it
keep
it
running
as
it
is
for
now.
Okay,
all
right!
I
just
want
to
see
if
a
site
bit
works,
okay,
okay
and
then
do
you
need
channel
now.
A
C
C
A
C
A
B
So
I
think
it's
safe
to
say
we
need
we,
we
we
need
to
write,
write,
something
and
or
kind
of
condense
this
and
then
upstreams
the
lessons
learned
here
to
the
catalog,
because
if,
if
we've
we've
practiced
this
before
right
with
this,
we
did
do
this
live.
But
this
was
seasoned
quote
unquote,
seasoned
tecton
users
and
we
still
had
this
much
trouble.
Obviously,
a
a
a
new
user
would
probably
have
thrown
their
hands
up
a
long
time
ago.
Right.
A
Yeah,
like
the,
if
you,
if
you
have
like
sending
a
message
to
slack,
is
a
pretty
pretty
regular
and
it
shouldn't
have
too
many
ways
to
send
message
to
slack
like
if
you
have
one
way
sending
sending
using
a
channel,
we
don't
need
sending
using
a
workbook
or
or
different
ways,
just
have
one
way
and
one
way
of
with
good
documentation.
I
think
that
that
helped
everyone.
B
C
C
B
It
was,
and
that's
the
beauty
of
streaming
you
you
find
find
things
like
this.
I
I
do
want
to
reiterate
to
our
audience
who
are
watching
that
this
video
will
be
back
up
on
youtube
under
the
cd
foundation,
probably
here
in
the
next
couple
hours.
So
if
you
missed
this
or
just
tuning
in
you
want
to
see
the
way
we
went
you're
more
than
welcome
to
re-watch
this
and
not
the
cd
foundational
twitter
account
will
also
retweet
or
tweet
out
the
link
to
it.
B
B
C
C
Yeah,
if
they
have
questions
yeah,
I
can
help
you
feel
linked
in.
I
can
do
it
through
the
slack
channel.
If
you
go
to
github.com,
I
think
cd
foundation
should
be
like
a
meetups
folder
and
then
there's
a
link
to
the
selection.
So
it's
public
search
now
you
can
join
it,
find
me
in
there
or
linkedin
and
we'll
go
from
there.