►
From YouTube: 2023-09-07 Crossplane Community Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right
so
recording
has
started,
and
this
is
the
September
7th
2023
cross
plain
community
meeting
I
will
go
ahead
and
in
the
zoom
chat
now
I
will
drop
a
link
to
the
agenda
documents,
so
everyone
who
has
already
joined
the
meeting
has
direct
access
to
the
agenda
Doc
and,
as
always,
it
is
an
open
and
living
document,
so
feel
free
to
add,
suggestions
and
topics
that
you
all
want
to
get
into
later
on
in
the
in
the
upcoming
agenda.
So
we'll
jump
right
on
into
it.
A
I,
don't
think
I
just
looked
this
morning
and
I,
don't
think
we
had
any
cross-plane
run
time
or
core
cross
plane,
patch
releases
or
regular
releases
since
the
last
community
meeting
so
I,
don't
think.
There's
anything
to
talk
about
there.
A
I
have
I,
do
have
a
vague
memory
in
my
mind
that
I
do
not
remember
what
it
was
for,
but
some
PRS
that
we
were
backboarding
recently
to
the
previous
branches
like
the
1.12
or
13
1.12
branches,
so
I
think
there
may
be
a
patch
lease
that's
coming
soon,
so
if
maybe
we'll
get
into
that
in
the
in
the
the
project
board.
But
if
anyone
can
can
jog
my
memory
or
knows
exactly
what
I'm
talking
about
there
right
away,
please
do
speak
up.
A
All
right,
so,
let's
do
a
quick
look
at
the
roadmap,
so
I
think
one
of
the
biggest
things
and
most
activity
that's
going
on
right
now
is
on
composition,
functions,
there's
a
core:
a
group
of
people
in
a
Sig.
That's
formed
around
that
and
making
a
lot
of
progress
on
that
so
I
wanted
to
when
we're
in
this
upfront
status.
Section
here
in
Milestone,
checkup,
section
I
do
want
to
hear
about
some
of
the
progress
there
and
later
in
the
agenda.
A
We
have
a
specific
topic
that
we
wanted
to
socialize
and
share
with
the
audience
here
around
some
some
design
decisions
being
made
with
composition
functions,
so
we
can
save
that
for
later
on,
but
I
definitely
wanted
to
hear
about
progress
on
the
composition,
functions,
the
generic
usage
and
deletion
ordering,
and
maybe
the
composition,
validation,
stuff
as
well,
and
then
environment
configs
too,
because
I
know,
there's
progress
in
all
of
those
and
I
think
the
latest
information
and
decisions
Etc
all
of
those
will
be
very
useful,
so
nick
filippi,
focusing
on
composition
functions.
A
B
Of
I
feel
pretty
good
about
the
1.14
Milestone,
it's
not
as
obvious
from
this
tracking
issue.
Unfortunately,
but
you
can
kind
of
break
it
up
into
my
say,
four
work
streams.
Let
me
see
if
I
get
that
correct.
One
is
the
base
functionality
and
cross
plane.
Just
making
sure
it's
possible
to
use
functions
like
functions
can
run
the
beta
version
functions
in
our
package
that
you
can
install.
So
can
you
install
a
package?
Can
you
then
call
that
package
and
you
know
send
send
run
functional
requests
to
it?
B
To
actually
basically
ask
it
to
do
some
kind
of
composition
for
you
that
is
I
I'm
hopeful
to
get
it
done
by
the
end
of
the
day
today,
I've
actually
just
been
rearranging
meetings
and
trying
to
clear
out
a
day,
so
that
I
actually
had
some
time
to
work
on
it
today,
where
pretty
much
just
in
the
ewe
test
and
final
polish
of
that
I
started.
B
Writing
a2e
tests
yesterday
and
just
found
a
few
places
where
the
plumbing
wasn't
quite
correct,
so
I'm
sort
of
just
getting
all
the
pieces
together
for
that
and
once
that's
you
know,
presuming
I
get
the
e2e
test
done
today.
There's
going
to
be
some
time
for
review,
it's
a
pretty
big
PR,
so
it'll
probably
hopefully
merge
next
week
unless
I
miss
something
huge.
So
that's
that's
kind
of
just
the
base
base
foundation
and
architecture.
B
Then
a
few
other
things
that
we
hope
to
or
plan
to
We
tend
to
do
in
the
1.14
timeline,
improved
tooling,
for
building
functions
so
figuring
out.
You
know,
we've
got
the
coupon
cross
play.
You
know,
there's
some
tentative
plans
to
have
sort
of
maybe
do
some
different
things
with
our
CLI,
but
basically
we
want
a
way
to
from
some
CLI,
build
a
function
and
push
a
function
to
the
marketplace.
B
Potentially
there's
some
extra
sort
of
credit
work
that
we
could
do
there.
That
would
involve
something
like
a
sort
of
a
Helm
template
render
command
for
composition
so
that
you
could
actually
output.
What's
going
on
in
a
composition
and
we'll
see
that
client-side
before
you
apply
it,
then
we
plan
to
have
some
functions
ready
to
go
so
functions
that
are
generally
reusable
I.
Think
there's
probably
two
functions
that
we're
going
to
have.
One
is
probably
going
to
be
go
templates
which
will
feel
like
using
Helm,
basically
and
another.
B
One
is
Passion
transform,
so
basically
native
cross-blade
composition,
as
it
is
today,
but
implemented
as
a
function.
So
let's
see
that
was
the
architecture
that
was
tooling
and
that
was
building
some
functions.
Jared
did
I
forget
any
other
work
streams
I'm.
What
else
is
there
I
feel
like
I'm,
forgetting
one.
A
B
Well,
there's
documentation
oh
and
an
SDK
for
for
writing
functions,
which
is
probably
something
that
we'll
kind
of
learn
as
we
as
we
build.
These
two
functions,
I
actually
already
built
a
patch
and
transform
function,
so
so
I've
got
some
learnings
from
that
already.
A
Awesome
and
then
Esky
anything
to
add
on
your
side.
Philippe
I,
don't
think
is
here
today,
I
ask
you
anything
that
you
want
to
add
to
that.
A
Sweet
this
is
going
to
be
pretty
exciting
release
with
just
this,
but
that's
not
all
we
have
all
right
and
Hassan.
You
showed
off
the
order.
Deletion,
usage,
tracking
sort
of
stuff
last
community
meeting,
I
think
which
is
very
cool
to
see
anything
like
any
blockers
or
obstacles
that
have
come
up
since
that
demo
that
you
want
to
share
or
everything's
on
track.
B
C
For
the
implementation
PR,
so
the
pr
got
some
like
reviews
and
we
are
like
discussing
the
last
bits.
So
hopefully
we
can
get
it
merged
either
tomorrow
or
early
next
week.
A
A
Last
week,
I
was
and
seeing
everything
working
I
didn't
assume
they
were
going
to
be
crazy
mountains
to
climb
still
after
that,
okay
and
then
let
me
see
if
we
can
look
at
this
because
Felipe
isn't
here
but
I
know
there
was
a
certain.
There
was
an
update.
Yes,
okay,
this
is
the
update.
A
I
was
thinking
out
that
I
did
not
read
thoroughly,
but
I
thought
was
important
to
to
at
least
consider
here,
because
this
was
going
to
be
in
three
phases
with
the
last
and
final
phase
being
you
know,
rendering
resources
out
in
their
in
their
entirety
to
do
validation
upon
them,
and
you
know
everything
all
the
inputs
and
everything
considered.
So
it
looks
like
Philippe
arrived
at
a
conclusion
that
that's
not
actually
a
feasible
goal.
A
The
details
are
included
here
in
the
rest
of
his
comments,
so
we're
pretty
much
I
think
at
a
point
where
the
beta
level
functionality,
I
think
is
fairly
rounded
out
Jean.
Is
that
correct,
or
is
there
any
big
things
that
are
still
outstanding
for
I'm
calling
validation,
work
beta.
E
You
know
it's
it's
pretty
much
done
apart
from
any
bugs
that
might
crop
up
we're
not
going
to
be
changing
anything
at
this
point.
Awesome.
A
Sounds
good
that
was
a
good
update
there,
okay
and
then
environment
configs
there's
been
a
lot
of
work
going
on
that.
Still
this
so
just
to
be
clear.
This
was
not
something
scheduled
in
1.14,
but
there
has
been
a
lot
of
traction
and
effort
on
it,
so
is
who
is
the
best
to
be
able
to
provide
a
kind
of
an
overall
status
update
on
that
where,
where
environment
configs
is?
E
So
max
is
not
here,
but
Max
has
been
pushing
forward.
A
few
features
and
Felipe
has
fixed
a
few
bugs
as
well.
So
this
kind
of
like
General
progress
being
made
towards
the
you
know
getting
environment
configs
into
beta
out
of
the
discussion
of
generic
cross-resource
references.
E
There
was
also
you
know,
decision
made
to
to
not
push
that
forward,
but
rather
to
to
work
on
shaping
the
environment,
conflicts
API
further
and
Frederick
has
a
opening
show
around
that
that
he
can
speak
to,
but
we
will
still
not
reach
beta
in
in
the
1.14
time
frame,
but
we're
definitely
making
a
lot
of
progress
in
in
terms
of
where
we
will
be
comfortable
with
the
final
shape
of
it
eventually
and
1.15
seems
like
a
safe
bet
where
we
can
say
that
we'll
reach
beta.
A
Do
you
have
where
what
is
the
new
issue
you've
opened,
then
to
kind
of
capture?
That
is
that
something
that's
underneath,
like
the
general
umbrella
tracking
issue
for
environment
configs?
No.
F
It's
not
I
mean
I
I
wanted
to
describe
that
as
well.
If
we
should
include
it
or
not
in
that
Jared.
E
If
you
go
to
the
generic
cross
resource
references
proposal
and
you
look
at
the
last
comment-
there's
a
link
to
the
to
the
issue
project.
A
C
F
So
this
issue
here
is:
is
this
the
right
one
yeah
no
I
mean,
and
it's
not
included
in
that
epic,
so
yeah
I
didn't
actually
ask
the
maintainers.
If
we
should
do
that
or
not.
E
E
It
in
the
Epic
whether
we
we
act
on
this
or
not
I,
think
it's
good
to
include
it
as
part
of
the
list
of
the
Epic.
A
And
so
this
would
be
okay
right
right,
because
this
is
a
kind
of
extending
the
existing
environments
API
for
this
type
of
functionality,
it
was
being
considered
for
cross
resource
references.
That
is
that
right,
right.
F
A
F
We
were
kind
of
speaking
about
resolving
things.
Why?
Why
environments,
it
was
basically
just
it-
was
taken
out
of
that
proposal
and
submitted
a
separate
issue.
A
Cool-
and
it
is
already
part
of
the
environment,
config
beta
tracking
issue,
so
it
looks
like
we're
good.
There.
A
F
And
I
today
create
an
another
issue
which
might
also
be
part
of
that
epic,
it's
a
just
a
small
thing
about
renaming
environment
and
config
field
are
actually
dropping
the
dropping
the
the
prefix,
so
it
should
be
on
top
of
the
issue
is
great.
F
G
A
A
So
I
I
I'm
not
signed
in
on
the
browser
that
I
share,
so
I
will
need
to
do
that
on
a
another
browser
and
I
specifically
do
not
keep
myself
signed
in
for
Community
meetings
due
to
sensitive
information
that
can
be
shared
on
the
screen.
A
B
No
I
think
it's
covered.
A
Cool
sounds
good
all
right,
so
then
yeah
so
then.
The
other
thing
I
would
add
here
is
that
developer
experience
improvements.
We
are
making
some
Investments
and
that's
in
1.14
as
well.
We
won't
call
that
complete
at
all,
but
we
are
definitely
continuing
to
invest
in
that
in
1.14
as
well
and
with
a
couple
of
side
chats
from
this
morning.
It
looks
like
you
know
that
we'll
be
proceeding
forward
with
that
and
then
I'll
be
creating
a
special
interest
group
around
that
as
well.
A
So
folks
that
are
interested
in
the
Builder
author.
You
know
developer
experience
for
a
cross
plane.
There
will
be
an
opportunity
to
get
involved
in
a
structured
effort
around
that
area
of
focus
and
so
be
on
the
lookout
for
ways
to
get
involved
with
that
within
the
the
Sig.
Just
like
some
of
the
other
sigs,
we
have
for
composition,
functions,
environment,
configs
and
stuff
like
that,
so
that
will
be
pretty
exciting.
A
I
think
we're
gonna
get
some
good
engagement
with
that
as
well
all
right,
all
right,
all
right,
so
we
yeah,
so
we
are
still
tracking
to
1.14
late
October.
We
are
about
a
little
bit
more
than
a
third
of
the
way
through
the
Milestone
here.
The
goal
still
is
to
have
the
release
in
late
October
so
to
have
it
completed
and
released
and
published
before
kubecon
in
Chicago
happens,
the
Cape
Cod
North
America
happens,
it's
like
November
6th
or
so
so
that
is
still
on
track.
A
I,
don't
see
any
major
things
that
are
calling
that
into
question,
and
that
is
still
the
plan.
Do
folks
have
specific
things
that
they
want
to
see
more
about
or
call
out
for
1.14.
A
All
right,
if
no
other
topic
or
comments
on
1.14,
then
we
can
keep
on
moving
on
here
and
so,
let's
then
move
into
the
provider
releases.
Recent
provider
releases,
so
I
I
didn't
do
a
thorough
dive
on
this
one,
and
so
correct
me
if
I'm
wrong
is
in
terms
of
the
beneficial
providers.
Is
there
any
recent
provider
updates
or
sorry
releases
since
last
community
meeting?
Besides
the
0.40
for
AWS.
E
No,
it's
just
this
one
and
we
released
this
one
as
a
special
out
of
sync
release,
because
there
was
a
few
community
members
who
gave
feedback
and
and
around
the
need
for
inline
policy
on
the
imro
and
we've
implemented
that
and
wanted
to
release
it,
because
the
issue
was
quite
was
open
for
quite
a
while,
and
we
eventually
you
know
settled
on
the
approach
we
were
going
to
take
and
wanted
to
release
it.
So
folks
could
use
it.
A
Awesome
Johnny
I
recall
hearing
that
feedback
from
a
number
of
people
as
well
yeah
using
this
provider
and
making
it
more
challenging
to
adopt
so
I
I.
Think
I
missed
this
one.
That's
really
really
cool
to
see.
So
that
is
a
nice
release
to
have
that
in
there
it's
compatible.
H
Is
the
that
inline
policy?
Is
it
backwards
compatible
with
what
was
there
before
or.
A
Great
okay
and
then
there
is
also
a
a
big
release
for
the
community
AWS
provider
just
last
week
as
well,
that
looks
like
a
whole
bunch
of
Investments
went
into
that
one
I
don't
know
if
anybody
wants
to
speak
to
this
one
as
well.
Otherwise,
the
release
notes
are
linked
right
here
in
the
agenda
doc.
A
Okay,
cool,
then,
let's
keep
on
moving
here,
not
too
much
agenda.
That's
still
left,
but
let's
move
on
to
the
community
topics
here.
So
there
is
a
number
of
pieces
of
content
here
that
are
interesting
and
talking
about
things
going
on
with
cross
plane
and
such
one
of
the
ones.
A
I
thought
was
the
most
interesting
and
it
got
a
number
of
reactions
as
well
in
the
announcements
channel
is
that
there
there
was
some
work
in
in
the
provider
ready
rest
done
recently
to
support
local
stack
and
that
that
developments
environments.
You
know
on
your
on
your
local
laptop
and
not
having
to
use
an
entire
actual
physical
AWS
environment
when
you're
just
doing
development
work,
and
then
the
local
stack
folks
added
the
documentation
specifically
for
using
crossplaying
with
local
Stacks.
A
So
this
is
a
you
know:
official
documentation,
page
about
how
to
set
it
up.
I
think
that
there's
not
anything
out
of
the
ordinary
in
here
really
besides,
you
know
pointing
the
provider
config
I,
guess
at
you
know
local
stack
endpoint
instead,
but
other
than
that
you
know
with
the
fixes
that
went
into
providerate
AWS,
then
this
works
as
you'd
expect.
So
it's
really
cool
to
have
this
as
an
option
for
folks
to
be
able
to
do
development
work
in
a
more
local
environment.
A
A
Let's
see
and
then
some
other
articles
as
well
and
then
cool
so
then
the
biggest
biggest
news
here
is
that
if
I
did
my
math
correctly,
which
I
think
I
did
because
it's
not
too
challenging
that
the
community
event
that
we
are
hosting
is
is
on
September
19th,
which
is
before
the
next
community
meeting.
A
So
before
we
see
each
other
in
a
community
meeting
context,
we
will
see
each
other
I
hope
in
the
the
Community
event
that
we're
hosting
so
the
lineup
and
the
speakers
and
everything
is
available
in
this
blog
post.
It
kind
of
talking
through
everything,
we're
going
to
see
there
some
definitely
exciting
contents
and
some
good
conversation,
some
good
topics
that
will
be
presented
there.
It's
a
two
hour
virtual
event,
so
I
think
it's
a
nice
length
to
get
some
quality
content
and
some
quality
Focus
time.
A
A
I
know
there's
a
fair
amount
of
registration
already,
but
if
you
have
not
yet
registered,
you
know
you
still
have
certainly
have
time
to
do
so
it
is
a
free
events
and
it
is
happening
in
less
than
two
weeks
so
looking
forward
to
seeing
everybody
there
and
thanks
again
for
all
the
folks
that
will
be
speaking
in
walking
us
through
their
topics
of
expertise
in
a
somewhat
similar
vein.
The
do
you
think
this
is
just
next
week.
A
Project
pointed
me
at
this
is
the
container
days
in
Hamburg
is
happening
just
next
week.
So
the
start
of
next
week,
Monday
Tuesday,
Wednesday
I,
think
this
is
so
there
will
be
a
number
of
people
from
the
crosswind
team
in
the
community
and
Founders
as
well.
A
That
will
be
there
locally
in
person
in
Hamburg
and
so
definitely
encourage
folks,
if
you
can
make
it
to
this
event,
if
you're
nearby
and
you
can
stop
by
there,
there
will
be
folks
from
the
community
to
chat
with
and
talk
to
and
all
that
sort
of
stuff
so
definitely
check
it
out
if
you're
able
to
to
make
it
there.
A
All
right
and
then
more
events,
more
events.
It
seems
to
be
the
season
four
events
here,
so
kubecon
North,
America
Chicago,
is
coming
up,
not
super
super
soon
we
do
have
time
to
prep
for
this,
but
essentially
two
months
from
now
is
the
timeline
here,
but
we
have
they,
since
they
published
a
schedule.
We
have
a.
This
is
too
small
I
think
we
have
the
official
schedule
there
that
calls
out
a
the
number
of
talks
that
are
focusing
on
Cross
plane.
So
you
know,
we've
got
the
contrib.
A
The
contribfest,
which
I'm
definitely
excited
about
Nick,
is
going
to
be
helping
out
with
that
and
we're
gonna
do
some
some
cool
stuff,
but
to
get
more
people
involved
in
contributing
to
the
project
and
you
know
doing
code
etc
for
a
cross
plane.
A
We
have
a
typical,
you
know
intro
and
deep
dive
session
that
we'll
be
sharing
with
everybody,
which
it
tends
to
be
very
popular,
so
excited
about
that
one
and
then
Clements
and
I
have
a
talk
that
we're
going
to
be
kind
of
going
through
some
of
the
the
journey
that
that
Clements
made
with
building
out
his
platform
at
consensus.
A
So
that
would
be
definitely
pretty
interesting
and
we'll
try
to
try
to
make
that
pretty
applicable
to
a
wide
audience
there,
and
some
of
the
lessons
learned
from
that
and
thanks
again
come
out
for
driving
that
talk
and
really
excited
to
share
the
stage
with
you,
dude
and
then
they're
also
another
a
couple.
Other
talks
from
the
narmada
folks
looks
like
so
kind
of
more
practical,
and
you
know
some
of
the
lessons
that
they
have
building
their
platforms
too.
A
So
five
different
talks
that
I
see,
at
least
on
the
schedule,
from
a
simple
search.
If
folks
know
of
other
topics,
that
there
are
talks
that
we'll
be
mentioning
crossplaying
feel
free
to
add
them
in
as
well,
but
two
months
until
kubecon,
and
definitely
a
lot
of
work
to
do
before
that,
but
definitely
looking
forward
to
it.
A
All
right
and
then
final
topic
that
we
have
on
the
agenda
already,
is
that
Nick
wanted
to
walk
us
through
some
of
the
recent
design
decisions
and
get
into
some
specifics
around
patch
and
transforms
and
functions
and
how
all
that
will
play
together.
Nick.
Do
you
want
me
to
just
bring
up
some
of
the
stuff
on
my
screen
here
or
do
you
want
to
share
anything
on
your
screen
or
let.
B
Me
send
you
a
link:
okay,
I
wanted
to
do
this.
Jared
said
Nixon.
B
The
is
the
truth.
B
B
After
a
bit
of
discussion
for
a
couple
of
days,
we
made
a
decision
last
week
that,
in
the
beta
implementation
of
composition
functions,
you
will
not
be
able
to
use
contemporary
patch
and
transform
style
composition
together
with
a
pipeline
of
functions,
so
in
the
alpha
design
of
functions
in
the
alpha
implementation
and
until
recently,
in
the
beta
design.
What
we
had
said
is
a
composition.
Today
has
an
array
of
resources.
B
We
call
this
patch
and
transform
because
you
can
hatch
to
and
from
the
resources
and
transform
the
values
that
you're
patching,
and
we
said
that
basically,
people
could,
if
they
want,
keep
that
and
then
add
a
couple
of
functions
on
the
end.
Basically,
that
would
process
the
results,
the
patch
and
transform
process,
while
implementing
the
code.
B
That
does
that
for
the
third
or
fourth
time
I
was
feeling
like
it
was
very
complicated,
and
there
was
a
lot
of
things
that
you
have
to
think
about
that
are
potentially
going
to
be
surprising
for
people
who
use
this
functionality
and
that
also
make
just
make
the
code
complex,
which
means
it's
more
likely
to
be
buggy.
Just
one
example
of
that
was:
what
happens
if
something
fails
during
the
patch
and
transform
pipeline?
What
happens
if
a
patch
can't
be
processed
or
they
would
have
a
required
patch
can't
be
processed?
B
Do
you
stop
the
whole
thing?
Do
you
stop
the
whole
composition
process?
Do
you
send
them
to
the
functions?
Do
you
send
only
the
patches
that
only
the
resources
that
worked
to
the
functions
it
just
gets
pretty
messy
to
work
around
so
then
I
started
thinking.
Admittedly,
my
my
impetus
was
was
thinking
of
that
from
how
complicated
it
is
this
controller,
but
then
I
realized
there
was
a
number
of
other
benefits.
I
started
thinking
about
what,
if
we
just
made
it
mutually
exclusive.
B
What
if
you
had
to
pick
basically
use
composition,
functions,
the
pipeline
of
functions
or
you
use
Patcher,
transform
resources
in
the
link
that
I
just
sent
to
Jared
the
function
patch
and
transform
repo
there's
a
section
in
the
readme
called
okay.
B
But
why-
and
it
goes
in
some
detail
as
to
what
the
benefits
of
making
these
mutually
exclusive
are,
and
specifically,
there
is
an
assumption
that
if
we
make
Native
patch
and
transform
support
and
composition
functions
mutually
exclusive,
you
will
still
be
able
to
do
patch
and
transform,
but
it
will
be
implemented
as
a
function.
So
patch
and
transform
becomes
one
of
the
functions
that
you
can
optionally
use,
rather
than
being
a
special
thing
that
is
separate
from
the
functions
pipeline
that
that
is
a
different
type
of
composition.
B
So
it's
not
Illustrated
in
this
example
here,
but
in
the
latest
thinking
I'm,
proposing
that
the
composition
type
have
a
spec
dot
mode
field
mode
with
default
to
resources
which
basically
says
just
work
the
same
as
it
does
today.
Just
use
patch
and
transform
no
functions
and
you
could
optionally
switch
mode
or
create
a
composition
of
mode
Pipeline,
and
that
would
run
a
pipeline
of
composition
functions
instead.
B
So
one
of
the
reasons
that
this
is
beneficial
is
that
it
allows
you
to
still
do
a
patch
and
transform
if
you
well.
One
reason
is:
if
you
don't
like
patent
transform,
you
just
completely
get
rid
of
it
and
you
can
do
something
else:
use
a
go
templates
function
or
write
your
own
code
or
whatever,
and
we've
heard
from
a
number
of
people
that
that's
exactly
what
they
plan
to
do.
B
Another
option
is:
if
you
are
using
passion
transform,
it
doesn't
have
to
be
the
first
step
in
the
pipeline
anymore.
It
doesn't
have
to
be
the
patch
and
transform
happens
and
then
other
functions
happen.
You
could
run
a
couple
of
functions
and
then
run
patch
and
transform
and
then
run
a
couple
of
other
functions
if
you
want
to
well.
This
example
that
we're
looking
at
at
the
moment
sketches
out
is
a
hypothetical
composition
that
is
actually
going
to
render
some
go
templates.
B
So
helm-like
basically
write
some,
you
know:
go
mustache
template
style
code,
it'll,
output,
some
resources
and
then
they
get
sent
to
the
patch
and
transform
pipeline
you'll
notice
that
patch
and
transform
here
doesn't
actually
have
a
base
resource.
It's
just
patches
and
transforms
so
what's
happening
here
is
the
base
resource
is
actually
being
produced
by
the
previous
function?
It's
using
a
Helm
template
to
render
or
using
go
templates.
B
I
should
say
Helm
glyco
templates,
to
render
out
some
resources
and
then
you
can
copy-
and
you
know,
use
use
typical
patch
and
transform
syntax
to
decorate
those
overlay
them
with
a
bit
of
data.
So
that's
one
benefit.
Basically,
you
could
move
patch
and
transform
to
anywhere
within
a
pipeline
rather
than
always
having
to
have
it
be
at
the
start.
B
The
next
benefit
is
that
if
patch
and
transform
becomes
a
function,
then
passion
transform
is
development
is
decoupled
from
composition,
core
it's
cross-plane
core.
So
if
we
can
get
most
people
to
sort
of
migrate
to
using
this
function,
instead
of
using
the
native
patch
and
transform
support,
then
one
of
the
benefits
is
if,
if
there's
a
new
feature
to
be
added
to
Passion,
transform,
let's
say
a
new
type
of
patch,
a
new
type
of
transform
or
whatever
that
doesn't
necessarily
have
to
be
released.
You
know
with
crossplay,
1.14
or
crosstalk
1.15.
B
We
would
I
imagine
end
up
having
a
different
set
of
maintainers
or
a
you
know,
not
exactly
the
same
set
of
maintainers
as
core
cross
played
for
the
for
the
Patcher
transform
function,
and
they
could
choose
to
release
it
more
frequently
if
they
wanted
to,
they
could
choose
to
say
Yep.
This
is
a
really
important
new
feature
that
we've
added
we're
going
to
just
do
a
release
next
week,
rather
than
waiting
up
to
three
months
for
a
crossline
release.
B
It
also
potentially
allows
you
to
let's
say:
let's
say
you
have
a
feature
that
you
want.
Let's
say
you
have
a
new
type
of
patch,
so
you
really
really
want
to
add
in
your
organization.
Just
absolutely
has
to
have
this
patch
and
you're
completely
sold
on
it,
but
the
maintainers
of
the
function
say
no.
We
will
we'll
die
on
this
hill.
We're
never
going
to
accept
that
patch.
We
don't
think
it's
a
good
idea
for
for
our
users.
B
It
now
becomes
a
lot
easier
for
you
to
just
Fork
the
function
and
be
like
we're
going
to
run
our
version
of
the
function
that
has
this
patch
that
we
want
in
it,
because
you're
not
maintaining
a
fork
of
all
of
cross
play
and
you're
just
walking
one
function
becomes.
You
know
it's
not
ideal,
but
it
becomes
more
like
the
choice
of
forking
a
provider
rather
than
forking
all
of
cross-plane.
Let's
say
the
other
thing
that
I
think
is
really
neat.
Is
it
makes
patch
and
transform
more
portable?
B
What
I
mean
by
that
is,
if
all
of
the
composition,
Logics,
that
your
composition
is
using,
is
in
versioned
functions,
and
this
makes
experiences.
This
is
just
a
sketch
here,
but
this
makes
experiences
like
this.
Xp
composition
render
much
more
feasible
right.
B
You
can
have
a
client-side
tool
that
does
not
need
to
vendor
or
otherwise
share
too
much
code
with
crossplay,
and
it
needs
to
share
very
little
code
with
crossplaying,
because
all
of
the
code
that
is
used
to
do
composition
is
inside
artifacts
it's
inside
the
function,
so
you
can
imagine
a
CLI
like
this.
That
looks
at
a
composition,
takes
the
XR,
as
input
pulls
down
the
functions
that
that
composition
uses
and
then
runs
them
and
passes
the
XR
through
them,
basically
to
produce
rendered
output.
B
B
You
would
need
to
basically
have
a
library
of
patch
and
transform
code
that
was
shared
between
the
client
and
the
server
and
then,
whenever
you
were
doing
this
rendering
you
would
have
to
make
sure
that
you
were
running
the
same
version.
Basically,
on
your
production
across
playing
as
you
were
in
your
CLI,
otherwise
they
could
potentially
produce
different
results.
B
What
would
this
do
in
1.14,
whereas
if
you
have
version
composition,
functions,
including
patch
and
transform,
you
can
just
say:
what's
this
going
to
do,
using
these
composition
functions
and
the
as
is
going
to
be
pretty
much
the
same,
regardless
of
what
version
you're
running
so
a
lot
of
these
a
lot
of
these
added
in?
Finally,
it
makes
the
implementation
simpler
of
composition
in
the
in
the
crossbank
code
base.
So
a
lot
of
these
are
kind
of
benefits.
B
Of
maybe
more
of
moving
patch
and
transform
into
a
function
is
a
different
way
to
think
about
it.
Rather
than
saying,
it's
mutually
exclusive,
with
the
function
pipeline,
but
they're
sort
of
two
sides
of
the
same
coin,
to
be
clear:
removing
resources,
support,
removing
what
I
would
call
now
native
patch
and
Trends,
oh
by
the
way
this
function's
already
built
as
well
I
built
this
over
this
weekend.
So
it's
it's
probably
got
like
you
know,
there's
a
few
known
issues
and
a
few
more
things
to
do,
but
it
is.
B
So
it
would
be
a
breaking
change
to
remove
native
patch
and
transform
support
from
crossbones.
So
that's
not
something
we
can
feasibly
do
what
the
composition
type
is
at
V1,
but
what
I
would
imagine
looking
forward?
You
know,
let's
say
six
months
from
now
or
more.
Let's
say
we
get
composition,
functions
to
the
point
where
we
consider
the
feature
GA,
it's
it's
V1,
it's
not
a
beta
feature
anymore.
We
have
good,
tooling,
around
composition,
functions
and
generally
there's
good
feedback
and
there's
no
major
bugs
with
it,
and
people
are
using
it
at
that
point.
B
What
I
would
recommend
is
that
we
Mark
the
resources
field
in
the
composition
and
the
resources
mode
of
composition
in
general
native
pattern.
Transform
at
that
point,
I
would
recommend
we
mark
it
as
deprecated
and
have
it's
say
basically,
hey.
We
recommend
you
use
motions.
Instead
of
this,
you
would
still
be
able
to
use
it.
We
wouldn't
deprecate,
it
again
doesn't
mean
we
have
a
plan
to
remove
it.
B
It
just
means
we've
identified
something
better,
then
we're
going
to
point
you
in
that
direction
and
we
would
probably
also
freeze
the
API
at
that
point.
So
we
would
not
accept
new
features
for
Native
patch
and
transform
only
bug
fixes
we
wouldn't
accept
any
patches
and
all
that
kind
of
thing
there.
But
you
know
that's,
that's
again.
That's
let's
say
six
plus
months
from
now.
That's
that's
functions.
Get
to
GA
functions
are
working
well,
a
lot
of
people
have
migrated
to
functions.
B
Then
can
we
start
setting
a
path
towards
deprecating
that
old
API-
and
you
know,
maybe
18
months
from
now
in
V2
of
cross,
plain
or
whatever?
Not
that
that
is
a
you
know.
Whenever
V2
happens,
I'll
be
two
of
the
Cross
composition.
Api
happens,
I
would
recommend.
We
go
to
a
pure
functions.
Implementation.
B
So
that's
it
any
I
know
many
of
the
folks
who've
been
paying
attention
to.
This
are
already
aware
of
this
any
questions
or
concerns
about
this.
G
Yeah
I,
like
I,
really
like
the
design
super
cool
ideas,
especially
like
a
different
life
cycle,
detached
from
a
corpus
plane.
My
usual
question:
how
vov
migrate
existing
compositions,
like
resuming
customers
so
cross
plain
users
say
you:
have
existing
passion
transform
in
a
code
base
right?
So
if
you
is
there
any
form
of
tooling
to
convert
to
function,
punch
in
transform.
B
I
think
it
would
be
trivial
to
write
tooling.
Will
the
cross
play
and
core
team
write?
Tooling?
Probably
not.
This
is
an
alpha
feature
that
we're
making
a
breaking
change
for.
So
it's
it's.
You
know
typical
Alpha
contract
I
would
say
also.
B
So
so,
specifically,
who
this
is
going
to
break
people
who
today
have
turned
on
the
alpha
feature
flag
and
are
using
functions
together
with
patch
and
transform
anyone
who's
not
using
functions
today?
This
will
be
a
no-op
for
because
they
are
just
using
the
resources
array.
The
resources
already
doesn't
change.
B
B
B
G
Yeah
that
doesn't
make
sense.
My
question
was
about,
like
you
know,
long-term
scenario
when
it
gets
the
blast
like
in
a.
G
Six
months
you
mentioned,
and
everything
is
stable
and
people
already
like
bought
into
the
idea
of
a
function
based
pattern
transform.
So
if
I
understand
correctly
currently,
even
without
tooling,
it
will
require,
like
a
simple
kind
of
copy,
yaml
copy
paste
right
into
slightly
different,
like
a
patch
and
transform
chunk
of
the
definition
right
and
it's
potentially
easily
automated
yeah.
B
Yeah
exactly
yeah
and
like
I
say
even
when
we
got
to
GA
like
if,
let's
let's
say
that
cross
play
in
one
point,
one
five
we
make
functions
GA
in
injecting
right,
I,
don't
know
if
that
will
be
the
case
or
not.
But
let's
say
that
we
do
that.
B
Even
at
that
point,
if
if
people
are
still
just
using
the
resources
right,
that
would
keep
working
like
it's
again
that,
like
patch,
if
you're,
using
a
composition
that
works
today
and
you're
not
using
functions.
That
composition
is
going
to
keep
working
until
like
V2
of
the
composition
type
which
which
we
have
no
plan
to
actually
make
so
for
a
long
time.
B
So,
in
order
to
start
using
functions
in
general,
because
you
know
you
have
to
start
specifying
a
pipeline
of
functions
and
if
you
did
just
want
to
move
to
kind
of
what
we
recommend
here,
we
notice
we're
seeing
this
deprecation
warning
now,
because
we've
added
that
and
we
want
to
move
to
the
function
yeah
it
would.
It
would
kind
of
Jared
if
you
can
just
see
the
everything
from
pipeline
step
to
the
resources
in
there.
B
If
you
could
just
sort
of
highlight
that
that
would
be
handy
if
you
get
what
I'm
saying
so
yeah
from
knock
knock
too
high
from
from
kind
to
resources
to
step
sorry
for
Backseat
drivers
that
doesn't
matter,
okay,
you
can
you
can
see
where
it
says
where
it
says:
resources,
colon
and
then
there's
an
array
from
up
to
where
it
says
pipeline
that
that
is
kind
of
what
you
need
to
add.
B
Yes,
you
did
I
will
say
there
are
some
caveats
at
the
moment,
so
the
things
that
this
function
doesn't
support
right
now
is
merged
policies
and
environment
configs.
It's
not
that
I
don't
want
to
support.
A
Cool,
yes,
thanks
for
sharing
this
nick
and
I
think
that
the
the
world
that
we'll
be
living
in
with
you
know,
functions
more
mature
and
you
know
the
ability
to
do
passion,
transform
logic
still
this
in
similar
ways
as
before,
you
know
but
have
everything
running
as
functions.
This
definitely
opens
up
a
lot
of
possibilities
and
a
lot
of
flexibility
too.
So
I'm
kind
of
excited
about
this
myself.
B
Yeah
something
that
Bob
had
suggested
as
well
was
someone
else.
I
think
also
had
thinking
along
the
same
lines
is
hypothetically.
You
could
imagine
maintaining
compatibility
with
the
way
the
compositions
work
today
by
implementing
the
the
actual
resources
array
to
like
make
that
special
and
have
that
actually
be
calling
a
function
just
as
fixed
in
the
cross-plane
code,
like
we
always
installed
a
function
that
does
the
backwards
compatible
old
school
native
patch
and
transform,
and
so
everything
actually
just
becomes
a
function.
B
B
Are
ready
to
be
specified
in
order
to
to
make
that
work
so
not
sure
how
possible
that
will
be,
but
so
there's
something
to
something
to
investigate
all.
A
Right
so
there
were
no
other
agenda
items
that
were
added
to
the
list
here.
So
I
will
open
the
floor
for
a
last
call
for
agenda
topics.
D
I,
don't
have
an
agenda
topic,
but
I
do
have
a
question
so
I'm,
just
quite
new
to
cross-plane
and
I'm
playing
around
with
it
to
check
it
out
on
gcp
provider
and
I.
Had
a
quick
question,
so
I
managed
to
create
projects
Etc,
but
I
noticed
that
I've
not
been
able
to
find
any
documentation
of
enabling
Services
something
similar
to
how
terraform
does
it.
A
So
for
I
mean,
are
you
asking
about
like
documentation
about
all
the
types
contained
in
the
GC
gcp
provider
and
like
what
all
their
fields
are
and
how
to
use
them
or
no.
D
Whether
it's
possible
to
enable
Services
such
as
compute
Etc,
so
I've
enabled
the
provider
and
everything
is
fine,
but
I
have
run
into
this
issue
where
the
resource
tells
me.
Can
you
go
and
manually
enable
the
API
within
your
gcp
project?
Oh,
so
that's
the
part
where
I'm
not
sure
is
that
automated
or
is
it
still
a
manual
process.
A
That's
a
really
good
question,
because
every
time
I've
done
it
I've
done
it
like
through
the
gcp
console,
so
yeah
I
would
open
the
floor
to
that.
Maybe
Yuri
you
might.
You
might
be
more
familiar
with
that?
If
you
know
you,
if
there
is
an
automation
or
a
type
that
represents
enabled
services
within
gcp
like
the
gcp
API
Services,
you
enable
within
a
project.
D
Yeah
and
just
to
add
to
that
I
I
did
check
out
something
called
cnrm
system,
which
is
Google's
version
or
something
similar
of
what
cross
plane
does,
but
very
specific
to
Google
itself.
Where
you
can
create
a
new
project
you
can
enable
apis.
You
can
do
all
those
things
so
I
have
added
all
the
permissions
that
are
required
to
perform
it
using
workload
identities,
but
just
not
sure
whether
that's
possible.
G
Yeah
I'm
not
sure
I'm
I've
had
something
similar
in
Azure
like
it
has
a
dedicated
object
for
IP
enablement,
so
it's
possible,
but
we
can
double
check
the
gcp
one.
D
That'd
be
awesome
and
if
it's
not
there,
I'm
happy
to
try
and
contribute
to
work
towards
trying
to
enable
it
and
write
code
very
required.
A
Yeah
and
so
I
mean
I
just
added
to
the
edge
of
the
dark.
A
type
I
found
from
searching
real
quick
is
that
there
is
a
like
in
the
gcp
provider.
There
is
support
for
projects
and
project
Services
Etc,
and
so
it
looks
like
this
type
here
is,
is
the
one
you
could
use
to
programmatically
turn
on
Services,
and
it
looks
like
there's
an
example
for
it
as
well
too.
So.
D
So
that's
probably
one
thing
which
I
found
that
finding
application
is
not
very
straightforward
across
plane,
so
Google
doesn't
necessarily
take
you
to
the
right
locations
or
even
if
I
search
within
cross
planes
our
website
itself.
It
doesn't
necessarily
take
me
to
the
right
location.
A
Yeah
and
I
think
that
there's
there's
going
to
be
a
bit
of
a
distinction
here
between
like
core
cross
plain,
and
you
know
like
the
functionality
with
like
the
general
functionality
and
the
cross-plane
docs
there
and
then
everything
that
the
entire
provider
ecosystem
is.
You
know
separate
from
that,
and
you
know
like
got
it:
it's
not
going
to
be
found
in
the
core
crossbandox.
So
there
it
is.
So
you
can
see
here
like
this
Marketplace
startup
on
that
I
O.
A
That
is
a
really
good
spot
that
where
providers
are
published
to
where
documentation
is
displayed
and
all
that
and
so
searching.
If
you
try
searching
in
there,
then
for
provider
specific
stuff,
then
you
may
have
better
luck,
finding
it
starting
there.
It's
a
starting
point.
D
Sounds
good
normally
I
was
looking
around
there,
but
I
did
not
search
in
there
for
enabling
services.
So
thanks
for.
A
That
yeah
and
if
there's
any
feedback,
you
know
it's
like
we're,
always
happy
to
hear
about.
Hey
I
was
looking
for
this
and
couldn't
find
it,
and
then
you
know
that
can
inform
us
to
you
know
better
to
help
with
this
discoverability
of
of
resources,
like
that's,
definitely
a
focus
area
right
now.
So
that's
good
feedback
to
have
and
will
always
be
useful
to
us.
D
A
Awesome,
dude,
sweet,
okay,
so
yeah
we'll
leave
this
in
the
agenda
doc
here
so
it's
available
for
others
as
well.
And
then,
if
there
are
no
other
agenda
items,
then
we
can
go
ahead
and
adjourn
for
the
week.
A
All
right
well
good
to
see
everybody
thanks
for
stopping
by
good
to
see
everyone
here
together,
and
we
will
hopefully
see
you
all
then,
the
next
time
at
the
community
Day
event
on
September
19th.