►
From YouTube: CNCF Serverless Working Group - 2018-04-23
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
A
A
C
F
Doug
everyone
yeah
I,
went
to
Sedona
in
Arizona
was
beautiful.
It's
one
of
those
little
places
that
people
say:
oh,
it's
so
beautiful,
so
beautiful,
and
then
you
get
there
and
you're
like
wow.
It
really
is
really
is
so
beautiful.
It's
been
a
few
days,
hiking
and
just
being
outside
and
away
from
the
screen
cool.
D
H
H
H
C
H
H
F
F
Let's
say
so:
I
kind
of
outlined
the
goals
of
my
presentation
in
the
beginning
of
this
issue.
You
know
want
to
introduce
cloud
events
and
announced
the
initial
version
that
we
finished
make
sure
we
communicate
the
why
you
know
why
this
is
important,
why
it's
going
to
be
a
big
deal
now
and
in
the
future
and
communicate
use
cases
of
cloud
events
when
I
kind
of
paint
a
picture
of
possibility
of
what?
F
What
an
event
will
enable
in
the
future
and
then
also
make
it
real
for
the
audience
by
showing,
by
showing
up
just
a
taste
of
this
in
a
real
demo,
unless
they,
of
course
tell
our
story
of
collaboration,
celebrate
the
people
who
have
been
working
on
this
so
anyway,
I
only
have
I,
think
3035
minutes,
I
believe
in
the
talk
at
the
same
time,
there's
a
lot
of
people
who've
expressed
interest
in
participating
this
demo
and
there's
a
lot
of
stuff.
We
could
do
so.
It's
a
bit
of
a
challenge
here
for
inspiration.
F
I've
outlined
a
painful
abuse
cases
for
discussion
topics,
things
that
we
can
illustrate
and
then
I
followed
up
in
the
comment
of
kind
of
something
I
think
that
we
might
be
able
to
pull
off
and
that
may
be
able
to
accommodate
all
the
people
who
want
to
participate
in
this
comments
is
a
proposal
for
a
ecommerce.
An
adventure
of
an
ecommerce
store
and
I'd
simply
walked
through
it.
F
During
my
presentation
and
I
pretend
to
be
a
user
and
I
do
a
couple
actions
in
this
ecommerce
application,
I'd
register
for
the
application
I'd
view
a
couple
products,
I
didn't
encounter.
An
error
and
I'd
also
purchase
a
product,
and
these
actions
are
gonna,
be
expressed
as
events,
and
these
events
can
integrate.
They're
gonna
be
cloud
events,
of
course,
I
think
I
might
just
publish
them
directly
from
the
client
side
of
the
of
the
web
application
and
I
outlined
a
few
events
in
this
flow.
F
There's
the
user
profile
is
created
that
happens
when
the
user
is
registered.
A
storage
object
is
created.
That
happens
when
we
fetch
the
user's
profile,
image
and
errors
received.
That
happens
when
the
user
is
encounters.
An
error
on
the
client-side
and
get
some
type
of
500
status
code,
a
user
viewed
event,
which
happens
when
the
user
is
simply
viewing
a
product
on
the
website
and
a
user
purchased
event,
which
of
course
happens
when
when
I
pretend
to
go
and
purchase
a
product.
F
The
way
I
think
this
can
work
is
if
we,
if
we
incorporate
our
company's
project,
called
the
event
gateway.
The
whole
thing
was
designed
as
a
event
router
for
the
surrealist
era,
and
it
could
simply
anyone
can
hook
up
there
fast
product
to
it
directly
and
I
could
basically
rig
up
this
whole
demo
to
publish
events
from
the
client
side,
pass
them
through
to
the
event
gateway
through
to
the
various
companies
fast
products
in
in
their
respective
platforms.
They
could
also
do
some
cloud
events
handling
I'm,
not
sure
how
far
they
want
to
take
it.
F
It's
really
up
to
them.
But
this
is
the
general
story.
I
was
thinking.
The
question
is:
can
we
can
we
pull
it
off,
of
course,
because
there's
there's
a
there's
a
lot
in
here
and
how'd
it?
How
does
everyone
want
to
integrate
and
my
general
thoughts
were?
You
know
we
publish
these
events
and
you
know
people
can
pick
what
what
they
want
to
do
with
them,
but.
G
F
Yes,
we
could
do
all
that
it's
it'll,
be
a
complicated
architecture
and
difficult
to
rig
up.
The
other
question
is
a
observability.
You
know
my
goal
here
is
to
make
it
real
for
people.
How
do
we
actually
show
them
what's
going
on,
and
how
do
we
show
them
across
all
these
across
all
these
integrations?
What's
going
on
now,
god
events
can
solve
this
problem
because
we
have
consistent
made
it
metadata.
F
Finally,
and
we
can
put
tracing
information
in
there
in
the
long
term,
we're
gonna
be
we're
gonna,
be
able
to
nail
that
and
provide
a
great
event
driven
observability
story
thanks
to
cloud
events,
but
as
for
the
demo,
which
is
coming
up
very
soon,
I'm,
not
sure
how
much
I'm
gonna
be
able
to
pull
off
and
that's
contingent
on
the
complexity
of
the
demo
itself.
Well,.
C
That's
that's
actually
something
I
was
trying
to
wrap
my
head
around
because
I
understand
everything.
You
said
there
in
terms
of
the
demo.
You
got
a
client.
Generic
events
goes
through
gateway.
It's
out
events,
that's
function,
calls
to
all
the
various
platforms
and
each
platform
then
receives
it
at
the
next
step
that
I'm
repping
having
to
wrap
my
head
around
in
terms
of
what?
What
what?
How
did
you
envision
presenting
the
output
from
all
our
various
companies
receiving
these
things
in
your
demo,
environment
I
mean?
C
Were
you
thinking
something
as
simple
as
having
a
whole
bunch
of
different?
You
know,
mini
Windows
said
here's
the
Microsoft
one,
here's
the
IBM
one,
here's
the
VMware
one
and
look
they
all
received
events.
You
could
see
that
they
all
got
it.
I
mean.
How
are
you
envisioning
this
playing
out
or
being
displayed
to
people.
F
Great
question:
it
depends
of
course,
what
what
providers
want
to
do
with
this.
You
know,
because
we
have
a
centralized
piece
of
middleware,
which
all
this
stuff
will
be
routing
through.
We
can
always
put
in
something
to
add
tags
and
use
that
to
create
some
type
of
visualization,
afterward
I,
don't
know
how
much
of
that
we're
gonna
be
able
to
rig
up
before
the
demo,
so
I
might
just
have
to
kind
of
fake
it
for
the
demo
yeah.
G
And
I
have
another
idea,
you
know
maybe
there's
like
a
Twitter
account
or
you
know,
an
object
bucket
where
every
function
after
it
gets
the
event,
generates
a
tweet
or
writes
a
file
or
something
golf.
And
then
you
know
you
can
open
a
Twitter
feed
or
object
bucket.
You
know
insert
and
show
all
those
responses.
G
C
G
G
F
Yeah,
the
challenge
here
is
to
define
a
simple
story
that
everybody
can
integrate
into
and
that
Twitter
example
is
actually
a
pretty
good
one.
I
guess
I
also
want
to
wanted
to
try
and
make
sure
that
we're
showing
off
the
value
of
cloud
events,
and
what
can
we
do
to
show
off
the
value
of
cloud
events
in
that
Twitter
example?
You
think
you're
on.
H
G
A
A
Well,
we
can,
we
can
have
yeah,
there's
there's
function
as
a
service
servers
endpoints,
and
there
are
publishers
and
I
think
if
we
can
show
that
the
functions
as
a
service
endpoints
can
receive
and-
and
they
said,
cloud
events
from
all
kinds
of
different
publishers.
If
we
can
basically
just
show
that-
and
that
might
be
such
that
you
know,
you
send
an
event
and
then
the
code-
that's
nothing
just
dumping
the
contents
of
that
event
into
a
log,
and
it
does
so
on
open
risk
and
the
Sun
on
our
platform.
A
There's
some
other
platforms
and
then
you
can
go
and
publish
to
that
from
different
providers
and
you
be
wire
them
together.
That's
that's
already
you
win
and
for
that
we
don't
need
to
have
a
fancy
scenario
and
defense
scenario
is
harder
and
more
work.
I
guess,
then
just
putting
having
existing
event,
publishers,
you
know
changing
them
to
go
and
publish,
or
you
know,
make
up
an
event
publisher
that
that
published
an
event
but
where
you
can
go
and
generically
parse.
That
thing.
G
Opening
people
can't
consoles
seems
a
little
complex,
I.
Think
that's
why
having
something
like
either
throwing
an
object
in
a
bucket
or
a
Twitter
feed,
or
anything
that
you
know
can
show
all
the
messages
writing
from
all
the
different
fast
platforms
will
be,
will
make
it
simpler.
I
do
agree
that,
having
more
than
one
publisher
allows
us
to
make
a
stronger
point
versus
having
a
single,
you
know,
even
maybe
a
one
event
from
Google
one
event
from
Asia
or
you
know,
etcetera.
A
Yeah,
and
and
and
so
unifying
all
the
all
the
kinds
of
events
that
we
all
have
like
like
getting
on,
because
what
you?
What
what
happens
here
with
the
events,
is
that
there
are
some
semantic
alignments
that
I
don't
think
we're
ready
for,
like
the
storage
object
created
thing,
there
is
no
such
event
that
all
of
us
publish
right,
yeah,
that's
gonna,
be
Queens.
A
Now
you
would
have
to
normalize
twice
you
normalize
from
a
a
whatever
current
event.
Format
exists
to
the
shared
event
formers
that
we
have
agreed
to
and
then
now
you're
doing
a
second
transformation
where
you
need
to
have
the
storage
event
and
need
to
go
and
normalize
that
across
platforms
and
that's
something
that
work.
That's
just
not
as
something
we've
done
in
this
form.
Right.
G
A
I
agree:
I,
agree
that
visualization
of
that
you
got
the
event
that
if
you
want
to
do
this
web,
where
Twitter
or
where
has
some
other
platform,
that's
that's
fine.
I
mean
you
show
that
you
show
the
mechanics.
You
just
want
to
surface
the
fact
that
that
someone
has
gotten
a
call
and
then,
as
as,
and
you
want
to
make
that
visible
somewhere.
H
A
G
H
G
To
SNS
I
say:
here's
my
HTTP
endpoint
send
a
message
to
it,
and
the
HTTP
endpoint
will
get
you
know
using
an
API
gateway
will
get
to
the
function.
So
what
is
the
role
of
the
event?
Router
in
that
scenario?
Is
that
it,
instead
of
registering
the
function,
you
etc?
You
register
a
generic
location,
and
that
would
route
based
on
some
policy
or
is
that
to
register
things
that
don't
have
a
web
walk
or.
F
If
you
wanted
to
to
create
a
scenario
where
you're
reacting
to
an
event
from
AWS
s3,
we
could
have
that
s3
event
be
published.
It
could
be
sent
via
SNS
over
to
a
lambda
function.
The
lambda
function
could
normalize
it
and
the
lambda
function
could
send
it
anywhere
to
be
honest
or
can
go
through
the
event.
Router
the
event
router
to
be
honest,
I'm
I,
think
the
event
router
is
a
very
our
event.
Router
is
a
very
convenient
way
to
rig
up
this
demo.
At
the
same
time,
I
don't
want
it
to
be
totally
centered.
F
G
But
if
we
can
show
something
interesting
about
the
event,
router
I
think
it's
a
it's
a
plus
I'm
just
trying
to
see.
What's
this
interesting
thing,
because
if,
if
you're
just
forwarding
an
HTTP
request,
people
say:
okay,
why
do
I
need
it?
Here's
something
more
interesting,
maybe
transforming
an
event
or
maybe
monitoring.
You
know
something
then
shershow's
valuers,
but.
C
Was
to
sort
of
was
the
word
I
look
for
to
sort
of
interject
the
interoperability
in
the
sense
that
sure
you
could
take
an
event
producer
hook
it
up
to
an
event
consumer
and
they
could.
That
could
work
just
fine,
but
you
also
could
very
well
have
just
set
yourself
up
to
be
locked
in
to
to
one
or
the
other,
but
sticking
the
event
router
in
the
middle,
where
all
five
or,
however
many
platforms
are
all
hooked
into
that.
F
F
It
seemed
like
there
was
some
consensus
earlier
on
in
this
call
that
if
we
just
simply
publish
the
same
event
to
multiple
fast
providers,
that
that
would
be
enough
to
show
off
right
now
is
that
is
that
the
set
is
that
what
people
were
communicating
earlier
and
is
this?
What
we
think
will
be
enough
to
you
know:
win
arts
and
minds
and
developers.
It
I
think
if
we
not.
A
The
same
event,
but
so
we
can
publish
arbitrary
events
from
arbitrary
sources
if
they
comply
with
our
spec
right.
So
I
have
this
I
posted
this
earlier.
The
email
unfortunately
go
out
have
this
generic
function,
which
basically
goes
to
a
natural
function
now
which
goes
and
takes
any
event
current
events
and
turns
it
into
a
cloud
event.
So
you
can
hook
up.
You
know
anything,
that's
in
our
platform.
We
can
now
spit
out
as
a
cloud
event
and
then
send
it
to
everybody.
I.
G
Think
what
we
need
Austin
is
is
two
things.
One
is
show
more
than
one
event,
maybe
potentially
even
from
two
separate
cloud
providers,
just
for
the
sake
of
showing
off
the
interoperability
and
yeah
and
then
and
then
we
need
to
make
it
visual
like
either
the
Twitter
or
any
other
idea
where
you
know
people
can
relate
to
that.
It
actually
arrived.
F
Okay,
so
I,
like
this
Your
Honor
I,
think
the
Twitter
scenario
using
Twitter
to
make
it
visual
is
great
because
it
asked
and
a
ver
ality
built
into
it.
Potentially,
you
know
people
can
look
at
it,
interact
with
it
and
I
think
that's
a
great
solution.
What
is
the
premise,
what
is
the
scenario
and
how
do
we
get?
You
know?
How
do
we
get
more
than
one
event
from
each
provider
and
integrate
Clements?
You
know
functions
and
Azure
events
into
this,
as
well
as
people
goals
as
well
as
well
as
other
people's.
F
A
C
A
G
A
A
Meant
that
code-
and
you
just
looked
at
so
this
is
this-
is
the
this
yeah
this
so
so
that
is
what
this
does
is
basically
just
prints
out
the
cloud
event
as
the
body
of
ecology
versus
comes
in,
so
we
can
make
that
function,
just
speak
to
Twitter
and
just
you
know,
take
the
events.
There
are
parts
of
the
events
and
then
just
tweet
that
out
and
then,
as
you
deploy
that,
and
you
apply
any
a
past
platform
with
different
scaffolding
around
it
is
it's
gonna
go
and
tweet
and
then
the
other
handler.
A
So
this
is
the
cloud
event
and
that's
that's
being
able
to
parse
the
cloud
event
per
se,
the
other
one,
that's
the
event
handler.
That
knows
how
to
turn-
and
this
is
something
that
now
Nate-
that
it
uses
now
our
native
binding
to
event
grid.
That
knows
how
to
take
our
event,
current
events
and
turns
it
into
cloud
Yvette's
effectively
and
then
goes
and
posts
them
out.
So
I
have
kind
of
both
ends
of
this.
This
is
this
is
hooking
into
our
platform
and
I
have
a
hard
wired
URL
here.
A
So,
basically,
you
would
kind
of
deploy
your
your
bridge,
your
bridge,
to
go
somewhere
else
here.
I
didn't
want
to
make
this
too
fancy
and
then
on
the
other
side,
you
have
your
your
your
tweeting
thing
and
in,
if
so
with
this,
we
so
from
the
my.
So
this
is
the
Microsoft
proprietary
proprietary.
If
you
will
bridge
that
translates
from
our
stuff
into
generic
called
event
stuff
and
on
the
other
side,
that
function
is
able
to
tweet
that
out.
A
If
we
I
think
already,
you
know
no
matter
a,
we
need
to
go,
and
maybe
you
need
to
go,
build
a
little
bit
of
a
scenario
around
it,
but
already
if
I
can
go
and
and
hook
this
up
and
I
can
go
and
push
with
four
deployments
of
this
function,
to
open
whisk
and
over
to
AWS,
I,
don't
know
and
somewhere
else
and
I
can
get
tweets
from
all
of
those
different
implementations.
That's
already
who
win
I.
F
Agree
with
that
actually
and
I
think
we
could
show.
The
story
could
also
be
here's
something
coming
from
Azure
to
Google
and
I,
hear
something
from
coming
from
Google's
Azure,
here's
something
coming
from
AWS
sure
and
here's
something
coming
from
AWS
that
is
now
will
be
reacted
to
by
Azure
Google.
You
know
IBM
and
multiple
ones,
I
think,
there's
a
good
story
to
tell.
A
Yeah
I
mean
you
can
go
and
write
this.
This
mapping
function
here
such
that
the
mapping
function
knows
five
URLs,
you
know
all
of
all
different
targets
rolls
the
dice
and
then
you
know
the
event
goes
this
way
or
that
way
or
that
way,
and
then
they
all
surface
out
in
the
Twitter
feed
all
together,
yeah.
C
A
They
tweet
about
it
and
we
can
make
it.
We
can
make
it
a
single
single
tweet
stream,
or
we
can
all
have
our
own
tweet
accounts.
For
that.
That's
that's
up
to
how
we
wanna
do
it
and
how
we
think
it's
it's
better.
We
can
I,
think
everybody
having
their
own
Twitter
account
for
this
purpose
and
then
having
a
Twitter
feed.
That
goes
to
subscribes
and
all
of
those,
maybe
the
fanciest
one.
Okay
I,
like
it
simple,
and
then
we
show
this
a
tweet
deck
so
that
it
actually
screams.
C
I
F
A
G
F
F
F
A
Say
so,
let's
say
I'm
building
a
thing
that
goes
and
uploads
clicker
pictures
into
a
storage
account
that
then,
will
contain
links
to
those
pictures
because
I'm
gonna
make
that
account
public.
And
if
you
understand
my
my
my
event,
which
is
easy
for
you
to
tell
because
you
have
a
cloud,
you
have
an
event
event
type.
Then
you
can
actually
go
and
dig
into
that
into
the
details,
because
you
then
you
know
what
it's
all
about
and
then
you
could
actually
go
and
tweet.
That
picture.
D
G
G
C
A
C
F
F
A
G
G
F
A
Do
the
following
thing:
I
will
write
a
periodic
agents
that
goes
and
fetches
a
random
picture
from
my
wonderful
aviation,
geek
photo
library
and
then
we'll
go
and
take
one
of
the
thumbnail
sizes
and
throw
that
into
an
azure
storage
account
and
then
I'm
going
to
use
that
this
gateway
effectively
to
be
sitting
between
event
grid
and
an
arbitrary
and
any
number
of
arbitrary
services
and
I
will
basically
just
use
a
random
function
to
go
and
balance
across
them.
And.
J
A
Of
you
cloud
events,
that
is,
the
Microsoft
storage,
a
blob
created
event
of
which
I
will
tell
you
the
detail,
data
schema
and
then
out
of
the
data
scheme,
I
fish,
the
URL,
and
then
he
can
go
and
tweet
that
you
got
it
that
you
got
a
that.
You
got
this
event
and
then
you
can
also
include
the
image
URL
and
that
will
actually
then
show
in
the
Twitter
feed
feed.
A
Since,
since
you,
since
you're
gonna
get
an
event
that
has
a
picture
on
it
because
I'm
generating
that
already,
you
could
do
that.
Actually,
since
since
Watson
IOT,
for
instance,
has
sorry
Watson
what
IOT
has
all
kinds
of
fancy
imaged
in
an
image
classification
logic
in
it,
you
could
go
and
classify
that
picture
and
figure
out
what
airplane
it
is.
H
A
F
G
F
G
A
B
G
F
A
Since
we
had
this
Twitter
idea,
I
think
for
my
for
my
storage
event.
I
would
propose
that
you
guys,
if,
if
we're
doing
this
Twitter
thing,
that
everybody
writes
to
a
Twitter
feed
and
the
way
they
write
to
the
Twitter
feed,
is
they
pick
up
some
properties
from
some
attributes
from
our
cloud
event
and
say
this
is
what
I
got
and
then
they
can
in
the
image
case
since
you,
since
everybody
understands
that,
can
then
go
and
take
the
image
URL
and
just
include
that
in
the
tweet
as
the
image
element.
A
And
that's
that's
how
I
think
about
it.
It's
like
I
would
literally
everybody
who
writes
that
function
in
their
platform,
which
will
probably
be
if
we're
doing
this,
a
node
B
the
same
code,
but
just
with
different
scaffolding
around
it.
Yeah
we'll
give
me
your
eye
and
then
I
will
go
in
and
basic
make
a
list
of
your
eyes
in
this
function
here
in
my
deployment
and
then
choose
a
random
number
and
for
every
call,
I
get
and
so
I
randomly
spray
across
them.
Oh.
A
F
All
right
it
sounds
like
we
have.
We
have
to
pretty
cool
examples.
We
have
a
Tobias
two
nucleo,
something
happens
on
s3
nucleo
is
going
to
react
to
it
doing
maybe
sentiment
analysis
of
a
text
file,
something
like
that
and
write
it
to
Twitter.
That's
a
cool
example
because,
that's
you
know
the
major
cloud
platform
combined
with
an
open-source
platform
I
think
that'll
be
pretty
compelling
to
users,
and
then
we
have
the
azure
example
too
many
fast
providers,
whoever
wants
to
integrate
with
that,
can
write.
Some
functions
to
do
so.
F
A
F
H
F
H
F
F
It's
all
in
the
marketing,
you
know
what,
let's,
let's
just
move
forward
with
these
two,
these
two
examples
and
then,
let's
see
a
see
where
we
get
to
with
these.
So
there's
the
ADA
base.
Nucleo
example,
Iran
I,
think
that's!
The
ball
is
gonna,
be
in
your
court.
On
that
one
it
sounds
like
you
know.
You
just
write
a
lambda
function
that
dad
transforms
to
a
cloud
event
which
sends
it
over
to
your
platform.
Since
we're
already
doing
an
image
example.
F
I
think
the
sentiment
analysis
of
a
text
file
or
doing
doing
some
other
type
of
data
processing
would
be
compelling.
That's
my
opinion
at
least,
and
then
regarding
the
azure
to
many
scenario.
Our
team
can
certainly
write
one
or
multiple
functions
to
react
to
that
image.
Uploaded
event
on
Azure
storage
Clemens,
if
you
could
just
you
know,
share,
share
the
code
and
give
us
an
example
of
what
that
event
looks
like
and
everything
we
could
get
started
and
we'll
it
will
start
all
this
by.
Let
me
outline
all
this
and
a
github
issue.
F
C
Easy
so
I
apologize,
I
had
to
step
away
for
a
second
home
I
had
a
phone
call,
but
as
I
was
coming
back
there
Austin.
You
made
some
comment
about
what
particular
platform
talking
to
another
particular
platform,
and
you
called
them
up
by
name.
Is
it
possible
for
us
to
write
this
up
in
such
a
way
that
anybody
can
choose
to
participate
on
either
side,
or
at
least
our
receiving
side?
That's.
G
D
G
H
F
Yeah,
that's
right,
I
think
keeping
it
simple,
especially
your
example
you're
on
just
because
that's
how
I
think
the
story
should
start
in
the
demo.
It's
just
like
here's,
a
one
to
one
connection
across
platforms
and
then
the
next
chapter
in
that
story
is
here's
a
one-to-many
connection
across
platforms
and
I.
Think
that's!
That's
fine!
Let
me
let
me
try
and
write
this
up
in
a
github
issue
and
we'll
get
some
feedback
hopefully
on
on
Thursday,
but
but
this
is
pretty
good
in
my
opinion.
Would.
F
B
C
C
I
was
gonna,
say
it's
not
because
I
was
gonna,
have
a
function
that
lets
anybody
post
to
me
and
I
was
gonna,
just
do
something
with
it,
but
Mark
had
mentioned
something
about
usernames
and
passwords.
Are
you
guys,
assuming
that
your
functions
are
gonna,
require
authentication,
no
I
I,
don't
think
we
should.
We
should
worry
about
that.
Okay,
I,
agree
to
I
just
want
to
make
sure
yeah.
F
Works
for
me:
okay,
cool,
okay,
Doug,
I,
I.
Think
I
could
write
this
down
in
a
way
where
people
can
plug
in
I.
Think
we
should
keep
the
first
example
simple,
just
showing
that
one
to
one
example
between
AWS
and
nucleo.
The
second
example
Azure
to
many
is
gonna,
be
a
good
candidate
for
other
people
to
to
plug
in
and
I'll
write
down
some
criteria
as
to
what
that
should
look
like
people
want
to
integrate,
and
then
maybe
we
could
take
it
from
there.
Yeah.
H
A
One
thing
it
might
so
one
thing
that
might
be
required
for
the
Azure
to
anybody
thing
is
that
there
so
we
require
and
I'm
asking
my
genera
team
for
what
the
white
listing
procedure
was.
The
white
listing
procedure
looks
like
well,
we
have
a
head
shake
that
is
kind
of
a
parallel
function,
so
you
don't
need
to
show
it
and
I
can
give
that
to
you
how
the
head
shape
looks,
but
we
have
kind
of
this
anti-abuse
function
which
I'm
trying
to
formalize
in
our
web
book
spec,
but
that's
kind
of
in
place.
A
F
A
The
point
is
that,
as
you
should
be
able
to
go
and
like,
and
as
are
things
should
be
able
to
talk
to
all
those
things
right.
So
let
me
let
me
talk
to
that.
Let
me
talk
to
our
to
our
guys
in
in.
In
doubt,
we
can
go
and
talk
to
your
gateway,
okay,
okay,
so
we'll
we'll
figure,
we'll
figure
figure
this
out
I'm
just
setting
this.
This
is
something
that
is
in
the
picture.
A
F
F
H
F
F
J
A
F
You're
on
I
got
a
quick
question
for
you
in
the
first
example,
which
is
now
AWS
too
many
doing
some
type
of
sentiment,
analysis
of
a
text
file.
Would
you
be
okay?
If
we
rigged
that
example
up
through
our
event
gateway,
we
could
author
the
land
a
function
that
does
the
transform
and
just
right,
yeah
and
that's.
G
D
F
G
A
The
email
that
the
email
that
I
said
that
I
said
earlier
to
the
to
the
list
actually
contains
an
example
already
what
I?
What
I
still
have
to
do
is
to
send
you
an
example
with
where
the
the
the
URL
actually
the
URL
for
that
for
that
it
for
the
image
block
actually
resolves,
and
you
can
get
at
it
because
so
for
that
I
need
to
make
on
public
turbot.