►
From YouTube: Keptn Community & Developer Meeting - May 20th, 2021
Description
Meeting notes: https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit
Sign up to our community newsletter: https://keptn.sh/community/newsletter/
Learn more: https://keptn.sh
Get started with tutorials: https://tutorials.keptn.sh
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/keptn
Follow us on Twitter: https://twitter.com/keptnProject
A
All
right,
yeah,
hi
everyone
and
welcome
to
the
next
episode
of
the
captain
dev
meeting
as
usual
today.
Is
it
it's
more
focused
on
the
features
and
capabilities
that
have
been
implemented
from
the
captain
core
team,
meaning
that
we
will
go
over
a
couple
of
pull
requests
and
issues
that
were
implemented
in
the
last
couple
of
last
two
weeks?
A
But
let's
just
have
a
brief
look
at
the
agenda.
There
are
no
action
items
listed
here
and
but
still
the
the
shout
out
and
the
question
for
a
code
owner
of
our
repository
for
the
notification
service.
A
A
As
usual,
you
will
find
them
on
github,
but
let
me
just
point
out
the
main
features
that
are
released
by
this
release.
First
of
all,
we
allow
now
customization
of
the
remediation
sequence,
meaning
that
before
captain
odot
8.3,
you
were
not
able
to
customize
your
remediation
sequence.
You
had
to
use
that
one
that
was
built
into
the
remediation
service,
and
now
you
can
model
it
via
the
gps
configuration
and
for
doing
that
or
when
you
want
to
also
upgrade
from
captain
0.8
to
2
8.3,
without
losing
the
capabilities
of
the
remediation
sequence.
A
Then
it's
now
necessary
that
you
copy
paste
this
sequence,
which
is
yeah
shown
here
into
your
shipyard
and
into
this
stage
where
you
want
to
enable
this
remediation
sequence
and
then
the
workflow
works
as
laid
out
here.
A
This
is
here
yeah
by
an
additional
property,
but
we
will
hear
a
little
bit
more
about
that
feature
in
a
second,
and
with
this
sequence
in
place,
you
have
still
the
capabilities
of
auto
remediation
and
fixing
or
resolving
problems
that
occurred
for
a
service.
A
Another
change
or
improvement
was
that
we
removed
the
limitation
of
the
service
name
from.
I
think
it
was
15
characters
now
43
correct.
We
lift
it
to
43
characters,
meaning
that
you
can
now
have
services
that
have
a
service
name
up
to
40,
43
jars
and
for
all
of
those
that
are
using
custom,
helm,
charts
and
are
deploying
those.
A
We
now
provide
the
feature
that
allows
you
to
explicitly
define
the
public
and
the
local
deployment
url,
and
therefore
you
can
make
use
of
this
endpoints.yaml
file.
You
provide
in
the
caption
repository,
and
this
one
is
then
used
to
deploy
your
custom
helm
chart
by
using
the
endpoints
defined
in
this
file,
all
right
yeah.
A
Those
are
the
three
key
announcements
of
the
upcoming
release
and
as
soon
as
you
have
upgraded,
we
are
looking
for
feedback
and
also
your
ideas
or
thoughts
on
the
features
that
are
coming.
B
Yeah,
thank
you,
okay.
So,
let's
start
with
something,
that's
related
to
the
release,
notes
and
there's.
Basically,
three
pull
requests
listed
here
for
the
update
of
the
slo
sli
file,
the
shipyard
yaml,
the
tutorials
and
the
spec.
I
only
show
the
one
for
the
examples,
because
the
the
other
ones
are
basically
yeah.
They
go
hand
in
hand
by
what
I'm
showing
you
here
so
essentially,
what
do
you
need
to
change?
B
In
our
examples,
it's
the
production
stage
and
last
but
not
least,
if
you
are
using
dynatrace,
there
is
a
new
sli
available
or
actually
the
sli
itself
is
not
new,
but
the
new
workflow
that
we
have
allows
a
good
usage
of
it
and
it's
called
problem
open
and
that
essentially
allows
you
to
query
the
number
of
open
problem
events
and
we
force
this.
In
our
example,
we
force
this
to
be
zero,
so
basically
the
evaluation
step
you
see
here
after
the
action
has
been
executed.
B
You
wait
10
minutes
and
the
evaluation
step
will
then
make
sure
that
problem
open
equals
to
zero
and
if
it
doesn't
equal
to
zero,
then
our
implemented
loop
here
well
starts
again
and
well.
The
remediation
action
get
executed
based
on
that
loop,
but
that's
something
that
has
been
presented
in.
I
think
two
weeks
ago
by
floriano
band.
A
Christian
yeah,
the
the
comment
you
made
on
the
api
version.
Currently
it's
not
documented
in
the
upgrade
instructions,
but
we
should
add
them
there,
yeah
right,
okay,.
B
So
I
don't
think
it's
it's
let's
say
blocking,
but
it
would
be
best
practice
that
you
specify.
C
B
Here
all
right,
yeah,
as
I
said,
there's
also
a
documentation
update,
but
I
want
to
show
you
some
some
quick
hints
in
our
documentation,
because
I
had
to
change
it
a
little
bit
so
when
you
enter
the
docs
for
captain
0.8
and
you
click
on
manage
there
is
this
part
that
says
shipyard,
and
this
didn't
this
wasn't
really
defining
or
declaring
how
the
shipyard
looks
like
and
what
it
is.
B
It
was
rather
a
guide
on
how
to
update
the
shipyard
and
I've
converted
it
into
a
more
well
I've
posted,
more
definitions
and
and
stuff
like
that
in
here.
So
this
should
be
your
entry
level
when
you're
interested
in
how
to
write
your
own
shipyard
and,
looking
at
my
last
comment,
we
also
need
to
update
this
here.
B
B
This
is
how
you
define
a
sequence
in
a
stage
or
in
multiple
stages
and
link
them,
and
there
are
some
reserved
tasks
if
you
think
you've
seen
this
before
you're
right,
but
this
is
something
that
was
hidden
in
the
continuous
delivery
documentation
here.
For
multi-stage
delivery,
and
that's
why
I
moved
it
out
and
with
that
change
I
also
added
a
little
bit
of
docs
for
the
remediation
part.
That
johannes
also
has
already
shown
us
in
the
release
notes.
B
So
when
you
go
here
to
automated
operations
and
remediation
config,
we
are
also
providing
a
shipyard
again
with
the
wrong
api
version,
but
we're
also
providing
a
shipyard,
in
this
case
just
a
single
stage
production
with
a
remediation
sequence
in
here.
So
if
you
just
want
to
try
out
this
new
feature,
how
do
remediations
work,
then?
B
B
Then
I
did
some
fixes
to
the
dyna
trace
slice
service
in
with
regards
to
a
response
time
degradation
that
I
detected
in
it.
It's
not
worth
looking
at
the
code.
It's
essentially
just
some
go
routine
that
I'm
calling
now
instead
of
executing
the
function
directly,
but
it
did
solve
the
response
time
degradation.
So
yeah
the
next
one
I
want
to
show
this
is
the
switching
projects
without
losing
context
in
captain's
bridge.
B
So
what
did
you
do
before
you
go
to
your
project
and
you
go
to
the
sequence
screen
and,
like
you
scroll
through
some
of
the
sequences,
and
then
you
decide,
you
want
to
go
to
a
different
project
and
so
like,
let's
say
I
go
to
sock
shop
and
what
would
happen
is
that
you
jump
back
to
the
so-called
environment
screen
and
I
have
adapted
this
little
drop
down
here.
B
So
if
you
are
on
a
sequence
screen,
for
instance,
and
you
go
to
the
stock
shop
to
another
project,
then
you
stay
on
the
sequence
screen
and
you
you
basically
get
immediately
all
the
sequences
here
and
the
same
is
obviously
true
for
the
services
screen.
I
think
this
one
is
better
because
you
can
see
here
the
services
that
are
running
I
can
go
to
another
project
and
it
immediately
updates
the
services
that
I'm
seeing
here.
B
Okay,
then,
this
one
johannes
also
already
said
something
about.
I
still
want
to
show
you
a
little
bit
of
the
details
about
this
change,
so
it
might
sound
weird.
We
allow
service
names
of
up
to
43
characters
right.
So
what's
behind
that,
there's
a
limitation
in
help
charge
and
I
think
it's
it
basically
goes
way
back
to
an
old
kubernetes
version
where
your
service
names
needed
to
be
below
53
characters
due
to
some
dns
limitations.
B
Unfortunately,
this
limitation
has
still
carried
on
to
modern,
kubernetes
and
helm,
and
it's
not
possible
to
lift
this,
but
then
you
might
see
okay,
53
characters,
why
not
53?
And
why
do
we
have
43?
So
we,
when
we
do
blue
green
deployments,
we
generate
service
names
and
these
service
names
have
the
name
dash
generated
in
it.
And
that's
if
you
can
count,
I
think,
that's
that's
10
characters,
if
I'm
not
mistaken,
so
that's
an
additional
10
characters.
We
need
to
reserve
for
captain.
B
Nevertheless,
with
my
change,
we
still
use
this
template,
but
we
fall
back
to
this
template
step
by
step.
If
the
service
name
is
too
long.
So
this
we
need
this
still
to
be
backwards
compatible.
So
everyone
that
has
projects
and
stages
and
services
that
fit
so
far
they
will
still
fit
in
this
schema,
and
if
you
create
a
new
project
with
a
very
long
service
name,
then
this
schema
will
be
used.
B
Okay,
last
but
not
least,
there
is
one
more
change
for
captain's
bridge,
so
the
index.html
file
was
delivered
with
a
caching
header
of
seven
days.
I
just
want
to
show
you
the
code
change,
because
this
might
appear
in
the
future
version
again,
and
I
think
it's
quite
okay,
that
we
look
into
it.
So
the
fix
is
easy.
The
fix
is
like
overriding
the
set
headers
function
here
for
express
and
saying.
If
your
file
ends
with
an
html
extension,
then
set
the
header
cache
control
to
to
no
cache
else.
B
It
would
have
the
the
max
age
of
one
week
or,
as
it
is
here
max
age
of
one
week,
which
is
fine,
if
you
think
about
static
files
like
images
javascript,
css
files,
because
as
they're
built
with
angular
and
with
webpack,
they
have
a
cache
buster
in
the
name
anyway.
So
that
should
work
fine,
but
for
the
index.html
it
doesn't
have
a
cache,
buster
and
probably
also
other
html
files.
They
they
need
to
be
delivered
without
being
cached.
D
I'm
going
to
present
you
two
per
request
from
my
side
for
the
captain's
bridge.
One
is
about
the
remediations
that
are
showing
in
the
bridge
due
to
the
changes
and
the
remediation
workflow
yeah.
We
had
to
fix
some
things
in
the
bridge
and
especially
everywhere.
D
The
problem
or
the
remediation
is
visible
to
the
user.
In
this
case
the
environment
screen
in
the
service
screen.
We
see
also
the
status
and
the
sequence
screen,
which
shows
the
remediation
sequence.
I
have
here
an
environment
where
I
have
a
yeah
in
my
production
environment.
D
Currently,
as
we
can
see
a
remediation
actually
running
and
as
you
can
see
here,
the
problem
is
failure
rate
increase
on
web
service
and
there
is
an
action
running
toggle
feature
flag,
enable
promotion
to
off,
and
since
this
is
still
running,
there
is
no
evaluation
result
here
there.
So
there
we
showed
a
loading
icon
and
in
case
that
there
are
multiple
remediation
steps,
actions
actually
implemented,
and
the
first
one
is
already
finished
and
you
would
see
the
result
of
the
first
one
here
and
that
the
second
one
is
running.
D
Actually
I,
as
we
can
see,
it
seems
that
there
is
a
problem
here.
I
already
know
where
this
is
coming
from,
but
yeah
we
will
see
it
in
the
sequence
screen
in
a
minute
also
in
the
services
screen.
When
I
click
on
the.
D
Service,
oh
yeah,
of
course,
now
it's
not
working
correctly,
probably
because
of
the
problem
event
that
was
there
yeah.
It
should
also
show
here
the
latest
evaluation
result,
which
would
yeah
indicate
the
problem
that
we
have
currently
there
and,
let's
have
a
look
in
it
yeah.
We
have
here
my
remediation
action
that
was
running
and
we
had
not
yet
the
evaluation.
D
So
that's
why
the
service
screen
was
also
not
showing
the
correct
result
and
the
problem
that
we
have
here
also
the
problem
itself
was
yeah
triggered
by
prometheus
service,
and
this
one
is
also
showing
up
here
in
the
environment
screen,
which
is
why
we
have
here
now
two
and
now
it's
going
three
entries
so,
as
you
can
see
for
the
remediation
itself,
the
first
action
didn't
pass.
It
shows
me
the
evaluation
result
and
now
the
second
action
is
running
here,
yeah
at
the
moment.
A
I
mean
I
didn't
get
it
to
why.
I
do
have
two
problems
here
or
a
while.
D
Actually,
that's
a
small
bug
that
we
yeah
see
right
now.
I
I
haven't
seen
it
before.
D
Also
the
problem
event
itself,
which
is
here,
is
identified
as
a
remediation
or
as
a
problem
in
the
environment
screen,
and,
of
course
this
is
started
but
never
finished,
and
since
it's
not
finished,
it's
also
showing
up
in
the
environment
screen,
but
this
needs
to
be
filtered
because
this
problem
event
itself
triggers
a
remediation
sequence
and
therefore
I
need
to
to
filter
those
problem.
Events
in
the
bridge,
so
it
doesn't
show
up
here
again
yeah
here
we
can
see
it.
D
This
is
actually
the
problem
event
which
is
not
finished,
of
course,
because
yeah,
there
is
no
finished
event
for
the
problem
itself,
but
the
problem
event
will
trigger
a
remediation
sequence
and
that's
the
one
that
should
show
up
here.
D
D
One
thing
that
we
enhanced
here
is
the
visualization
of
this
staged
tiles,
as
you
have
already
seen
here
in
my
running
bridge,
the
size
of
this
tiles
is
also
larger,
now
and
fixed.
So,
for
example,
if
you
see
here
three
stages,
you
get
a
scroll
bar
and
yeah,
so
you
have
more
details
visible
here
and
we
have
more
space
for
the
service
name,
the
version
and
also
the
latest
sequence
that
was
executed
in
this
stage.
D
For
this
artifact,
also
in
case
that
you
have
the
same
trigger
for
multiple
stages,
it
will
stack
them,
as
you
can
see
here
in
this
screenshot,
for
example,
we
have
here
three
production
environments,
a
b
and
c,
and
they
all
have
the
same
parent,
so
they
all
have
the
same
trigger
in
the
shipyard
the
ammo
configured,
then
the
bridge
will
align
them
and
stack
them
and
show
that
they
are
in
parallel.
D
One
more
thing
that
I
would
like
to
mention
is
that
during
this
sprint
we
have
discussed
and
also
provided
already,
a
suggestion
for
customization
of
captain's
bridge
where
we
will
allow
to
customize
several
parts
of
the
bridge,
like
the
logo,
background,
colors
and
the
title
of
the
application
itself.
D
This
was
a
research
task,
and
now
we
will
have
yeah
follow-up
issues
to
yeah,
provide
the
necessary
steps
and
documentation
how
to
customize
the
captain's
bridge.
So
this
is
ongoing.
A
Okay,
I
was
working
on
one
issue
in
this
print,
which
is
about
the
upgrade
from
older
data
2
to
auto
data,
and
I
want
to
actually
emphasize
and
mention
a
couple
of
things
I
already
did,
but
again
at
this
time,
it's
important
that
you
also
update
the
shipyard
in
case
you
want
to
have
remediations
enabled
and
therefore
we
provide
the
instructions
here
in
step.
Two
step:
one
is
the
the
normal
upgrade
where
you
download
the
captain.
Cli
you
do.
The
captain
upgrade
command
and
control
plane
is
then
upgraded
automatically.
A
This
is
what
you
are
used
to
and
now
in
step,
two
yeah,
it's
all
about
updating
the
shipyard
configuration
and
what
you
have
to
do
technically,
basically,
is
that
you
copy
paste
this
snippet,
which
defines
the
remediation
sequence.
A
A
You
go
there
and
yeah
you
edit
this
file
and
in
my
particular
case
I
want
to
add
this
remediation
sequence,
to
my
production
environment
for
customer
a
and
you
just
do
a
paste
copy
paste
and
one
thing
you
have
to
change.
This
is
the
name
of
the
stage
and
in
my
case
it's
the
production,
minus
customer
minus
a
stage,
and
this
is
what
you
have
to
adapt
here
and
when
you
are
done
or
when
this
is
done,
you
just
save
it
and
you're
good
to
go
for
having
remediations
enabled
then
for
this
particular
environment.
A
A
A
A
Oh
didn't
I
stop
here
sorry
here.
E
Okay.
Today,
I
want
to
show
you
a
free
pro
request
that
I've
worked
on
in
this
sprint,
so
the
first
one
is
for
the
sheepdog
controller,
support
sequence
loops.
So,
let's
quickly
go
to
the
issue
to
see
what
that's
all
about,
so
that
was
actually
a
feature,
that's
necessary
for
supporting
the
new
remediation
sequences,
because
the
way
it's
going
to
work
is
basically,
we
have
the
remediation
gamma
that
will
be
used
by
the
remediation
service
and
here
for
a
specific
problem
type.
E
E
If
we
have
a
look
at
this
sequence,
we'll
send
out
the
get
action
task
which
will
be
picked
up
by
the
remediation
service,
also
with
the
name
or
the
the
title
of
the
problem,
we'll
check
the
title
and
see
which
action
it's
going
to
which
action
should
be
executed
first,
that
one
in
that
case
it
will
return
the
first
action
scaling.
E
Then
that
action
will
be
executed
by
whatever
service
will
be
responsible
for
handling
this
task
and
then,
after
some
time,
that's
missing
here.
So
we
do
have
now
the
possibility
to
define
waiting
time
before
the
next
task
is
going
to
be
started.
So,
for
example,
if
you
define
a
value
of
10
minutes
here
after
10
minutes,
the
evaluation
will
be
triggered.
Lighter
service
will
check
the
slo
file
and
also
check
whether
there
are
any
open
problems.
E
If
you're
using
the
dynamic
traces
slicers,
you
have
the
possibility
to
do
so
and
then,
when
the
evaluation
is
successful,
the
remediation
will
be
complete.
But
otherwise,
when
the
evaluation
was
not
successful,
so
the
evaluation
result
was
failed
and
that
sequence
will
be
triggered
again
and
then
that
case
the
remediation
service
will
return.
The
next
action
that
should
be
executed
and
the
whole
iteration
starts
again
so
executing
the
action
waiting
evaluating
and
checking
whether
this
has
been
successful.
E
So,
let's
have
a
quick
look
at
my
bridge
to
see
to
see
how
that
looks
like
in
practice.
So
we
do
have
a
remediation
sequence
open
here
in
our
production
stage,
and
if
we
expand
this,
so
we
have
two
iterations
of
the
remediation
sequence
here,
the
first
one
and
second
one
so
in
the
first
one
the
get
actual
triggered
event
was
sent
to
the
remediation
service.
E
Then
that
executed
with
the
first
action
to
be
executed
for
that
problem.
In
that
case,
it
was
the
toggle
feature,
action
where
we
set
the
enable
promotion
to
off
and
that
was
executed
and
then
afterwards,
after
10
minutes,
the
evaluation
was
performed,
and
in
that
case
it
failed
that
case
it
failed
because
we
didn't
have
a
time
frame
specified
for
the
lighthouse
service.
So
I
will
come
back
to
that
specific
problem
in
my
next
request.
E
I
want
to
discuss,
but
anyway,
for
now,
let's
just
focus
on
the
fact
that
the
evaluation
failed
and
if
you
recall
the
shipyard
I
showed
earlier,
we
would
like
to
trigger
the
remediation
again
if
the
evaluation
result
was
in
fact
failed
and
that's
exactly
what
happened
here
so
then
the
next
action
was
fetched.
In
that
case,
I
just
specified
the
same
action
twice
in
the
shipyard.
So
that's
why
the
toggle
feature
enabled
promotion
was
set
to
off
again
and
then.
E
In
the
meantime,
I've
deployed
the
correct
version
of
the
lightsaber
service,
so
it
could
actually
handle
the
incoming
evaluation.triggered
event,
and
in
that
case
the
evaluation
was
successful.
So
we
can
also
check
here.
E
So
let's
go
to
the
issue
so
basically
what
the
lighthouse
servers
did
before
this
pull
request
was
to
check
if
the
evaluation
triggered
event
contained
the
start
and
demand
property,
and
if
those
were
available,
it
performed
an
evaluation
for
exactly
that
time
range,
but
for
the
remediation
use
case.
If
you
recall
the
example
I
showed
earlier
in
the
bridge,
we
would
also
like
to
to
just.
G
E
A
couple
of
minutes
until
we
trigger
the
evaluation
and
in
the
shipyard
file
in
the
evaluation
task,
we
wanted
to
be
able
to
specify
just
the
time
frame
that
we
want
to
have
evaluated.
So
in
that
case,
we
always
want
to
look
at
the
last
10
minutes,
so
that's
also
what's
specified
in
the
as
a
property
in
the
shipyard
file
and
in
the
shipyard
file.
Of
course,
we
don't
always
want
to
update
the
exact
start
and
end
times.
E
Then
too,
there
are
actually
actual
values,
so
we
want
to
only
provide
the
time
frame
of
10
minutes
and
that's
what
has
been
added
in
the
to
the
lighthouse
service
in
that
case
and
also
to
the
corresponding
evaluation.triggered
event.
So,
actually,
here
we
see
how
that
change
affected
the
behavior
of
the
lighter
service.
E
So
in
the
first
iteration
I
had
the
old
version
of
the
lighthouse
service
deployed
where
it
couldn't
handle
this
time
frame,
property
that
was
set
to
10
minutes,
but
afterwards,
after
implementing
and
deploying
this
pull
request,
the
lighthouse
service
was
now
able
to
handle
that.
So
again.
Here
we
also
passed
the
time
frame
of
ten
minutes
and
in
that
case
the
lighthouse
service
correctly
interpret
interpreted
this
value
of
10
minutes
and
sent
out
the
correct,
get
sli
event
with
the
correct
time
frame.
E
So
in
that
case
we
were
interested
in
the
time
frame
from
1349
to
1359
and
dinotris
sli
service,
retrieved,
those
values
and
the
lighthouse
service
was
able
to
evaluate
those
sli
all
right.
Are
there
any
questions
about
that?
E
E
So,
in
the
last
version
of
captain
we
already
had
the
possibility
to
do
the
deployment
test
using
the
user
managed
deployment
strategy.
E
Add
resource
command
to
deploy
a
so-called
endpoints.yaml
file
that
should
be
located
in
the
helm,
slash
under
helm,
slash
endpoints
in
your
service
directory
in
your
github
server
and
afterwards,
if
you
trigger
a
deployment
using
the
user,
manage
deployment
strategy,
the
home
service
will
look
for
that
file
and
then
include
the
values
that
are
specified
here
in
the
correlating
deployment
finished
events.
So
I
think
I
do
have
an
example
here.
C
C
E
Where
we
triggered
the
delivery
sequence
so
yeah,
so
the
first
example
here
was,
I
think,
an
example
where
we
didn't
upload
the
the
endpoints.gmo
file
before
deploying.
So
in
that
case
the
deployment
will
still
work,
but
in
that
case
those
are
properties
will
be
missing
and
what
I
did
afterwards
before
triggering
the
next
delivery
sequence.
E
I
uploaded
this
file
and
then
the
home
service
did
its
thing
fetched
the
endpoints
that
the
ammo
file-
and
in
that
case
it
was
able
to
determine
their
uris
and
include
them
in
the
deployment
and
finished
event
and
those
deployment
uris
could
now
be
used
by
the
next
task
execution
service,
like
the
jmeter
service,
in
order
to
to
execute
the
tests
against
those
your
eyes
and
yeah,
maybe
really
quickly.
Let's
show
how
the
structure
of
this
endpoints
that
yama
file
looks.
E
Yeah-
it's
not
really
pretty
in
that
way,
but
here
in
the
integration
test
for
this
feature,
which
is
written
in,
go
that's
basically
the
structure
of
the
of
the
endpoints
that
the
armor
file,
so
it's
just
a
deployments,
uri's
local
property
and
then,
which
is
an
array
of
strings
and
the
same
is
for
the
holes
for
the
deployment.
Uri
is
public,
so
you
can
also
pass
an
array
of
urls.
Your
application
will
be
reachable
on
once
it
is
deployed.
G
I
have
a
question
flow.
Would
it
be
possible.
E
G
E
G
The
result
to
warning
yes
with
a
message:
oh
hey,
you
forgot,
probably
forgot
unintentionally,
to
to
to
upload
the
endpoint,
the
amplifier,
so
you
don't
have
those
uris.
E
F
I
clicked
on
the
button,
didn't
want
to
talk,
I
think
yeah
as
I've.
You
have
seen
in
the
notes
already.
I
have
just
a
smaller
quality
of
life
improvements.
F
This
I
will
just
just
read
quickly.
So,
first
of
all,
the
approval
process
is
visible
again,
so
if
there
is
an
open
approval,
it's
marked
with
the
question
mark.
I
think
this
already
worked,
but
now
it's
it's
visible
again.
I
think
this
is
very
nice
for
recognizing
it's
also.
The
approval
box
is
now
available
on
our
screens,
including
the
the
service
screen
as
well
as
here
so
yeah.
F
This,
I
think,
improves
to
the
user
experience.
What's
also
added
is
the
is
the
link
to
the
stage
execution,
so
you
can,
if
you
for
example,
see
that
there
is
a
plot,
a
problem
or
an
approval
open.
It
can
just
go
to
the
sequence
directly
from
the
environment
screen
here
and
also
the
second
link
that
was
added
was
here
in
the
service
screen.
There's
this
the
view
service
execution
button
now
this
is
actually
the
first
step
of
improving
the
empty
screen.
F
A
No
questions
here
just
one
question,
but
I
think
that
we
also
have
this
issue
in
the
backlog
that,
for
me,
it's
not
a
little
bit
difficult
to
see,
which
sequence
is
actually
is
actually
selected.
A
E
A
Currently
yeah
you're,
looking
at
currently
selected.
F
H
H
So,
for
me,
I
implemented
the
remediations
in
the
server
screen
so
that
the
seller
screen
also
shows
remediations.
As
you
can
see,
the
card
service
now
shows
an
and
running
icon.
If
there
is
a
running
remediation,
if
I
expand
it,
I
see
which
deployment
has
the
active
remuneration
running
and
in
the
timeline
I
see
the
the
running
icon
next
to
the
stage
when
I
click
the
remediation
under
error
action,
I
can
see
their
open
revelations
and,
as
you
can
see,
there's
a
running
remuneration
for
filler
rate
increase
and
yeah.
H
Also,
we
can
see
the
remediation
conflict
we
have
when
we
expanded.
We
see
the
remediation
point,
the
amplifier
and
yeah,
and
also
we
have
a
link
to
view
the
active
remediation.
H
So
this
redirects
here-
yes,
so
that's
basically
it
and
next
to
that.
Maybe
to
mention
there's
also
a
deep
link
for
that.
So
also
refreshing
and
refresh
the
page
now.
H
The
remediation
system
is
stereo
selected
yeah,
that's
basically
it
any
questions,
maybe
to
mention
this
thing:
yeah.
That
also
shows
the
evaluation
of
the
the
remediation.
If
there
was
any.
H
H
A
H
A
No,
then
I
think
we
can
move
on
to
the
next
one
on
the
list
it's
burned
when
I'm
not
mistaken
a
guest
and
someone
who's
new
to
the
community.
Now
let
me
just
change
the
permission
here
allowed
to
talk
hi.
C
Yeah
hi
everyone.
Thank
you
for
having
me
here.
Let
me
enjoy
this
meeting,
so
I
had
came
across
this
project
via
the
mentorship
program
and
and
I'm
going
to
discuss
the
issue
that
I've
linked
and
that
I
understood
the
addition
of
the
web
book.
Part
of
the
like
the
user
story
that
that's
being
written
here
has
been
written
here,
but
I
I
didn't
quite
understand
the
templating
part
of
this.
A
Let
me
just
explain
you
what
mr
temp,
what
is
me
meant
by
the
templating
well,
captain
will
always
send
out
so-called
cloud
events.
Captain
cloud
events,
these
one
follow
a
specific
specification
and
the
end
point
that
is
then
used
for
the
web
book
looks
different
or
may
takes
a
payload
that
that
has
another
structure
and
with
the
templating
mechanism
it
should
be
a
mechanism
that
takes
a
captain
cloud
event
translated
over
to
the
payload.
A
C
Yeah
so
by
templating,
I'm
trying
to
create
a
custom
cloud.
A
Event,
correct
yeah:
you
take
the
captain
cloud
event
and
translate
it
into
a
custom,
custom
event
or
custom
payload.
C
Right
right,
and
one
more
question
is
that
it
is
it
is
mentioned
here
like
the
the
feature
mentioned
here
can
be
like
can
be
used
by
the
generator
executor
service.
C
So
if
I
have
to
understand,
like
the
whole,
not
not
the
implementation,
but
the
use
of
this
feature
is
there
like
a
project
or
a
tutorial,
where
I
can
see
how
the
generated
executive
service
is
used
to
to
basically
emulate
this
feature
which
we,
which
we
have
to
implement
in
captain
itself.
A
The
generic
executor
service-
let
me
just
go
to
that
one
yeah,
that
one
is
it's
a
service
that
allows
you
to
execute
any
kind
of
job
yeah
based
on
a
captain
cloud
event,
and
this
one
would
also
then
be
kind
or
could
be
the
the
basis
for
implementing
than
the
web
hook
service.
A
A
Organization
there
is
the
let
me
just
search
it:
real
quick
template,
yeah
here's
here,
it's
pinned
the
captain
service
template,
which
is
also
written
in
go,
and
this
one
is
also
a
very
good
starting
point
for
writing
your
captain
service,
which
will
be
eventually
the
web
book
service,
and
because
this
template
already
provides
the
mechanism
for
the
event
handling
and
also
handler
functions
that
just
need
to
be
implemented.
Just
need
to
be
overwritten
for
for
your
code
or
for
your
purpose
that
you
want
to
implement.
A
A
C
B
Take
the
point
that
yeah,
let
me
just
make
sure
to
go.
B
A
All
right,
let
me
just
go
back.
Does
this
clarify
your
questions?
The
first
one
was,
but
the
templating
and
the
second
one
about
the
generic
executor.
C
Yeah
yeah
it
does
and
and
I'll
I'll
make
sure
to
go
through
what
you
shared
and
then
maybe
come
back
and
find
more
questions.
A
Okay
feel
free.
You
can
also
reach
out
to
jurgen
or
myself
on
biasleg
just.
A
You
to
get
your
clash,
questions
clarified.
Sure
sure.
A
A
If
not,
then,
let's
close
the
session
for
this
week,
thanks
for
joining
in
stay
tuned
for
the
captain
release
the
upcoming
one
tomorrow
and
yeah
have
a
nice
day
and
see
you
next
week,
then
bye.