►
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
B
Well
excited
excited,
I'm
presenting
so
we'll
see
yeah.
A
B
What
do
you
feel?
Do
you
want
to
continue.
A
A
A
B
Definitely
yeah
python
is,
is
pretty
big
and
probably
also
more.
B
A
Yeah
I
know
that
that,
for
like
open
api,
there
is
like
you
can
generate
client
code.
It
doesn't
turn
out
super
nice,
but
maybe
it
can
be
used
as
some
sort
of
a
base
but
yeah.
If
we
had
like
a
formal
specification
in
a
machine-readable
language
of
our
specification,
then
we
should
be
able
to
do
something
based
on
that,
but
it
could
be
a
nice
thing
to
investigate
a
bit
or
ask
around
and
see
like
if
there's
any
project.
B
A
No,
that's
true.
I
guess
I
was
I
should
have
said.
The
interface
has
to
be
nice,
exactly,
as
I
said
like.
If
it
generates
not
so
nice
api
methods,
then
it
can
be
tricky
to
use.
You
might
end
up
having
to
write
a
layer
on
top
of
it
anyway
to
get
to
some
sort
of
acceptable
level.
So
if
we
can
avoid
that,
that
would
be
good
like
it's
good
enough
as
it's
generated
so
to
say,
or.
A
No,
I
was
just
maybe
you
you
were
of
the
opinion
that
we
should
have
our
own,
like
syntactic
sugar
layer
on
top
of
it,
and
that
could
be
good
as
well.
But
it
would
be
nice
not
to
have
to
generate
all
the
underlying
code
and
also
to
be
able
to
to
state
easily
if
we
are
compliant
with
a
spec
or
not,
would
be
great.
B
B
You're,
probably
gonna
need
to
have
tests
for
it
also
yeah
and
that's
when
I
started
writing
the
tests
for
the
current
code.
I
wasn't
realizing
there's
a
lot
of
duplication
ongoing
here.
B
B
Yeah,
it
should
be
so
then
yeah
yeah.
Definitely
I
mean
we're,
probably
not
the
only
one
trying
some
events
I
mean
it
was.
I
don't
know
if
pronounce
the
name
smoothie
or
something.
B
Who
had
the
presentation
on
on
the
jenkins
cloud
events
so
yeah
yeah
yeah?
She
is
also
sounding
like
things,
so
I
don't
know
yeah.
A
I
think
we
have
brought
up
the
topic
before
of
having
like
a
an
actual
specification
cloud.
Events
does
not
have
that.
As
far
as
I'm
aware,
they
mostly
have
documentation
for
their
stuff,
but
I
think
we
came
to
the
conclusion
that
we
did
not
really
want
to
at
least
not
now
aim
for
an
actual
specification
like
a
file
specification
or
a
schema.
It
would
more
be
a
documentation
and
a
specification
in
that
sense.
Do
you
remember
that
discussion
as
well.
B
Yeah,
I
don't
know
for
for
cloud
events,
it's
not
that
much
of
I
mean
it's
not
very
much
of
a
specification.
I
think
the
closest
one
kept
on.
They
have
a
specification
as
far
as
I
remember
like
they
have
at
least
have
a
schema
and
a
full
also
has
a
schema,
but
yeah
there
wasn't
we
wanted.
We
didn't
want
to
do
the
heavy
like
eso
standard
thing.
I
guess
I
think
that
was
what
they
were
opting
out
on,
but
maybe
I'm
remembering
wrong
now.
A
A
B
Of
course,
this
is,
I
guess
this
is
specific
data
in
itself,
so
but.
A
Definitely,
what
do
you
mean
by
specific
data
just
from.
B
My
understanding,
maybe
I'm
wrong.
Maybe
I
should
share
my
screen
here.
A
It
seems
to
support
some
type
of
validation,
I'm
not
sure
if
it
actually
implements
the
validation,
but
from
a
schema
standpoint.
It
has
some
of
that
at
least.
A
A
Yeah,
that
makes
it
a
little
less
appealing,
but
maybe
that
can
be
used
as
a
base
for
something
nicer
afterwards.
A
B
B
A
A
Yeah
I
I
know
I
was
messing
with
one
project
that
was
able
to
like.
I
could
set
some
like
boundaries
and
stuff
in
the
json
scheme,
and
it
generated
just
a
bunch
of
different,
like
example,
requests
for
example,
json
from
it.
B
B
B
A
A
Just
for
my
understanding
there
do
you
mean
that
that
would
be
us
like
code
that
is
running
under
the
api
layer
of
the
library,
or
is
that
something
that
we
would
do
to
like
generate
examples
and
documentation
and
stuff.
B
Maybe
we
don't
want
it
at
all.
I
was
just
trying
to
see
if
we
would
pin
down
something
from
the
meeting
as
we've
been
talking
about
it,
but
maybe
no,
I
didn't
have
any
good
good
idea.
There.
A
Because
it
can
be
useful
if
you
want
to
like
do
like
load,
testing
or
stuff,
like
that,
some
sort
of
us
or
resolution
like
that
to
just
generate
massive
amounts
of
messages
and
just
send
them.
B
There
is
actually
excuse
me.
B
I'm
trying
to
think
now
because
when
I
wrote
the
the
unit
tests
for
sorry.
B
B
B
Which
can
create
a
lot
of
events
and
do
some
here,
so
it's
basically
a
min
full
message
and
so
on
and
so
on
and
all
right.
Because
because
I
use
this
when
I
test.
B
A
B
B
B
B
B
B
B
B
But
you're
still
being
able
to
connect
to
yeah
exactly
and
where
do
they
have
the
sdks
again?
Oh
here
it
is.
B
B
It's
not
that
much
more
or
it's
less
information
that's
needed
here
than
in
in
go
because
ghost
is,
is
typed,
yeah
yeah.
This
seems
to
be
quite
thin.
Actually.
A
A
In
this
library,
or
when
they
actually
call
it,
this
seems
like
like
this
product
id,
for
instance,
I
think
that
becomes
a
python
attribute
further
down
in
the
python
code.
A
Yeah,
that
probably
means
that
there
is
actually
python
code,
because
otherwise
you
wouldn't
be
allowed
to
do
that.
What
would
be
interesting
to
see
is,
can
you
add
documentation
to
that?
Can
you
add
typing
to
it,
or
does
it
add
typing
to
it
would
be
interesting
to
see
like
it
would
be
awesome
if
it
generated
typing
compliant
code
and
had
dock
strings
for
it.
B
That
I
can't
say,
but
dog
strings
would
also
be
kind
of
very
helpful.
Also
true,.
A
Coming
up
now,
I
assumed
just
said,
recording
in
progress
which
made
me
think.
Maybe
I
I
disconnected
and
reconnected
to
the
meeting
or
something
now
so
but
yeah
yeah,
and
I
was
just
looking
into
the
test
code
of
this
cloud
events
generator
code
to
see
if
they
had
any
examples
of
how
the
generated
code
would
look.
But
I
haven't
found
anything
yet.
A
B
B
Yeah
yeah,
you
will
get
to
write
your
correct
valid
event
from
that
one.
A
A
B
A
A
Exactly
so
so,
and
I
think
at
least
visual
city
code
has
support
for
fetching
the
type
information
from
the
docs
string,
but
you
could
also
put
it
in
the
actual
method
called
online
29,
but
it
doesn't
seem
like
they
do
that
because
I
don't
see
any
reference
to
the
data
type
thing
up
there,
but
maybe
that
is
something
that
could
be
could
be
added.
If
we
want
to
improve
this.
This
type
of
generation.
B
A
They
are
using
the
it's
based
on
the
open
api
generator.
So
in
the
comment
above
so
that
is
the
one
that
I
used
a
long
time
ago
to
generate
various
various
libraries
from
open
api
specifications.
I
don't
think
it
actually
uses
that
format
for
specification.
It's
just
online
22,
something
that
is
based
on,
like
the
templates
are
based
on
the
open
api
generator.
But
I
I
think
it's
only
the
templates.
I
don't
think
the
library
is
based
on
that
as
a
whole.
A
A
B
A
A
A
It
is
2009,
so
it's
not
that
old,
I
guess,
but
still
quite
old
yeah,
maybe
it's
based
on
ruby,
then
probably
yeah.
It
seemed
like
that
was
the
initial
implementation
in
the
github
repository
you
are
in
or
in
that
project.
A
But
still,
I
guess
this
would
really
only
deal
with
the
templating
part.
So
then
we
would
have
to
design
the
spec
format
ourselves
or
use.
Oh
sorry,
the
incoming
spec
format
ourselves
or
use
json
schema
for
something
reasonable,
like
that
yeah
yeah,
interesting
to
json
schemas
should
be
fine.
I
guess
because
the
cloud
events
themselves
at
least
the
way
we
are
trying
to
transmit
them,
would
be
fully
jason,
so
yeah.
If
we
could
just
figure
out
some
sort
of
yeah.
No,
actually
that
would
be
fine,
yeah
yeah.
B
Because
you
basically
I
mean
you
could
probably
like
it.
It's
more
or
less
like
compiler
generation
like
you're,
providing
some
kind
of
of
the.
B
A
A
B
Think
it
is
this
one
like
an
image
you
mean.
Oh,
you
mean
like
that.
A
I
have
a
folder
called
schemas
or
yeah
model.
Might
there
we
go.
That
seems
like
a
uml
model
because.
B
Maybe
I
should
reference
this
this
this
jpeg
instead,
if
I
wanted
to
make
it
right
here,.
B
But
I
guess
they
also
have,
because
they
can
you
can
from
this
this
one
here
you
can
generate.
B
So,
let's
see
if
I
have
it
in
markdown,
there
is
a
lot
of
of
text
here.
B
B
Because
here
it
says,
building
specification:
first,
you
have
serve
and
you
have
build.
A
B
A
A
But
I
think,
like
as
a
general
summary
of
the
whole
concept
it
seems
like
it
would
help
adoption
of
the
spec
if
we
were
able
to
to
define
a
schema
in
such
a
way
that
it's
likely
that
people
can
generate
the
library
if
in
their
own
favorite
language.
Even
if
we
don't
supply
a
language,
a
library
in
that
language,
because
I
don't
think
we
want
to
maintain
too
many
different
libraries
for
too
many
different
languages,
either.
B
B
So
maybe
we
should
say
something
of.
A
B
B
Out
of
it,
yeah
that's
good!
That
was
a
good
discussion.
So
thank
you
and
then
see
you
on
monday,
then
yeah
yeah,
good.