►
From YouTube: 2023-09-21 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
recording
has
started,
and
this
is
the
September
21st
2023
cross
plain
community
meeting.
So,
as
always
in
the
chat,
I
will
drop
a
in
the
zoom
chat.
That
is
I
will
drop
a
direct
link
to
the
agenda
document.
So
you
folks
can
click
on
that
feel
free
to
add
yourself
as
an
attendee.
If
you
want
to,
and
also
as
always
the
agenda
document
is
open
for
anybody
to
make
contributions
or
discussion
topics
that
they're
interested
in
so
feel
free
to
add
suggestions
and
we'll
merge
them
on
into
the
document.
A
So
not
too
much
in
terms
of
recent
releases,
there
was
a
the
universe,
the
upbounds
universal
CrossFit,
there's
a
that
distribution
of
Crossway
did
have
a
release
in
the
last
couple
weeks
and
you
can
click
into
the
release.
Notes
there
if
you're
curious
about
hopes
included
in
there,
but
mostly
all
eyes.
Right
now
are
on
the
upcoming
1.14
release.
We
are
just
about
a
month
away
now
it's
scheduled
for
late
October,
so
a
little
bit
more
than
a
month,
but
that's
about
the
approximate
timeline
there.
A
A
As
far
as
I
know,
everything
is
on
track
to
be
completed
for
1.14
you'll
notice
that
we
have
already
closed
out.
One
of
the
high
level
epics
for
the
1.14
Milestone
Hassan
was
is
kind
enough.
I
think
it
was
actually
two
meetings
ago
to
show
us
a
demo
of
the
usage
type,
the
new
usage
API.
That
is
helpful
for
enforcing
order
deletion
of
your
resources,
and
that
is
in
that
has
been
merged
into
the
main
branch
of
cross
plain,
and
it
will
definitely
be
included
in
1.14
everything
else.
A
There
is
I
think
that
the
observable
resources
in
this
in
the
composition,
validation,
stuff,
I,
think
that's
not
much
left
to
go
on
that,
and
so
the
two
bigger
things
that
are
still
left
and
still
have
ongoing
work
are
the
composition,
functions,
work
to
get
those
matured
and
into
experience
around
those
and
moving
those
to
Beta,
which
will
go
into
a
little
bit
more
in
depth
later
on
in
the
meeting
here
today
and
then
a
lot
of
developer
experience,
improvements
that
we're
investing
in
that
we'll
talk
about
later
in
the
agenda
as
well,
along
with
the
full
context
of
you,
know,
expanding
the
scope
of
the
charter
of
Crossman
that
we
announced
yesterday.
A
So
that's
the
high
level
for
1.14
I
will
bring
up
the
release
board
for
1.14
as
well.
I,
don't
think
it's
entirely
up
to
date,
there's
a
few
things,
probably
that
are
maybe
a
little
bit
stale
or
need
to
be
updated
here.
But
the
key
key
takeaway
here
is
that
everything
we've
got
planned
in
the
roadmap
for
1.14
is
on
track
and
I.
Don't
see
major
major
obstacles
there
and
then
there's
you
know
another
another
number
of
other
things
in
flights
as
well
on
the
1.14
board.
A
And
Hassan
I
did
I
did,
did
I
represent
the
order
deletion
stuff
correctly.
When
I
was
speaking
about
it.
Anything
you
would
need
to
correct
there.
A
All
right
awesome
is
anyone,
let's
see
so
Esky
is
here
and
then
no
Felipe
and
no
nick,
as
you
is
there
anything
that
you
wanted
to
add
for
the
composition,
functions,
efforts.
C
D
ready
to
be
used
for
creating
new
functions,
we
have
much
deployment
part
already.
There
is
one
work
on
going
on
flip
side,
which
is
actually
changing
the
newly
introduced
secrets
with
certificates,
so
that
part
is
ongoing.
I
am
working
on
a
new
composition
function
which
will
allow
us
to
use,
go
templates
and,
as
far
as
I
know,
Nick
is
working
on
a
go
SDK
for
writing
functions,
so
I
think
everything
is
on
track
and
we
will
be
ready
for
round
14.
A
Nice
Esky
in
that
particular
part
you
were
working
on
there.
You
know
a
reusable
or
general
function
that
allows
you
to
essentially
to
write
composition.
Logic
in
you
know,
go
template
style,
Helm,
template.
A
A
All
right,
so
that's
Road,
Mappy,
stuff
and
1.14
reminder
that
late
October
is
what
we're
targeting
there.
Typically,
we
do
the
the
fourth
Tuesday
in
the
month
there
so
I
think
I'm
not
looking
at
a
calendar
but
I
think
that's
around
the
23rd
or
so
that
will
be
the
approximate
time
that
we're
shooting
for,
but
with
some
definitely
way
to
push
it
back
a
little
bit
as
needed
for
landing
and
Landing
all
the
features
and
getting
everything
well
tested
and
feeling
good
about
everything.
A
The
the
intent
certainly
is
to
get
the
release
out
before
Cape
Cod
North
America
in
Chicago.
That
is
still
very
much
a
strong
desire
for
everyone
around
here
all
right.
If
there
are
no
other
comments
about
1.14
of
the
progress
there
from
the
group,
then
we
can
move
along
to
the
provider
section,
not
a
lot
to
talk
about
there.
I
think
that
they
on
Tuesday,
I,
think
so
five
days
or
so
from
now
is
when
we're
expecting
another
drop
of
provide
provider
releases.
A
A
Are
you
on
the
call
here
today
it
doesn't
look
like
it
looks
like
we're
missing
a
couple
folks
I
wanted
to
get
some
updates
from,
but
yeah
so
that
there
is
a
new
provider,
key
book
that
is
available
and
in
the
marketplace
as
well.
There
Tobias
it
looks
like
you
have
something
to
share
for
writers
as
well.
Do
you
want
to
go
ahead
and
share
right
now.
E
Sure
so
I
have
a
small
question,
so
there
is
a
provided
GitHub
already
and
the
thing
is,
it
seems
to
be
abandoned
and
because
we're
currently
using
a
similar
logic,
built
on
top
of
another
framework
and
I
wanted
to
replace
it
with
such
logic.
I
just
started.
E
Writing
and
now
I
have
a
provider
GitHub,
which
has
pretty
much
the
basic
features
and
I
wanted
to
ask
like
how
how
you
handle
such
stuff,
like
I,
mean
I,
have
to
say
it's:
it's
not
my
native
language,
so
to
say,
I'm
coming
actually
from
python,
so
but
I
was
contributing
in
the
provider
AWS,
so
I
thought
I
started
from
scratch,
and
now
it
looks
like
it's
almost
ready
for
some
kind
of
an
alpha
release
and
the
old
work.
A
Not
able
to
hear
you
right
now,
it's
biased,
even
though
I
don't
see
you
that
you're
muted.
So
hopefully
you
can
at
least
hear
the
response
here
and
if
not,
we
can
you
could.
Oh
I
think
it's
about
us
got
kicked
out
as
well,
and
it
looks
like
it's
joining
back
in
again
now
now
let
me
give
to
bias
like
five
seconds
to
maybe
come
back
on
with
audio
before
we
move
on.
A
All
right
so,
like
I'll,
give
a
response
here.
No
and
then
you
know,
tobiasive
is
not
able
to
listen
to
it.
Now.
You
can
definitely
check
out
the
recording
and
that'll
be
that'll,
be
captured
there
as
well,
so
so
for
for
the
GitHub
provider.
There
I
I,
like
the
effort
first
off
about
I,
just
started
writing
and
ended
up
with
a
provider.
That's
that's
a
happy
place
to
end
up
with.
So
that's
cool
man
and
congratulations
on
that
effort
there.
A
So
in
general,
in
general,
it's
good
in
the
community
to
have
convergence
upon
a
single
provider,
so
that
there's
you
know
you
don't
have
multiple
providers
and
there's
confusion
about
it.
We've
seen
that
before
and
there's
no
doubt
about
it
and
it's
it's
good
to
end
up
with
convergence.
A
So
one
thing
Tobias
that
we
might
want
to
do
there
is
let's
try
to
get
a
conversation
with
with
the
current
maintainers
of
the
current
provider
GitHub
and
let's,
let's
try
to
approach
it
from
that
angle
of
you
have
some
new
developments
that
you
either
a
want
to.
You
know
contribute
as
a
whole
or
maybe
consider
merging
with
the
existing
provider
or
becoming
a
maintainer
on
the
existing
provider,
something
along
those
lines.
A
But
let's
sync
up
with
the
current
maintainer
team
for
better
GitHub
and
see
you
know,
get
a
baseline
of
what
that
team
is
planning
to
do
and
what
we
can
do
with.
What
with
your
efforts
that
you've
made
too,
does
that
sound,
reasonable.
E
Yeah
so
give
me
some
history
actually
coming
from
exactly
that
route.
So
I
was
checking
and
the
last
commit
is
actually
two
years
ago
and
I
tried
to
text
the
maintainer
like
and
he
didn't
respond.
I
tried
to
ask
Christopher
because
I
regularly
in
contact
with
him,
but
he
seemed
to
be
very
busy
and
then
I
posted
in
a
channel,
and
they
said
like
okay
best
is
to
go
just
to
the
the
community
meeting.
So.
D
A
Yeah
yeah
cool,
okay,
thanks
for
that
context,
definitely
and
then
yeah
and
then
I
I
I'm
happy
to
follow
up
with
with
those
folks
as
well
and
see
if
we
can
get
a
bit
of
a
bit
of
response
like
when
in
general,
if
a
maintainer,
sorry,
if
a
provider
is
no
longer
maintained,
it
can
be
archived
or
there
can
be
new
maintainers
joining
in
there.
So
I
think.
A
That's
that's
a
that's
a
route
to
explore
to
see
you
know
if
the
existing
maintainer
team,
you
know
wants
to
have
your
contribution
come
in
and
essentially
you
you
become
a
maintainer
on
it,
but
we
will
follow
up
with
the
maintainer
team
to
get
a
confirmation
about
that
and
just
so
we're
all
on
the
same
page
on
what
a
concrete
steps
to
take.
But
that's
that's
the
approach
that
we'll
take
care.
E
Yeah
would
be
really
great:
I
bought
I
built
a
hundred
percent
on
top
of
what
was
already
there.
I
just
used
a
new
template.
So
let's,
let's
see
how
this
goes.
D
E
I'm
gonna
send
you
the
link
and
thanks
for
your
ears,
yeah.
A
B
Yeah
I'll
just
add,
like
just
checking
the
repository,
and
it
looks
like
there's
no
releases
so
like
it's
not
available.
E
A
Yeah
that
sounds
great
to
us.
Thanks
for
your
Your
Enthusiasm
and
your
efforts
yeah,
it
will
follow.
E
A
A
D
A
Man,
okay,
so
then
we'll
move
on
to
the
community
topics
section
here.
So
there
is
a
number
of
pieces
of
content
from
around
the
ecosystem
in
the
industry
that
are
mentioning
cross
planes.
So
there's
a
number
of
links
that
you
can
click
into
here
and
check
those
out
on
your
own
time.
We
will
go
into
more
specific
details
about
Clement
mentioned
this
in
the
chat
as
well
about
donating
about
donating
the
jet
framework
and
providers
to
the
cross-playing
community
too.
A
So
we'll
go
into
more
details
on
that
in
just
a
little
bit
and
then
I
did
want
to
call
attention
to
the
community
newsletter.
Here
we
have
started
a
newsletter
for
for
this,
this
audience
here
for
the
folks
that
are
adopters
and
users
and
contributors
to
crossblane.
A
We
want
to
do
that
on
a
regular
Cadence
to
give
another
another
outlet
for
folks
to
get
updates
on
the
community
if
they're
not
super
involved
in
slack
or
you
know,
Twitter
or
whatever
just
another
option
to
stay
in
touch
with
the
project,
and
so,
if
folks
check
on
that
blog
post
there,
it's
kind
of
announcing
the
community
newsletter
and
what
its
intent
is
and
then
there's
a
way
to
to
opt
in
And,
subscribe
to
it
as
well.
If
you're
interested
in
that,
so
click
go
through
that
and
check
that
out.
A
So
big
news
from
this
week
definitely
was
the
Community
Day
event
that
was
on
Tuesday
morning.
So
just
a
couple
days
ago
and
I
thought
it
was
awesome.
It
was
a
really
cool
event.
There
was
a
lot
of
participation
a
lot
of
it.
You
know,
folks
that
got
registered
very
good
content
as
well,
really
loved
all
the
talks,
so
that
was
super
fun.
The
plan
here
is
definitely
to
we're
currently
processing
the
recordings.
A
You
know
segmenting
them
up
into
specific
talks
so
that
we
can
upload
talk
by
talk
and
they're
used
more
easily
indexable
discoverable.
A
That
way,
you
know
adding
like
speaker,
cards
and
stuff
like
that,
so
they're
being
processed
right
now
and
as
soon
as
those
are
available,
we
both
be
posting
them
on
YouTube,
so
that
they're
accessible
for
everybody
to
check
out
who
wasn't
available
to
make
the
make
the
event
so
be
on
the
lookout
for
that
and
then
I
wanted
to
specifically
call
out
Kelly
for
her
efforts
here
on
organizing
and
driving
the
event
and
getting
everything
put
together.
A
She
put
a
lot
of
work
and
a
lot
of
a
lot
of
effort
into
it
and
I
think
it
turned
out
really
great.
So
thank
you
very
much
Kelly
for
your
efforts
on
that
and
your
success
as
well.
A
There
is
everyone
who
is
registered
for
the
event
I
believe
you
got
an
automated
email
after
it
was
over
with
a
feedback
form
so
feel
free
to
add
your
feedback
there
and-
and
let
us
know
you
know
what
you
liked,
what
you
didn't
like,
what
could
be
improved
all
that
sort
of
stuff
there's
a
direct
link
to
it
as
well.
A
If
you
didn't
just
if
you
didn't
get
the
email
about
it,
so
feel
free
to
pick
through
on
that,
and
then
I
wanted
to
open
the
floor
up
for
anybody
in
this
group
here.
If
there
was
any
thoughts
or
experiences
or
highlights
or
anything
that
you
wanted
to
share
about
the
Community
Day
event
that
was
earlier
this
week.
A
Oh
feel
free
to
put
your
feedback
into
the
forum
if
you
want
to
make
that
in
a
in
a
more
direct
route
for
for
the
event
planners
there
and
we'll
be
happy
to
you
know,
look
through
all
that
and
try
to
make
the
next
event
even
better
than
this
one
was
all
right:
nothing
new
on
kubecon,
Chicago
stuff.
This
is
just
an
ongoing
link
here.
A
So
folks
can
see
all
the
cross-plane
related
talks
and
get
those
on
their
schedule
if
they're
interested
in
those
we're
we're
involved,
I'm
involved
in
a
number
of
talks
and
we're
making
progress
on
all
of
those
to
get
some
good
sessions
together
and
I'm.
Looking
forward
to
getting
to
Chicago
and
hanging
out
with
everybody.
A
All
right,
let
me
do
another
check
here
to
see
if
Nick
is
online,
he
is
not
so
I
will
take
this
one
for
him.
Then.
A
All
right
so
Nick
opened
up
this
discussion
just
a
few
days
ago,
and
so
the
effort
on
composition,
functions
and
maturing
them
and
improving
the
experience
as
we
go
towards
beta
here
for
1.14
is
to
a
point
now,
where
we're
ready
for
folks
to
test
it
and
provide
feedback.
So
I
think
this
is
a
really
cool
opportunity
to
take
the
resources
and
the
you
know,
the
experiences
that
we've
built
so
far,
and
you
know
for
folks
to
go
ahead
and
already
write
functions
with
this
new
experience.
A
I
think
it's
I
don't
want
to
see
this
too
much,
but
I
believe
that
this
is
a
much
easier
experience
here
and
a
much
improved
and
streamlined
way
to
go
about
writing.
Custom
Logic
for
composition,
functions.
There's
a
couple
of
different
examples
you
could
check
out
and
Nick
is
mentioning
to
you
know.
A
The
best
place
to
get
started
is
to
check
out
the
readme
of
the
template,
repo
that
you
can
use
as
a
starting
point
that
has
all
of
the
you
know:
boilerplate
code
and
dependencies
and
build
structure
and
all
that
sort
of
stuff,
and
you
can
just
focus
on
writing
only
your
custom
custom
logic
within
there.
A
So
anybody
who
engages
in
this
effort
here
go
ahead
and
we'd
love
to
for
you
to
share
your
efforts
in
this
discussion
here,
looks
like
there's
been
a
bit
of
chatter
around
it
already
and
you
know,
get
your
feedback
early
feedback.
So
we
still
have
plenty
of
time
to
make.
You
know,
updates
or
Corrections
for
1.14
and
I'm
excited
to
see
what
folks
are
coming
up
with
here
too
so
check
out
this
discussion
here
and
if
you've
got
time,
definitely
try
to
try
your
hand
at
writing.
A
composition
function.
B
Jared,
actually,
the
that
second
link
is
also
shared
in
the
last
comment
of
the
previous
discussion.
So.
B
The
contact
stash
and
mention
what's.
B
A
B
Nick
you
just
shared
it
in
this,
like
cross-plane
slack
and
it's
it
looks
like
it's
a
like
small
little
Tool
called
X
render
and
it's
acts
like
a
health
template
render.
So
you
can
use
it
to
locally
render
any
composite
or
composition
and
like
this
will
help
Shifting
the
left
for
the
feedback
loop.
So
you,
so
you
wouldn't
need
to
run
cross-plane
to
see
like
what
how
your
composition
behaves
so
I
think
it's
a
like
great
capability
and
it
will
also
be
used
for
functional
development
as
well.
B
So
you
can
just
run
your
function
locally
and
see
how
it
renders
the
the
resources
so
I
think
it
looks
like
a
quite
a
nice
addition
to
the
function
picture.
Amazing.
A
I
I
did
not
know
that
Nick
had
already
gotten
something
up
and
running
for
that.
So
that's
that's!
Fantastic
progress
really
stoked
to
see
that
well
what
what
that
guy
can
do
without
without
his
fiber
internet
connection,
that's
amazing.
D
A
Alrighty
thanks
for
calling
that
out,
Hassan.
A
All
right,
so,
let's
go
into
the
next
section
here,
so
basam
I
see
you're
on
the
call
here
today
and
you
actually
made
this
announcement
at
the
community
Day
event.
Do
you
want
to
take
this
agenda
item
here
to
kind
of
talk
through
some
of
these
Charter
updates
and
the
donation
of
the
up
jet
Tech
framework
and
providers
that
upbounder
is
making.
D
A
All
right,
maybe
maybe
some
stepped
away
so
I
will
go
ahead
and
take
this
one,
then
so
yeah
so
I
have
a
community
day
on
Tuesday.
We
made
an
announcement,
two
big
announcements
here.
So
let's
walk
through
those
and
see
what
they
mean
and
then
we
can.
You
know
kind
of
answer
some
questions
if
folks
are
still
kind
of
curious
about
them
as
well.
So
the
first
one
here
is
that
we
made
a
update
to
the
Charter
to
expand.
It
include
and
essentially
include
more
things
within
the
scope
of
the
project.
A
So
you
know
over
the
last.
You
know
a
couple
couple
of
years
here:
we've
gotten
fairly
clear
feedback
from
folks
that
you
know
the
adoption
journey
of
cross
plain
is
it
has
its
challenges
and
it
has
some
obstacles
there
and
there's
a
number
of
things
that
could
be
included
within
the
project
that
would
facilitate
the
successful
adoption
of
the
project,
make
it
easier
to
use
and
make
it
easier
to
understand.
A
So
we've
got
more
explicit
about
that
and
added
you
know
made
this
official
Charter
updates
to
include
those
types
of
things
into
into
the
projects.
So
now
that's
kind
of
you
know
fully
sanctioned,
and
you
know
part
of
our
mission
here
and
you
can
expect
development
work
on
these
areas.
So
the
two
high-level
areas
is,
one
of
them
is
providers
in
general,
so
you
know
across
had
opinions
on
extensions
and
what
it
means
to
be
a
provider,
but
all
providers
were
essentially
outside
of
the
project.
They
were
kind
of.
A
You
know
in
a
we
have
a
neutral
place
for
with
you
know,
with
well-defined
governance
for
folks
to
collaborate
on
providers,
but
they
weren't.
You
know
really
part
of
the
project
officially,
and
so
you
know
now,
we've
made
that
possible
for
providers
to
be
you
know,
brought
into
the
project
and
have
more
of
a
complete
experience
and
support
around
those,
and
the
other
area
was
this
kind
of
broad
but
fairly
impactful
area
of
developer
experience.
So
you
know
in
the
charter
before
there
was
a
gap
there
around.
A
You
know
tooling
and
experiences
and
stuff
like
that
automation,
Etc.
That
would
help
you
to
build
your
platform.
You
know
build
compositions
and
you
know
have
a
good
experience
around
those
and
your
early
feedback
and
all
that
sort
of
stuff.
A
You
know
it's
a
manager
control
plane,
so
you
can
expect
with
some
of
that
developer
experience.
Expansion
of
our
Focus
to
I
mean
the
end
goal
here
is
to
make
cross-plane
a
more
complete
Project
without
these
gaps
in
it
and
to
make
it
easier
to
use
and
easier
to
adopt.
That's
really
the
whole
point
of
this.
This
effort
here
to
expand
the
charter
so
highly
related
to
that
is
the
other.
A
The
other
announcement
that
was
made
on
Tuesday
as
well,
and
you
can
read
some
details
in
this
blog
post
here
also,
but
essentially,
let's
take
a
look
at
the
steering
committee
vote
so
essentially
upbound
as
a
as
a
company
has
been
working
on
a
you
know,
the
upjet
framework,
which
enables
you
to
do
code
generation
of
crossband
providers
fairly
easily,
and
it
has
created
a
set
of
providers
as
well.
A
All
those
have
previously
been
underneath
the
outbound
organization-
and
you
know,
with
a
permissive
Apache
2
license,
but
you
know
vendor
vendor
run
completely
that
there
was.
They
were
part
of
the
outbound
organization,
so
we
we
took
a
vote
here
to
accept
the
donation
from
upbound
of
both
the
upjet
framework
and
then
some
of
the
providers
as
well
like
AWS,
Azure
and
gcp
providers
from
upbound
to
and
include
those
or
merge
those
into
the
crossfiting
organization.
A
This
is
really
the
way
to
look
at
this
I
think
is
really
a
governance,
a
governance
thing,
so
the
license
is
still
Apache
too,
but
that
does
not
change,
but
basically
this.
This
donation
here
gives
the
providers
and
and
the
update
framework
to
the
crosswind
project
to
the
cloud
native
Computing
foundation.
So
there
would
be
there
would.
It
is
not
possible
then,
to
re-license
them
in
the
future
and
change
that
to
any
more
restrictive
licenses.
A
They
will
be
open,
they
will
be
belonging
to
the
foundation
and
we
believe
that's
a
more
sustainable
model
for
for
these
providers
to
to
exist
in
the
community
context
instead.
A
So
let
me
see
if
there's
some
more
links
to
talk
about
there
and
then
we
can
kind
of
address
anything
that
comes
up
here
yeah.
So
there
will
be
a
deeper
blog
post
here
from
the
Crossland
team.
I'll
be
trying
to
write
that
in
the
next
next
few
days,
or
so
to
kind
of
explain
more
details
around
this
and
you
know
answer
any
questions
that
come
up
there.
So
there
will
be
some
more
content
around
that
and
Pete.
You
wanted
to
make
a
note
here
as
well
about
the
docs.
D
Yeah
so
with
the
providers
being
out
of
scope
for
cross-playing
we've
not
really
done
much
to
talk
about
providers
and
documentation
outside
of
the
provider.
Object
we're
working,
I'm
kind
of
thinking
through
some
of
the
specifics,
but
effectively
we'll
be
open
to
starting
to
document
providers
and
some
components
around
them
inside
of
Prospect
documentation
going
forward
so
I
think
it'll
make
especially
the
authentication
components
which
has
been
real
tricky
for
folks.
A
lot
easier,
a
lot
more
discoverable.
A
Yep
thanks
for
that
Pete,
that's
definitely
a
logical
extension
of
Fighters
coming
into
the
charter
of
the
project
and
belonging
there
to
have
docs
there
as
well.
Then
I
see
there's
a
couple
things
going
on
in
the
chat
here
like
Jason
was
asking
about.
A
You
know
we
that
upbound
mentioned
that
they're
really
changing
the
way
that
we're
generating
providers
over
time
and
if
that's
going
to
be
part
of
upchat
or
something
else
it
looks
like
Assam
did
answer
that
in
the
chat
and
mentioned
that
that
will
that
is
intended
to
be
part
of
upchat
as
well,
and
that
all
developments
and
work
on
providers
there
will
be
done
within
the
community
after
this,
and
this
move
has
happened.
A
A
major
question
that
comes
up
for
almost
everybody
from
this,
so
I
want
to
go
ahead
and
address
it.
Right
now
is
is
about
like
a
migration
impact
here,
and
so
the
intent
here
is
that
this
moves
the
projects
to
a
new
home
to
the
Cross
plain.
You
know
crossbane
related
or
GitHub
organizations,
but
it
does
not
change
the
the
know.
Api
types
of
the
group
value
kinds
Etc.
A
So
there
is
intended
to
be
zero
migration
effort
for
for
folks
that
are
already
using
these
providers
that
you
know
you
would
not
have
to
change
schema
or
change
change.
Anything
like
that,
the
so
that
should
be
a
smooth
process
there
and
that's
a
I
wanted
to
address
that
right
away
and
then
Jason's
also
asking
about
generating
from
open,
open
tofu.
So
the
the
plan
on
that
right
now
Jason
is
that
you
know
we
we
want
to
we
want
to
so.
A
Oh
sorry,
so
this
is
about
generating
a
knots
nuts
like
runtime
usage
of
it.
That's
a
good
question:
I,
don't
I,
don't
see
an
immediate
like
desire
to
move
or
change
to
to
using
open,
tofu
right
right
now,.
F
I
can
I
can
add
some
context.
Yeah
yeah
with
the
plan
is
to
remove
terraform
completely
from
the
providers.
Sorry
from
from
the
crossbank
providers,.
F
We
are
going
directly
to
the
npl
licensed
providers
as
part
of
object,
and
there
is
no
intermediate
terraform
CLI
def
engine
open,
tofu
or
not
so
so.
The
short
answer
is
no.
We
will
not
be
using
open
Tofu
for
code,
generate
code
generation
or
anything
else
on
that
we're
going
directly
to
the
MPL
licensed
terraform
providers.
A
F
The
terraform
provider
schema
which
every
provider
publishes
so
it's
part
of
the
provider
itself.
It's
really
very
little
change
from
what
we're
doing
it's
just
the
invocation
path.
As
I
understand
it
will
not
go
through
terraform
CLI
going
forward,
it'll
be
directly
to
the
providers
versus
going
through
an
intermediate
CLI.
D
A
Yeah
I
think
this
maybe
speaks
to
you
know
future
plans
as
well
of
you
know,
more
close
relationships
with
the
cloud
providers
themselves
and
you
know
building
cross-plane
providers.
You
know
based
on
you,
know,
code
generation
from
their
native
python
pipelines
themselves
and
you
know
avoiding
terraform
altogether
and
you
know,
which
is
the
the
long-term
Vision
here.
I
think
that's
like
a
sustainable
model
that
results
in
high
quality
and
you
know
deeper
investments
into
the
providers,
and
so
you
know
in
that
model,
that's
it's!
F
Yeah
I
mean
look.
The
the
goal
of
this
move
is
that
we
can
have
these
discussions
in
this
forum
here
and
I.
Think
everyone
benefits
if
there
are
really
high
quality
providers
with
High
coverage,
full
coverage
and
are
maintained
by
you
know
an
active
and
Vibrant
Community
or
even
the
infrastructure
of
Engineers
themselves.
F
And
if
there
are
lots
of
providers
and
there's,
then
there
is
a
choice
that
detracts
from
you
know
the
oh,
the
tracks
from
the
you
know
being
able
to
get
started
with
crossband
and
use
it
more
effectively,
so
I
think
over
time.
We
are.
Our
goal
is
to
try
to
converge
these
providers,
but
that
discussion
will
happen
here.
Not
you
know
in
other
places,
just
if
it's
so
now
possible
to
have
that
as
part
of
the
community
discussion.
A
Yep,
exactly
all
right
awesome
thanks
for
for
your
contributions
to
to
talking
through
this,
these
updates
as
well
man,
so
we
we
briefly
then
got
into
you
know
how
developer
experience
as
a
whole
is
now
part
of
the
charter
of
the
cross
between
project.
So
I
did
want
to
call
out
some
of
our
our
plans
around
that
and
and
ways
to
start
getting
involved
there
too.
A
So
1.14
does
you
know,
as
we
discussed
has
about
a
month
left,
there's
not
a
lot
of
time
left,
but
we
do
have
a
high
level
tracking
issue
here.
A
That's
a
road
map
item
and
part
of
1.14,
where
we're
kind
of
getting
a
little
bit
more
clear
about
what
type
of
functionality
we
would
want
to
have
to
improve
developer
experience
in
Cross
plain
in
this
in
this
time
frame,
so
I
think
a
big
takeaway
here
is
that
composition
functions
as
a
whole
has
a
lot
of
Investments
to
make,
and
you
know
strongly
believe
that
with
the
right
Investments
and
the
right
experience
that
that
will
be
a
big
leap
forward
for
the
expressiveness,
the
the
flexibility
and
the
ease
of
use.
A
Actually,
two
of
cross
blame.
So
there
are
a
number
of
plans
here
that
we
have
for
building
experience
around
the
building,
testing
and
usage
of
composition
functions,
so
some
developer
effort
will
definitely
go
into
building
that
developer
experience
around
composition
functions
in
1.14.
A
So
what
we
ship
in
1.14
for
composition
functions
is
fairly
complete
and
then
also
we'll
get
a
start
on
more
General
cross-plane
functionality
to
make
you
know
around
with
this,
in
the
spirit
of
making
crossblade
easier
to
use,
for
instance,
a
diagnose
command
in
the
crossband
CLI
to
be
able
to
track
down.
You
know
what
it
might
be
wrong
with
resources
in
your
cluster
and
get
you
short
track
shortcut
any
sort
of
debugging
there
and
give
you
a
direct
answer
very
quickly.
A
With
this
tooling,
you
could
see
something
similar
where
we
have
plans
going
in
on
the
roadmap
going
into
say,
1.15
as
well
and
kind
of
continuing
to
build
more
functionality
to
into
the
cross-plane
tooling,
but
also
shift
left
a
lot
of
the
experiences
here.
So,
for
instance,
validation
right
now
on
compositions
is
done
at
apply
time
where
you,
you
know,
on
your
live
cluster
you're.
Applying
your
composition,
and
if
there
is
something
wrong
with
it,
it
will
result
in
a
failure
that
you
need
to
track
down.
A
We
want
to
provide
more
tooling
and
functionality
to
shift
that
left
to
build
time
and
make
your
build
time
easier
to
produce
functional,
successful
Cloud,
cross-band
platforms
and
compositions
early
on.
So
these
some
of
these
plans
are
getting
captured,
still
and
added
being
added
to
the
roadmap.
Now
that
we've
just
expanded
the
charter-
and
you
know
taking
the
opportunity
to
add
all
this
interesting
stuff
into
the
roadmap
as
well
and
I-
am
inviting
folks
as
well
to
get
involved
directly
with
this
effort
too
so
I've
started
a
brand
new
special
interest
group.
A
We've
got
I
think
like
seven
or
eight
of
them
right
now.
Now
this
new
special
interest
group
would
be
focused
on
developer
experience.
So
I
don't
think
this
PR
has
been
merged
yet
to
add
a
link
to
it
to
the
readme.
But
essentially
you
can
it's
just
like
the
other
sigs
in
Cross
plain
there's
a
new
slack
channel,
for.
Let
me
make
this
a
little
bit
more
Sig
of
x,
I!
A
Think
it's
that
actually
so
on
Crossman
slack
feel
free
to
join
sigdevx
and
we
can
participate
and
collaborate
together
on
improving
the
usability
and
experience
around
cross-plane
in
a
cloud
operative
fashion,
and
we
will
also
be
getting
a
a
recurring
meeting
going
together
for
folks
that
are
interested
in
the
experience
around
cross-plane
that
we
can
have
a
synchronous
point
of
conversation
as
well.
So
folks
that
are
interested
in
that.
Please
do
join
that
slack
Channel
and
we'll
be
meeting
together
soon
to
be
pushing
all
this
effort
together.
Collaboratively.
A
All
right,
well,
I,
think
that
was
the
last
agenda
item
here
that
was
captured
in
the
dock.
So
if
folks
have
anything
else,
they
want
to
add
speak
up
now
and
otherwise,
if
there's
nothing
else,
then
we
can
go
ahead
and
adjourn.
A
All
right,
well,
then,
I
guess:
that's
it
good
to
see
everybody
today,
thanks
for
the
great
questions
and
really
excited
to
keep
moving
everything
forward
towards
1.14.