►
From YouTube: 2021-01-04 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
the
recording
has
started-
and
this
is
the
january
4th
2021
cross
playing
community
meeting
first
meeting
in
the
new
year
here,
so
welcome
to
2021
everybody,
and
I
hope
everyone
got
some
time
to
unplug
recharge
and
enjoy
the
holidays.
A
So
I
didn't
have
a
like
a
super
strong
agenda
myself.
Today.
It
was
like
some
of
this
is
gonna,
be
kind
of
getting
things
paged
back
in,
I
suppose,
and
just
kind
of
getting
getting
all
aligned
again
and
and
sort
of
picking
up
where
we
left
off
and
also
at
times,
maybe
remembering
where
we
left
off
as
well
too.
A
So
in
the
first
section
here
I
just
kind
of
wanted
to
talk
about
the
road
map
we
just
released
v
1.0,
which
was
amazing
work
from
the
team
here
before
the
community
day
before
we
all
went
on
holiday
break.
So
the
1.0
is
out-
and
you
know
it's
a
great
statement
on
getting
being
ready
for
production
usage
and
all
sorts
of
things
like
that,
and
the
next
phase
here
will
be
beyond
1.0.
So
the
next
next
release
like
1.1,
so
we
have
the
roadmap
has
been
updated
here.
A
So
you
know
if
you
want
to
check
out
the
crossplane
repo
and
then
the
roadmap.md,
we
have
a
1.1.
You
know,
what's
next
section
there
with
a
little
bit
of
details
and
then
the
project
board,
I
don't
think
really
has
been
updated
yet
so
we
can
kind
of
do
that
in
the
next
sorry.
A
Expert
planning
or
something,
but
you
know
we
tried
to
capture
a
little
bit
about
the
main
areas
we'll
be
focusing
on,
and
some
of
this
may
need
a
little
bit
of
updating
here,
but
I
would
love
to
hear
some
updates
from
folks
about
thoughts
of
focus
areas
and
places
where
we'll
be
investing
in
this
next
milestone
in
1.1.
A
C
Yeah,
I
think
the
this
roughly
covers
it.
You
know
if
we
go
back
to
the
road
map,
I
think
that
that
is
fairly
up-to-date,
and
so
you
know,
there's
some
carryover
stuff
from
composition,
rolling
into
a
1-1
release.
You
know
sporting
multiple
api
versions
as
we
look
to
go
beyond
100,
is
something
I
think
that
we
talked
about
for
for
package
manager.
C
There's
some
improvements
around
the
code,
gen
for
better
crr
handling,
with
the
array
of
resource
references
off
of
the
managed
resources
that
might
be
worth
the
discussion
nick.
If
there's
any
additional
thinking
on
that,
if
we
still
want
to
go
that
route,
the
multi-language
support
I
kind
of
wrapped
up
the
year
post
community
day
with
designing
pr,
for
you
know,
based
on
some
of
allah's
feedback.
So
I
put
that
in
the
agenda
for
discussion,
but
what
other
stuff
is
there
floating
around
dan?
B
Yeah
I
listed
a
few
things
in
the
the
dock
that
could
be
relevant
for
the
package
manager,
mostly
just
around.
You
know,
different
upgrade
functionality.
So,
like
one
of
the
big
things
we
talked
about
with
the
package
manager
that
wasn't
something
that
was
in
the
1.0
release
is,
you
know,
safeguards
about
rolling
forward
to
new
versions
and
that
sort
of
thing,
and
so
I
anticipate
that
will
be
a
big
focus
area.
There
is
in
terms
of
like
more
critical
things.
B
I'd
say
there
is
kind
of
a
bug
you
could
call
it
for
upgrading
to
a
new
version
of
a
package
if
there's
a
dependency
that
has
a
different
package
name
so
right
now,
the
dependency
resolver
will
create
a
new
package.
If
there's
not
a
dependency
that
exists
right
and
it
needs
to
be
there
if
that
dependency
has
the
well.
If
it's
in
the
middle
of
upgrade
right,
you
might
not
have
a
revision
in
place,
and
so
the
dependency
resolver
will
say.
B
If
the
names
match,
that's
not
an
issue,
because
the
dependency
resolver
will
try
to
create
the
package
and
say:
oh,
I
see
one
already
exists
here,
so
it
doesn't
matter
so
basically,
the
the
problem
area
here
is
when
you've
installed
something
and
then
you
install
something
that
depends
on
it.
So
it's
not
auto
resolving
the
dependencies.
It's
recognizing
that
one
is
there,
but
it
just
has
a
different
name
than
the
dependency
resolver
will
default
to
using.
B
D
D
Reloading
state-
and
I
I
kind
of
want
to
do
like
a
big
planning
exercise
like
more
than
usual
sprint
planning
to
just
just
load
up
everything
that
we
could
possibly
work
on
and
then
get
a
bit
of
a
to
kind
of
take
the
road
map
and
boil
it
down
a
little
bit,
for
I
don't
know
the
next
quarter
or
so
just
for
our
team
to
make
sure
that
we've
got
a
good
idea.
A
C
D
C
C
Bugs
I
think
that
ultimately
got
caught
in
the
the
the
stacks
or
the
platform
configs
or
whatever,
and
so
a
lot
gave
feedback
that,
for
all
you
know,
languages
supported
by
jsii,
which
is
basically
the
multi-language
support
that
amazon's
created
for
cdks
or
for
cdk
and
for
all
the
cdks.
But
you
know
it
basically
supports
like.net
java
python
they're
going
to
be
adding,
go
support,
and
so
you
know
using
the
fluent
api.
C
It
won't
necessarily
translate
well
to
all
of
those
and
he's
kind
of
lived
that
and
so
basically
put
together
a
little
design
here.
That
you
know
addresses
some
of
those
issues
and
provide
some
examples
down
below
about
what
that
would
actually
look
like,
and
I'm
pretty
happy
with
that.
C
It
definitely
like
is
more
dry
than
you
would
otherwise
get,
and
you
get
all
the
compile
time
checking
for
the
things
that
you
need
and,
like
I
said
it
kind
of
surfaced,
a
handful
of
bugs
that
you
know
things
were
like
mistyped
or
fields
that
were
in
there
that
weren't
correct
it
just
would
be
solved
in
part
by
you
know
some
validating
web
hooks
for
compositions,
and
things
like
that.
C
You
know
before
I
got
too
far
along,
but
at
design
time
you
know
it
definitely
kind
of
made
things
quite
a
bit
cleaner
and
fairly.
C
Not
a
ton
of
indentation,
which
kind
of
made
the
editing
experience
very
cumbersome,
and
so,
if
you
all
want
to
take
a
look
at
this
and
drop
some
comments,
that
would
be
appreciated
and
you
know
then,
if
you
go
back
to,
I
guess
that
pr,
I
think
I
dropped
a
link
at
the
bottom.
C
A
lot
dropped
a
post
that
was
super
useful
over
the
break
and
it
kind
of
highlighted
the
fact
that,
as
we're
moving
more
towards
like
running
things
behind
the
api
line,
as
opposed
to
during
build
time
yeah,
if
you
go
to
pr
34
there,
and
then
I
think
it
just.
I
think
I
dropped
a
comment
at
the
bottom
of
this.
But.
C
C
Yeah,
oh,
you
responded
yeah,
so
there's
just
some
issues
where
they
they
have
memory
leaks
due
to
the
way
that
they
actually
model
this
and
so
running
that
behind
the
api
line
is
kind
of
an
open
issue
that
they
need
to
like
rewrite
portions
of
jsii,
to
really
support
kind
of
a
broader
set
of
use
cases,
and
so
that's
kind
of
throwing
into
question
the
whole
thing.
C
In
my
view,
if
we
can
use
this
behind
the
api
line
in
a
reliable
way,
unless
we
kind
of
you
know
just
spin
up
temporary
side
cards
or
something
I
don't
know
so,
there's
more
investigation,
that's
required
here,
but
I
wanted
to
make
everybody
aware
that,
like
we're
kind
of
investigating
this
path,
you
know
the
the
wx
feels
pretty
good.
C
There
are
some
open
issues,
as
is
called
out
here,
for
running
things
behind
the
api
line,
and
I
think
we
just
need
to
have
like
a
higher
level
brainstorm
on
where
we
want
to
go
next
and
the
experience
we
want
to
provide.
But
yeah.
A
Yeah
and
it'll
be
good
to
talk
about
this
effort,
phil
in,
like
the
greater
context
that
nick
was
kind
of
bringing
up
to
around,
like
a
bigger
planning
exercise
and
all
the
things
that
we're
doing
and
where
we
want
to
put
some
effort
for
it,
etc.
And
you
know
the
priorities
around
everything
kind
of
just
repage
everything
in
and
understand.
You
know
where
what
we're
going
to
be
focusing
on
on
2021
after
you
know,
going
really
hard
to
get
1.0
out
by
the
end
of
2020.
A
I
think
casey
and
both
casey
and
move
off
or
not
online,
to
give
an
update
on
some
of
the
recent
efforts
around
provider,
the
cogen
and
provider
acceleration
stuff
phil.
Do
you
do
you
know
the
latest
data
set,
or
I
mean
nick.
D
You
know
that
not
in
great
detail.
I
do
know
that
casey
did
a
very
big
push
at
the
end
of
last
year
before
he
went
on
vacation.
I
think
he
was
like
right
on
the
cusp
of
getting
terraform
kojin
sort
of
actually
functionally
useful
end
to
end.
So
I
think
it's
if
it's,
if
it's
not
there,
it's
really
close
so
we'll
find
out
soon.
I
hope.
B
D
A
The
community
day
how's
that
work,
so
that
was
really
cool
awesome
yeah.
So
I
think
that
you
know
at
this
point
I
think,
like
a
release
schedule
for
1.1.
Doesn't
we
don't
have
enough
information
to
do
that?
I
think
we
need
to
do
a
bigger
planning
exercise
and
understand
everything
that
we
want
to
put
into
it,
and
you
know
where
the
priorities
are.
D
Yeah,
that's
what
I
was
going
to
say,
or
at
least
I
remembered
us
talking
about
wanting
to
tweak
the
release
schedule
to
maybe
give
it
a
little
bit
more
time
between
releases.
Realistically,
we
often
end
up
doing
six
to
eight
weeks
per
release.
Anyway,
despite
our
stated.
A
Yeah
and
in
general
I
don't,
I
personally
don't
have
a
big
problem
with
that.
I
think
that
you
know
the
situation
I
don't
necessarily
want
to
get
into
is
when
we,
you
know,
go
like
early
on
in
the
project
between
like
zero
one
zero,
two
zero
three
we
were
doing
like
four
or
five
months.
I
think
at
a
time
which
is
definitely
people
are
gonna,
end
up
waiting
for
fixes
for
much
longer
than
they
should
so.
You
know
like
four
weeks
six
weeks.
A
D
Yeah,
I
mean
one
thing
to
keep
in
mind
now
as
well.
Is
that,
with
the
with
the
release
of
crossplay
1.0?
That
means,
theoretically,
the
the
sort
of
feature
changes
cross
plane
are
gonna
sort
of
you
know
we're
gonna,
hopefully
start
to
get
a
little
bit
more
boring
and
just
be
sort
of
keeping
the
core
of
cosplaying
running.
I
I
do
think
it
was
only
1.0,
so
we
are
going
to
add
some
more
features.
D
Obviously,
but
there
won't
be
breaking
api
changes
there,
which
also
means
that
we
should
have
good
compatibility
with
our
providers
from
now
on.
So
we're
not
going
to
be,
as
I
don't
think,
there's
going
to
be
as
much
of
a
need
to
ship
every
provider
in
the
world
every
time
we
should
cross
planes,
so
maybe
one
thing
we
could
consider
is
keeping
a
faster
cadence
for
providers
or
something
or
you
know,
biting
the
bullet
and
saying
providers
release
when
they're
ready
they
have
their
own
release.
Teams
and
crossplay
gets
released.
A
B
Yeah
another
thing
to
note
there
is
the
six
weeks
would
be
for
a
new
minor
version,
but
we
we
should
have
patch
versions
whenever
they
need
to
go
out
right.
So
we
could
be
releasing
those
every
day
if
we
needed
to
so
something
to
keep
in
mind
there.
We
haven't
really
had
many
needs
for
a
patch
release
in
the
past,
because
with
our
like
velocity,
combined
with
the
cadence
that
we
were
releasing,
which
was
pretty
quickly
at
least
in
recent
months,
then
right.
B
The
the
patches
weren't
really
super
relevant,
but
we
may
want
to
just
start
doing
patches
like
every
two
weeks
or
something
that's
what
we
do
upstream
or
you
know
around
there,
depending
on
the
the
time
of
the
release
cadence,
so
something
to
think
about
yeah.
A
A
Cool
anything
else,
anybody
want
to
bring
up
about
1.1
or
roadmap
beyond
et.
A
Cetera
cool,
let's
jump
down
to
the
community
topics,
then
so
yeah.
So
right
before
the
holidays,
we
did
the
second
crossman
community
day.
That
event
was
definitely
a
big
success.
I
think
we
had
some
amazing
speakers,
some
really
cool
stuff,
that
we
were
showing
off
the
1.0
release
was
right
before
the
event
as
well
too.
So
it's
definitely
a
a
really
good
place.
A
I
think
for
the
crossfit
project
to
be
in
as
a
whole
to
have
that
1.0
out
to
you
know,
have
some
stability
to
be
production,
ready,
etc
and
then
to
have
an
amazing
event,
come
together
to
kind
of
celebrate
it
a
bit
as
well
too
and
then
get
some
time
off.
So
the
recordings
have
been
posted
to
youtube
so
on
this
playlist
here
we
have
all
of
the
community
day
recordings.
A
But
cool
yep
yeah,
so
thanks
everybody
for
the
great
work
that
went
into
not
just
the
community
day,
but
also
mondatto
as
well
too.
I
think
that
we
have
a
lot
of
things
to
be
really
proud
about
to
be
accomplished
in
2020,
so
super
excited
about
that
and
what
we're,
what
we
all
did.
C
Yeah,
it
was
awesome
to
see
the
whole
community
kind
of
really
come
together
around
that
and
all
the
people
that
came
to
to
talk,
and
you.
D
A
Definitely
cool
so
were
there
any
particular
prs
or
other?
You
know
technical,
deep
dives
to
do
that.
Folks,
hadn't!
Yet
added
to
the
agenda.
C
No,
I
think,
we've
covered
it.
You
know
so
nick
if
you
want
to
maybe
schedule
some
time
for
like
planning
exercise
and
also
maybe
like
a
retro.
You
know
for
like
one
hour
that
might
be
nice
yeah.
D
I've
got
a
for
out
for
our
about
team.
I
put
in
a
retro
already,
I
think,
for
thursday
morning
and
planning
I
feel
like
it
might
be
nice
to
break
the
planning
up
over
two
sessions
or
something
like
do
like
wednesday,
then
thursday
or
something
so,
we
can
just
sort
of
do
a
pre-game
like
brainstorm
for
an
hour
and
then
come
back
the
next
day
and
like
actually
put
it
all
together
or
something
like
that,
so
I'll,
try
and
find
some
time
for
that
as
well.
A
Yep
sounds
great
cool.
If,
if
we
didn't
have
anything
else
at
this
this
in
the
agenda
here,
then
then
we
can
continue
that
effort
to
figure
out
the
planing
and
and
get
get
the
q1
playing
here
for
a
cross
playing
project
like
more
solid
over
the
the
next
week
or
so,
and
then
we
can
break
off
here
and
if
slack
is
going
to
be
nice,
then
we
can
keep
talking
on
slack.
C
Very
cool
so
and
I
did
see
that
a
lot
came
back
and
he
said
that
they
do
spawn
a
new
child
process
for
every
cdk.
It's
invocation
behind.