►
From YouTube: CDF SIG Events - Dec 19, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
C
A
A
B
A
Let's
go
with
five
minutes,
personal
I
think
we
should
get
going
away.
Let's
see
this
might
be
a
quick
meeting
done,
since
we
have
quite
a
few
participants.
Sorry,
not
that
many
participants
today,
let's
see
but
anyway,
for
the
record
I-
think
it's
valuable
to
just
bring
this
subject
points
out
that
they
are
ready
to
catch
under
there.
A
As
you
can
see,
people
might
consume
this
meeting
afterwards
as
a
recording.
So
then
it's
it's
anyway
worthwhile
to
have
it
there.
So
I
believe
I'm
sharing
the
agenda
there
and
just
for
information.
Unless
you're
aware
you
might
have
seen
you
can
select
that
there
is
now
a
new
time
slot
for
the
Asia
Pacific
run
date
time
for
the
City
events
working
group
meeting,
which
normally
occurs
on
Wednesdays.
A
So
the
meeting
that
was
supposed
to
be
held,
this
Wednesday
is
moved
to
this
Monday
and
it
has
already
passed
a
few
hours
ago,
the
information
there
and
that's
how
it
will
continue.
So
it
will
be
on
the
same
day,
then,
actually
as
the
zig
events
meeting,
which
we
also
discussed
them
under
this
meeting
today,
and
this
is
the
events
work
group
meeting
today,
where
we
discussed
briefly
on
the
the
scope
of
these
two
different
meetings.
A
So
they,
the
Sig
events
meeting
which
we
are
on
right
now,
will
mostly
focus
on
on
presentations
from
different
contributors
to
the
to
the
sake
and
people
that
are
interested
to
share
their
event.
Driven
experience
and
we'll
also
talk
about
interactions
with
other
six.
If
there
is
anything
to
to
bring
up
there
and
any
non-state
event
specific
event,
discussions
I'd
say
which
is
not
specific
to
the
syrians.
A
Protocol
itself
could
also
be
interested
to
bring
up
here,
and
we
have
this
sequence
meeting
on
demand
when
there
is
an
agenda
for
it
and
also
then,
for
the
record,
the
upcoming
meetings
during
the
coming
holidays,
the
coming
two
weeks,
there
will
be
no
meetings.
So
the
next
week's
City
events
work
group
meeting
is
canceled
and
also
the
week
after
that.
A
So
that
is
said,
upgrades
from
the
TOC
and
other
special
interest
groups
in
City,
Foundation
I,
don't
have
anything
noted
there
and
I
doubt
that
any
one
of
you
have
been
to
any
of
those
working
groups
to
bring
some
information
back.
A
C
A
A
Mention
it
before
we
go
there
that
I
also
intended
to
look
into
the
the
refresh
of
the
website.
We
have
to
see
that's
not
the
website,
but
I
would
need
Terry
on
the
call
for
that.
The
account
doesn't
seem
to
be
here
now
and
I
could
mention
something
about
the
CO2
version
of
CD
events
in
the
end,
but
yeah
we'll
see.
C
It's
actually
in
the
starting
phase.
Let's
say
like
this
is
not
a
PR
for
the
changes
right
now,
I
mean
like
not
for
the
code
changes
or
nothing,
but
it's
a
design
discussion
in
this
Pinnacle
governance,
repo
that
we
have
raised
and
the
proposal
we
are
keeping
on
the
Spinnaker
Community
to
discuss
further
like
to
integrate
CD
events
into
Spinnaker.
So
we
have
like,
based
on
the
the
POC
outcome,
so
we
have
like
some
analyzes
and
the
design
proposals
have
been
updated
here
and
there
is.
C
Some
discussion
is
going
on
with
the
Spinnaker
community
members
and
within
our
team
to
have
this
Spinnaker
integrated
using
CD
events
so
yeah.
There
are
some
couple
of
questions
that
I
need
to
answer
there
and
and
like
I'm,
updating
the
design
to
different
goals
and
design
proposals
that
we
have
discussed
internally
within
our
team.
So
I
think
once
that
is
finalized
and
approved
by
his
clinical
community.
C
So
we
can
go
ahead
and
further
say
that
like
Spinnaker
can
support
CD
events
and
we
can
like
show
one
demo
to
the
Spinnaker
Community,
wherein
the
CD
integration
works
with
other
cacd
tools
with
Spinnaker.
C
So
that's
that's
more
on
it
on
the
design
proposal,
so
we
have
discussed
several
design
proposals,
so
this
is
Handy
like
we
can
have.
The
this
PR
is
updated
with
the
latest
design
proposals
that
have
been
discussed
so
far,
so
I'm
still
waiting
for
the
comments
from
Spinnaker
Community
to
someone
review
and
put
some
comments
even
to
ask
and
and
like
once
they
are
finalized
and
reviewed
and
approved.
So
we
can
go
ahead
and
see
the
things
how
it
works
yeah.
So
these
are
some
things.
C
I
have
added
on
the
design
like
how
the
configuration
will
be,
and
what's
the
new
things
that
we
need
to
add
and
what's
the
existing
things
are
there.
So
there
are
a
couple
of
things
that
existing
WebEx
configurations
that
we
can
use
right
now
to
send
and
receive
CD
events,
and
so
there
are
like
more
capabilities
that
we
can
bring
into
the
Spinnaker
site
by
implementing
some
notifications
and
Pub
sub
system
types,
so
that
I
have
explained
here
everything.
C
So
we
can
go
through
I
think
when
the
Spinnaker
communities
is
approved
and
I
can
go
over
more
into
how
this
design
goes
and
and
how
this
will
integrate
this
vinegar
using
CD
events.
D
A
Will
it's
just
something
you'd
like
to
elaborate
on
or
something
you
would
like
feedback
from
the
series
Community
about
or
I
mean
what
would
be.
The
difference
is
when,
when
connecting
this
into
the
the
book
itself,
compared
to
how
it
was
done
earlier,
and
maybe
compared
to
other
tools
that
also
connect
to
each
other
to
in
the
book.
C
And
the
park
is
like
implemented
survey
that
it
has
a
separate
CD
events
controller
so
that
we
have
created
to
produce
and
consume
CD
events
all
together
separately,
but
there
are
some
existing
mechanisms
that
we
can
reuse
from
Spinnaker
side
instead
of
like
implementing
new
things
inside
Spinnaker,
and
even
that
has
been
discussed
with
the
Spinnaker
community
members
and
internally
Ericsson
teams,
and
that
that's
why
we
have
come
up
with
the
something
that
is
already
existing.
C
So
we
can
reuse
some
of
the
functionalities
of
Spinnaker
and
and
make
use
of
like
to
use
the
City
events
produce
and
consume
yeah.
So
this
is
how
we
like
you,
can
see
the
CD
events.
Controller
is
a
part.
That's
the
park
using
it,
but
right
now,
so
this
will
be
replaced
by
the
existing
functionalities.
That
Spinnaker
is
already
having
it.
So
let's
say
the
notifications
are
Pub
sub
system
types
or
we
have
some
web
hooks
functionalities
that
already
existing
in
this
Pinnacle.
A
A
C
Right
it'll
be
something
similar
right
exactly
so
even
the
POC
that
we
had
also
in
the
similar
context,
but
only
thing
is
like
in
the
CD
events
controller
when
you
have
done
so
new
endpoints
that
I've
created.
But
now
so
we
have
like
something
web
books,
so
we
can
create
a
dynamic
web
hooks
and
and
using
that,
so
we
can
even
Spinnaker
can
able
to
consume
any
CD
event
that
comes
from
K
native.
So
we
can
configure
in
that
way.
So
right
now
it
is
achievable.
C
Using
CD
I
mean
the
webhooks
functionality
which
exists
in
Spanish
that
that
works
the
same
way
how
it
work,
how
it
is
working
with
Captain,
intact
and
right
now,
right.
That's
true
yeah,
but
there
are
some
things
like
we
need
to
mention
like
I,
have
even
added
in
the
design
proposalizable.
So
there
is
no
attribute
constraints,
specifications
that
we
can
go
with
because
web
hooks
right
now
it
only
accepts
the
payload
constraints,
not
the
yeah,
not
the
attribute
attribute
constraints
yeah.
C
This
is
the
one,
so
it
has
only
the
payload
constraints,
but
we
need
like
when
CD
event
is
consumed.
So
we
should
have
something
like
an
attribute
constraint,
so
that
will
decide
which
event
type
that
we
are
consuming
and
based
on
that
we
need
to
run
some
pipeline,
so
that
will
be
the
new
portion
of
validation
that
we
can
add
it
in
the
this
automated
trigger
web
configuration
here,
yeah.
D
A
C
It
will
be,
it
will
be
free
text,
because
if
you
see
the
above
screenshot
there,
we
have
like
attribute
constraints
when
it
comes
to
the
pub
sub
model
in
the
above
yeah.
So
we.
B
C
Here,
payload
constraints,
attribute
constraint
and
autovet
constraints,
but
attribute
constraint
is
something
is
missing
in
the
webhook
configurations.
Web
hook
type,
but
that
is
exist
for
the
pub
subsystem
type.
So
this
is
attribute
constraint
is
something
we
can
use
like.
Cetca
type
is
like
what
type
of
event
I
am
interested
on
to
run
this
particular
pipeline.
When
this
is
configured
so
we
can
configure.
This
is
the
way,
but
this
is
this.
Functionality
is
not
exist
for
the
a
vapor
configure
configuration
the
below
screenshot
rules.
C
So
that's
something
we
need
to
add
on
an
extra
validation
to
receive
a
specific
event
type
for
for
CD
event.
A
C
Yeah,
so
if
a
theme
yeah,
if
you
have
something
incorrect,
so
definitely
so
that
will
not
be
triggered.
I
think
this
is
something
it's
a
free
text
that
is
like
configurable
in
all
the
way
for
different
types
in
Spinnaker.
C
If
you
see
if
there
is
no
particular
implementation
for
specific
things,
but
yeah,
it's
all
like
kind
of
templates
that
we
can
add
anything
I,
think
that
needs
to
be
well
documented
instead
of
having
it
here,
because
that's
the
way
they
are
following
it
all
the
way,
even
for
Pub
sub
system
types
and
Google
and
Amazon.
So
even
they
have
the
documentation
for
different
types
and
things
like
that.
What
needs
to
be
accepted
here.
A
A
A
A
When
the
City
events
protocol
becomes
stable
enough,
it
could
make
sense
to
to
do
specific.
Let
me
drop
down
lists
of
event
types
or
something
like
that,
but
we
are
far
from
having
a
stable
citizens
protocol
at
the
moment.
So
I
think
this
is
this:
okay,
really
a
good
way
forward.
Now,
at
this
point,.
D
C
D
C
Right
now
like
for
sending
a
CD
event
also,
we
have
something
like
a
Web
book
configuration
so
like
right
now.
What
you
see
on
the
screen
is
like
this
is
how
we
can
even
send
an
event
with
this
type
of
event,
but
this
does
not
accept
any
extensions
that
is
cacd
specific
extension.
So
this
is
a
straightforward,
a
cloud
event
so
without
having
any
additional
CD
event.
C
Specifications
like
you
see
here
so
this
is
all
the
web
hook
configuration
to
send
a
particular
event
to
the
events
broker,
so
the
web
hook.
Url
is
the
event
broker
that
I'm
using
it's
okay
native
Eventing,
Canada
events
broker
and
I
can
send
this
like
it.
C
It
is
like
a
cloud
event
that
I
can
send,
but
not
an
additional
extensions
like
what's
the
artifact
like
if
I'm
sending
this
is
as
a
service
deployed,
so
I
should
have
like
service
deployed
extensions
to
be
added,
so
that
is
not
as
possible
right
now
from
this
web
of
configuration
so
like
to
achieve
this.
Maybe
we
can
have
something
like
a
notification
so
wherein,
like
Spinnaker,
has
a
type
of
notification
at
each
pipeline
stage
is
completed.
C
So
we
can,
we
can
decide
like
when
to
send
certain
notifications,
and
in
that
notifications
we
can
have
a
new
CD
event.
Type
notification
is
added,
so
in
that
probably
we
can
list
out
all
the
different
type
of
CD
events
supported
and
user
can
select,
which
type
of
CD
event
that
I
need
to
send
and
to
which
event
broker.
So
this
is
the
two
selected
fields
that
we
can
introduce.
C
I
think
I
don't
have
that
screenshot,
but
that
is
the
new
thing
that
we
need
to
implement
when
it
comes
to
the
sending
a
notification,
so
that
will
work
as
like
producing
some
CD
even
to
external
words,.
A
C
D
A
D
D
C
C
So
that
is
something
missing,
so
we
can
we
can
achieve
like
using.
We
have
a
Java
SDK
right,
so
we
can
send
a
specific
event,
let's
say
like
if
I
want
to
send
a
CD
or
like
service
deployed
event.
So
this
is
the
oldest
old
format
of
event
that
I
mentioned,
but
yeah.
C
So
when
I
want
to
send
service
deployed
event,
so
I
can
select,
which
event
type
I
need
to
send
and
what
is
the
broker
from
the
notification
point
of
view
so
and
and
we
can
use
underneath
the
Java
SDK
so
and
that
will
construct
a
CD
service
deployed
event
and
send
to
the
specific
broker
URL
that
is
selected
here
when
it.
When
it
comes
to
notification,
okay,
so
yeah
we
can
use
the
Java
SDK
to
construct
the
actual
CD
event.
What
we
need
and
and
send
to
the.
B
C
C
Yeah
exactly
you
so
that
that's
what
will
be
pending
so
I'll
show
you
someone
from
Spinnaker
community
so
to
have
this
reviewed.
A
C
Yeah
yeah
some
may
have
answered
so
some
will
be
invalid,
based
on
the
new
design
discussions.
A
D
A
D
A
Yeah
yeah
I
think
this
looks
like
a
going
in
the
right
direction.
Making
this
I
mean
quite
a
small
footprint.
Upstream
pull
request
done
to
what's
been
occurred
to
just
support
this.
This
basic
City
events
where
you're
working
for
the
ram
types
and
then
it
can,
of
course,
the
elaborated
later
on
at
least
yeah.
This
would
make
it
make
spinner
support,
City
events
both
for
sending
and
receiving,
which
is
great
yep.
A
A
So
there
is
a
a
narrative
here
that
you
can
follow
more
naturally,
hopefully
on
so
you
can
understand
what
City
events
is
and
also
the
documentation
part
is
improved
here.
The
white
paper
and
the
primary
is
linked
from
this
menu,
and
then
we
have
the
different
buckets
of
events
also
from
within
this.
D
A
C
That
I
have
one
question
on
the
latest
the
documentation,
so
we
see
so
there
are
like
specifications.
We
have
right
for
different
buckets,
that
we
have
like
core
and
source
code,
Version
Control
and
integration
and
deployment,
and
there
are
like
different
event
types.
C
Are
there
I
think
so
for
some
I
see
still
at
0.1.1,
but
there
are
like
some
still
0.1
dot,
iPhone
draft,
so
the
event
types
and
there
are
also
I-
think
the
fields
are
also
got
updated
to
some
things
like
an
object
like
if
you
see
the
environment
is
changed
like
something
is
updated
to
environment
as
an
object
and
and
little
bit
changes.
I
see
like
from
last
time
to
this
time
and
when
we
actually
started
the
Java
SDK,
so
some
things
are
different.
A
Yeah
yeah,
you
should
yeah
and
there
is
a
yeah.
This
is
the
latest
zeroth
one,
one
version:
that's
the
tag
there.
There
there's
actually
a
0.12
version
now
with
very
small
updates
in
the
last
one
and
when
doing
the
job
SDK
now
I
think
it's
you
Adam,
who
is
working
on
the
osdk
and
updates
there,
and
then
you
should
look
into
this
012
version
of
the
spec
yeah
to
get
the
cards
stated.
A
Yes,
yes,
and-
and
the
releases
should
be-
should
be
declared
here,
what's
changed,
so
you
can
see
what
the
changes
are
between
different
releases
as
well,
so
I
guess
there
is
no
depth
towards
the
version
in
the
book.
Unfortunately,
so
it's
not
that
easy,
maybe
to
see
what
has
changed
since
the
book
implementation,
but
at
least
from
from
one
zero
one
zero
on
it
should
be
possible
to
see
the
the
disks
did.
A
These
change
logs
here
is
that
and
of
course,
you
can
even
specify
directly
from
zero
one
zero
to
zero
one
two
here,
so
you
get
both
those
changes
looks
are
in
the
same.
We
can
see
all
the
changes
there,
okay,
so
that
should
probably
help
you
when
updating
the
the
SDK,
at
least
from
this
version
on.
A
C
It's
more
in
line
I
see
like
it's.
It's
it's
getting
better
like
for
the
changes
yeah.
So
we
have
more
information
added
yeah,
that's
good.
D
A
So
that's
that
done
and
it
when
it
comes
to
the
next
minor
list
of
City
events
0.2,
we
intend
to
release
that
somewhere
in
late,
February,
I
believe
I
think
we
set
the
let's
see
where
we
can
find
the
Milestone
definition
there.
A
A
So
there
are
some
issues
in
the
course
deck
and
then
on
the
group
of
Concepts.
One
of
them
is
updating
the
existing
proper
concept
of
0.0.1,
which
are
somewhat
part
of
already
foreign.
A
Python
and
go
and
the
supportive
use
case
where
we
would
look
into
how
to
link
events
to
each
other
or
relate
them
to
each
other
or
somehow
there
are
different
ways
of
looking
into
that.
Connecting
events
is
one
of
them
and
Global
event.
Id
is
another
one,
so
that
this
would
be
character
driven
by
Andrea,
and
you
see
more
or
less
all
of
these
stories
starting
to
people
know,
but
that
doesn't
mean
that
these
people
will
will
be
able
to
finish
them
all
by
themselves.
A
So
you're
very
much
welcome
to
join,
join
in
there
to
help
out
in
and
everyone's
that.
You
see
that
you
can
help
me
out
in
if
you
have
any
inputs,
please
go
into
these
issues
and
help
out
in
solving
them,
together
with
a
person
that
is
assigned
to
them
right
now,
so
all
of
them
are
assigned
now,
at
least
so
we
have
a
driver
for
each
of
them
and
the
ones
which
are
not
currently
on
the
roadmap.
A
D
A
April
or
maybe
May,
and
then
there
are
a
lot
of
items
that
are
not
even
planned
yet
clearly
coming
release
and,
of
course,
if
you
have
any
ideas
on
any
of
these
issues
that
you
think
are
critical
to
get
into
zero,
two
or
zero,
three
don't
hesitate
to
reach
out,
so
we
can
discuss
it.
Those
should
be
brought
in
there.