►
From YouTube: Keptn Developer Meeting - Aug 11, 2022
Description
Meeting notes: https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit
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
Sign up to our newsletter: https://bit.ly/KeptnNews
A
Welcome
everyone
to
the
next
instance
of
the
developer
meeting
today
is
the
11th
of
august,
and
although
it's
vacation
time,
we
still
have
some
committee
members
here
in
the
meeting
I'd
like
to
kick
off
the
meeting
with
an
announcement,
because
we
discovered
recently
that,
with
the
latest
version
of
captain
one
of
the
latest
version
of
captain,
we
introduced
a
regression
or
a
behavior
change.
That
was
not
documented.
A
A
Hence
we
recommend
users
that
have
multiple
remote
execution
planes
to
have
for
each
integration
in
a
separate,
remote
plane
have
a
different
name
for
that,
and
if
you
want
to
change
the
name
of
your
integration,
you
can
do
that
via
the
case.
The
employment
name
and
parameter
variable
of
your
integration
or,
if
you're,
using
the
sap,
connector
library,
you
can
just
change
the
name
while
you're
calling
the
method
that
does
the
registration.
A
And
that's
the
announcement
of
today
sorry
for
this
breaking
change
that
we
forgot
to
highlight.
We
changed
the
release,
note
to
make
it
still
available,
however,
but
with
that
I
will
hand
over.
A
B
A
B
A
B
A
C
Yeah
good
okay,
some
couple
of
things
made
in
the
last
two
weeks
by
the
team.
The
first
one
is
adapting
the
pipelines
on
the
future
removal
of
jmeter
and
helm
services
from
the
captain
core
repository.
C
C
C
Yeah,
nothing
much
to
say
about
it.
Second
issue
was
migrating.
The
quality
gates,
integration
test
to
a
faster
component
test.
We
have
some
failure,
use
cases
in
the
integration
test
for
the
quality
gate
so
for
the
lighthouse
service
and
for
the
evaluation.
C
C
C
Most
cases
there
is
just
some
minor
refactorings
in
the
lighthouse
service
and
creating
a
new
main
test
go
where
the
tests
are
located.
C
Another
issue
was
a
small
one,
removing
the
configuration
service
kubernetes
service,
as
we
recently
moved
for
the
resource
service.
We
still
had
a
kubernetes
service
named
as
a
configuration
service,
so
we
just
remove
it
together
with
airbags.
C
Yeah
and
last
thing
was
a
bug
fix.
We
had
recently
a
problem
when
updating
an
integration
in
the
shipyard
controller,
for
example
webhook
that
does
not
have
subscriptions
or
has
a
nil
subscriptions.
C
It
was
basically
not
able
to
update
a
nil
subscription
field
in
the
whole
integration,
so
we
are
now
testing
if
the
integration
has
subscriptions
equal
to
nil
and
if,
yes,
we
do
not
update
only
the
subscriptions
field,
but
also
the
whole
integration
with
the
appropriate
subscriptions.
So
from
now
on,
this
bug
is
not
an
issue
basically
without
this
fix,
when
this
problem
occurs
due
to
some
reason.
C
D
Okay,
let's
go
to
the
bridgepot,
so
first
we
fixed
the
bug
regarding
the
web
hook
and
creation
and
updating.
There
was
a
bug
that
values
that
are
used
for
the
headers:
they
are
sent
with
name
value
properties
instead
of
key
value.
D
This
was
then
a
problem
in
the
webhook
service,
because
yeah
are
there
unknown
properties
because,
instead
of
key
name
was
sent
by
yeah,
better
client
and
yeah.
This
is
fixed
now.
So,
if
you
create
now,
for
example,
custom
web
hook.
D
You
can
now
see
if
you
create
a
subscription,
it
is
correct,
fully
sent
with
key
value
instead
of
a
name
menu
yeah,
and
this
is
fixed.
Now,
yes,
was
previously
present,
not
found
not
visible,
because
we
use
the
same
interface,
client
and
server
set,
but
there
are
some
form
controls
with
type
any
and
that's
why
this
bug
didn't
came
up
come
up
earlier
yeah,
so
this
payload
is
fixed
now
and
the
web
book
is
correctly
created.
D
Then
the
next
thing
we
now
use
the
new
line
chart
component
types
hence
implemented.
So
now,
if
d3
is
enabled
with
the
d3
enabled
flag,
you
can
now
also
switch
to
chart
and
have
the
new
blind
shot
here.
Yeah.
I
don't
have
nice
evaluations
here,
but
now
this
one
is
also
our
own
component
with
d3
instead
of
high
charts
yeah.
That's
to
that
so
we're
now
using
both
charts
for
instead
of
headshots,
then
the
next
thing
yeah
we
improved
some
visualization
for
the
result
for
the
slide
breakdown.
D
Previously,
we
just
showed
a
message
that
the
score
represents
a
portion
of
the
total
score
for
an
indicator
result,
and
now
we
also
explain
the
fail
and
the
warning
message.
So
if,
for
example,
the
score
is
now,
then
we
also
have
the
error
here
or
the
red
the
message
that
there's
quite
a
set
knife,
because
it
is
because
it
failed
and
also
for
warning.
If
it
is
warning,
then
the
result
is
the
score
is
half.
D
We
also
documented
this
now
in
the
document
page
under
concept,
concepts
and
quarter
gates,
and
then
we
also
state
how
this
score
is
calculated
and
how
warning
and
failed
affects
the
score
yeah.
So
this
is
now
also
adjusted
yeah
and
better
visualized,
with
an
underline
that
is
overlay
available
yeah,
then
the
next
thing
was
part
of
a
refactoring
task,
a
bit
of
performance
task.
D
Previously
the
evaluation
was
yeah.
The
evaluation
details
you
see
here
also
showed
the
also
has
that
heat
map
inside
and
previously
for
this
overlay.
We
fetched
50
evaluations
which
were
not
necessary
because
we
don't
show
the
heat
map
here
and
only
the
if
we
show
the
heat
map
there.
All
the
data
should
be
aggregated
and
fetched,
and
now,
as
you
can
see,
there
is
no
additional
check.
If
you
hover
over
it.
There
is
no
loading,
that's
just
showing
this
evaluation
and
don't
fetch
50
other
ones
yeah.
D
A
A
So
the
integration
tests
do
not
reference
any
more
help.
Multimeter
then
we
also
prepare
a
bit
of
refactoring
for
the
shipping
controller,
where
the
package
structure
has
been
changed,
so
it's
easier
to
add
new
files
to
extend
functionality,
because
everything
is
now
into
his
own
proper
package
instead
of
having
one
big
folder
full
of
files,
and
then
he
also
started
to
work
on
this
inbound,
inventive
validation.
A
So
you
might
know
that
captain
provides
this
post,
slash
event,
endpoint,
where
anyone
can
send
events
into
captain
from
a
remote
execution
plane,
but
we
don't
take
any
assumption
whole
or
we
don't
try
to
validate
this
event
and
what
bern
tries
to
do
is
for
each
event,
type
that
is
well
known
in
captain.
So,
based
on
our
specification,
we
can
assume
some
sort
of
structure
on
these
events.
A
So
if
you're
using
event
not
according
to
our
specification
or
100
to
our
specifications,
your
integration
might
fail.
So
we
want
to
enable
this
by
default.
But
if
it
crashes
any
problems
to
your
installation,
you
can
disable
the
event,
validation,
dot
enabled
and
they
can
set
it
to
false.
B
Come
on
there
we
go
and
we
can
share
my
screen.
He
has
filed
three
tickets
and
there
are
tickets
for
discussion.
So
maybe
we
should
just
point
out
if
anybody's
not
aware,
we
have
a
new
get
started
with
kept
in
tutorial,
it's
under
explore
captain,
because
we,
because
quickstart,
is
taken
by
something
else.
I
think
it's
vastly
superior.
You
use
this
killer
coda,
so
they
don't
have
to
you
open
it
up
and
it
just
starts
installing.
B
Oh,
we
have
to
sign
into
it.
Okay,
so
you
won't
get
to
see
it
in
any
event,
once
you're
signed
in
it
just
starts
it
does
an
installation
there's
nice
text
for
people
to
read.
It
takes
about
three
minutes
to
get
everything
installed
and
it
goes
into
a
lot
more
about
kept
and
it's
re.
I
think
it's
a
good
and
and
when
you're
done
you
actually
know
a
little
something
about
it.
We
are
left
with
these
old
tutorials,
which
I
believe
were
last
updated
for
captain
11.
B
there's.
I
guess
the
two
main
ones
are
the
full
tour
on
prometheus
and
the
full
tour
on
dinotrace
the
the
new
one
really
does
it.
It
does.
Just
prometheus,
I
talked
to
the
dynatrace
people
and
they're,
going
to
go
off
they're,
going
to
use
killer
captain
and
do
a
real
dynatrace
one
that
will
have
some
dynatrace
features
in
it
too,
so
they're
off,
because
our
our
feel
was
that
for
the
principles
of
captain
it
doesn't
matter
what
your
I
mean
for
this
quickie.
It
doesn't
matter
what
your
data
source
is.
B
You
get
the
principles
of
how
you
do
it
so
so
we
have
that
we
have
a
second
one
filed
for
the
resources
section
of
of
some
things.
It's
sort
of
just
old
stuff,
it's
time
to
clean
up,
and
we
have
one
more
is
what
to
do
with
the
quick
start,
which
again
I
mean
it's
using
socks
shop.
It's
I
don't
know
that
anybody's
getting
it
to
re
to
work.
People
are
coming
in
and
they're
showing
up
on
the
help
station.
B
The
other
thing
we're
doing
in
the
background.
What
we
realized
is
that
a
lot
of
people
are
using
these
tutorials,
not
as
tutorials
but
because
they're
the
only
place
that
we
give
a
sequential
list
of
steps
that
one
can
run
to
to
install
or
to
create
a
project.
B
So
so
that's
being
done
also
that
will
be
available.
So
I
don't
know
we
could
discuss
here
or
we
could
just
make
that
available
to
everybody
and
we
can
discuss
asynchronously
in
the
jira
ticket.
Does
anybody
have
words
of
wisdom.
B
B
Sorry
about
that,
and
that
is
not
working
well,
the
the
three
the
links
for
the
three.
B
Issues
are
in
the
in
the
agenda,
so
you
can
look
at.
I
think
we
all
the.
I
guess
the
question
is
I
we
don't.
I
don't
know
who
all
might
care
about
those
I
mean
they
don't
work,
it's
hard
for
me
to
see
a
justification
for
keeping
them.
We
have
something
else
new
and
better
that
works,
but
there's
people
all
over
who
love
the
my
impression.
Is
they
love
having
the
title
and
they
haven't
looked
at
them
lately
to
see
what
the
contents
are,
but
I'm
being
cynical
so.
E
I
think,
having
a
banner
there
that
states
that
those
are
outdated
and
the
new
tutorials
will
be
provided
using
a
new
framework
is
definitely
already
a
good
idea
to
help
the
users
and
to
not
let
them
play
around
with
with
outdated
or
old
tutorials,
with
captain
auto
11.
B
E
The
question
is
a
little
bit
whether
there
are
still
references
towards
the
tutorials
and
if
we
break
them
when
we
are
going
to
to
really
delete
them,
I
mean
quite
of
them,
are
old
and
then
not
relevant
anymore,
when
I
think
about
captain
auto
date
or
0.7
they
are
from
from
yesterday,
but
those
that
are
about
a
half
a
year
old.
Here
we
might
have
some
some
real
active.
A
And
maybe
we
could
change
the
layout
to
say
this
website
is
being
deprecated.
Please
go
over
killer
coda,
so
we
keep
up
the
website
still
alive
for
a
while,
but
we
notified
the
user
that
should
move
towards
the
new
platform.
B
That's
a
good
idea
and
the
quick
start
is
a
link
in
the
documentation.
So
if
we
just
renamed
that
section
there,
they
would
get
there
the
one
that
we've
got
we'll
have
more
coming,
but
yeah
yeah.
That
would
work
if
so,
if
we
preserve
so
their
links
would
work
if
they're,
if
they
get
there,
they'll
just
find
that
and
they'll
get
redirected.
B
And
is
it
okay?
Can
we
just
go
ahead
and
do
that
or
does
it
need
to
be
run
by
more
people?
I
don't
I
don't
know
who
all
might
have
an
interest
in
it.
E
I
mean
I
don't
see
any
any
investments
that
are
currently
ongoing
in
the
old
tutorials
and
instead
of
of
leaving
a
community
member
on
an
old
tutorial.
I
think
it's
better
to
guide
them
directly
to
the
new
ones
and
in
other
words,
let's
do
it
as
soon
as
possible,
so
that
we
don't
have
a
frustrated
community.
B
Yeah,
that's
that's
wonderful!
Okay!
We
will
get
to
that
quickly.
Can
somebody
else
since
item?
I
don't
know
why
it
lets
me.
It
won't
says
we
can't
share
your
screen
after
I
do
it
for
just
mine.
I
want
to
take
a
quick
look
at
two
reference
pages
that
I'm
working
at
working
on.
A
A
B
That
would
be
wonderful
and
then
oopsie
and
your
explorer
captain
back
to
the
agenda
and
there's
a
link
to
the
pull
requests.
B
There
we
go,
we
have
two
we're
still
working
on
these
reference
pages
and
we're
we're
waiting
to
know
exactly
what
the
capabilities
will
be
of
the
new
dock
engine.
B
I
think
everybody's
senses
for
for
in
cloud
events
and
values.yaml,
and
maybe
most
of
them
it's
in
the
software,
and
I
mean
I
can
copy
from
the
software
and
put
them
in
the
documentation,
and
I
can
do
that
repeatedly
and
try
to
keep
them
in
sync,
and
we
all
know
how
well
that's
going
to
work
so
what
I've
got
right
now
for
these
two
for
cloud
events
is
in
place
of
synopsis,
I've
got
spec,
and
that
is
a
link
that
takes
them
into
the
the
real
one
in
the
software.
B
I
am
hoping
with
the
new
tools
that
we
will
be
able
to
just
pull
something
in.
If
not,
we
may
want
to
do
like
we
do
with
cli
and
author
the
reference
page
in
the
software
repository.
B
So
there
you
see,
you
get
the
specification
and
then
I
added
some
usage
notes
and
we
have
the
differences
between
versions
and
we
have
the
c
also,
which
I
think
I
mean
at
least
for
for
those
people
who
don't
live
in
the
code
all
the
time.
At
least
they
don't
have
to
go
sleeping
through
the
code,
trying
to
find
what
that
spec
is.
B
B
I
actually
did
copy
the
whole
spec
into
the
synopsis,
and
then
I
decided
no,
we
won't
do
this,
but
what
I
had
also
done
was
started
a
list
because,
as
I
look
at
the
spec
a
lot
of
those
fields,
I
don't
instantly
know
what
they
are
or
I
want
to
know
what
the
range
of
file
values
is,
and
I
don't
know
if
we
need
to
document
every
single
one
of
them.
B
I
started
out
it's
like
okay,
we
can
give
them
a
sentence
about
what
each
section
is
about,
which
will
have
a
link
to
the
docs
that
talk
about
that
feature.
So,
and
I
don't
I
don't
know
I'll-
probably
have
to
work
with
mo
to
figure
out.
It
may
be
that
there's
only
a
few
of
these
that
users
regularly
interact
with,
and
that's
all
we
want
to
describe
because
actually
having
this
whole
list,
we're
in
almost
as
much
trouble
for
maintenance.
A
A
We
were
investigating
some
tools
that
can
just
read
this
yaml
file
and
automatically
generate
a
table
for
documentation
purposes.
Maybe
when
we
get
to
the
ticket
we
can
reach
out
to
you
mike
to
maybe
improve
this.
B
Good
yeah
and
then
and
see
what
the
new
doc
engine
is
going
to
do,
so
I
it
would
be
nice
to
get
something
up
there
for
now.
If
the
one
thing
I
really
want
to
do
squirrel
down
this
one,
the
important
thing
on
this
one
is
all
that
marvelous
writing.
That
mo
did
for
all
the
changes
in
0.17
are
in
the
upgrade
guide
to
update
to
17,
and
I
just
copied
those
over
lock,
stock
and
barrel
at
the
end.
B
But
so
we
will
have
a
record
of
exactly
what
those
changes
were
because
as
soon
as
somebody
goes
to
18
they're
not
going
to
see
the
17
upgrade
instructions
but-
and
that
was
pretty
major,
so
I
think
which
so
for
now
I
should
just
delete
out
all
those
descriptions,
all
the
individual
descriptions
and
we'll
just
have
a
very
bare
bones,
one
that
will
link
to
the
spec
we'll
give
them
a
couple
of
usage
notes
and
we'll
have
the
differences
between
versions,
and
we
put
does
that.
Does
that
work?
B
B
I
will
go
ahead
and
change
the
pr
and
then
somebody
can
look
at
it
in
more
detail
to
see.
If-
and
maybe
somebody
may
have,
suggestions
for
additional
usage
note,
you
know
trying
to
the
my
definition
of
these
reference
pages
is
I
read
the
guide
when
I'm
new
to
this,
and
I
learn
how
to
do
this
learning?
How
to
do
things
then,
once
I
know
what
I'm
doing
these
are.
B
This
is
a
place
where
I
can
look
something
up
quickly,
the
stuff
that
I
need
to
look
up
quickly
so
but
of
course
people
look
at
it,
maybe
when
they
don't
have
enough
background
so,
but
I've
had
since
I've
had
this
shipyard
file,
there
have
been
several
questions
that
have
come
up
that
I've
get.
We
add
that
to
the
shipyard
file,
so,
okay,
thank
you
very
much.
Those
are
my
issues.