►
From YouTube: 2020-09-14 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
september
14th
2020
cross,
plane
community
meeting-
feel
free
to
add
yourself
to
the
attendees
list.
If
you
are
not
already
there,
let's
hop
into
talking
about
the
0.13
milestone
that
we
are
actively
working
towards
right
now.
The
planned
release
time
frame
is
about
23rd,
maybe
24th
somewhere
around
there.
So
that's
next
week,
mid
to
late
next
week,
we've
been
tracking
issues
on
the
organizational
level
project
board,
but
we
can
dive
into
some
of
the
specifics
right
here.
A
Thank
you,
dan.
We're
accepting
boss
edition
as
movement
types.
It's
like
yes,
yes,
yes,
yes,
all
right,
let's
see
so
I
don't
see
casey
here
but
phil.
Would
you
like
to
please
get
us
going
with
an
update
on
the
provider
acceleration
code
generation
stuff?
I
know
there
was
a
some
cool
stuff
with
some
of
the
providers.
Specifically
too.
B
Yeah
totally
so
so,
kfc
is
making
progress
on
the
provider
acceleration,
but
then
also
helping
out
with
the
code
gen
for
native
aws
and
native
azure
providers.
And
so
we
had.
You
know
cool
hack
session
last
week
with
jay
pipes
from
aws
and
she's,
putting
together
a
pr
for
adapting
the
ack
cogen
pipeline
to
emit
a
couple
cross,
plane
resources,
and
we
feel
that
once
that's
done,
it
will
be
able
to
just
co-generate
the
whole
thing.
B
So
they
have
metadata
from
you
know,
like
all
the
aws
services,
so
super
exciting
progress
there
so
still
more
work
to
be
done,
but
I
think
jay's
will
be
putting
together
a
a
branch
called
crossplane
in
his
fork
of
ack
for
the
code
gen
there.
B
C
B
So
you
know
dave
and
matt,
and
christian
and
bevin
and
george,
and
so
there's
a
a
pr
opened
up
for
adapting
the
azure
coach
on
pipeline
to
to
emit
cross-plane
resources,
there's
kind
of
initial
design.
Thinking
around
that,
so
we've
just
been
going
back
and
forth
and
providing
some
feedback
and
collaborating
together
and
yeah.
So
that's
super
awesome
progress
there,
but
then
also
for
the
terraform
wrapped
code
gen.
You
know
that's
all
proceeding
for
providers
that
don't
have
cogent
pipelines
and
so
yeah.
B
So
multiple
fronts
and
super
exciting
times-
and
you
know
the
really
nice
thing
will
be-
is
that
with
all
of
those
providers
being
auto
generated
that
you
can.
B
Those
resources
into
your
own
into
your
own
abstractions,
with
composition
and
cross
planes,
so
really
nice
to
see
kind
of
that.
That.
A
Cool,
especially
like
the
integration
into
the
code
generation
pipelines
that
would
you
know
from
the
providers
themselves
that
would
be
generating
cross-plane
resources
from
the
you
know,
from
their
like
definitions
of
their
apis
like
the
source,
I
think
that's
super
exciting.
B
A
Yeah,
win-win
cool
all
right
move
off.
Do
you
want
to
give
us
a
quick
update
about
crossband
agent?
I
think
it's
been.
It
has
been
too
much
focus
on
that
quite
recently,.
E
Yeah
I
mean
the
there
is
this
compost
resource
definition
update
pr,
but
it's
been
there.
I
for
a
while
I've
been
waiting
for
final
review.
B
E
E
There
is
a
comment
on
my
first
pr.
Let
me
just
link
it:
okay,.
B
A
For
watching
sounds
good
dan
lots
of
action
with
the
update
of
the
package
manager.
Do
you
want
to
bring
us
up
to
speed
on
everything
that's
going
on
there.
C
Yeah
for
sure,
so,
let's
see,
I
think
it
might
have
been
since
last
time,
but
the
the
meta
types
were
emerged,
a
while
back.
C
Those
are
the
types
that
are
kind
of
like
on
disk,
where
you
specify
how
you
want
to
build
something
in
you
know
in
the
package
you're
creating
so
in
your
git
repo
before
you
build
it
and
push
it
and
that
sort
of
thing,
so
those
are
not
actually
crds
that
are
installed
into
a
cluster,
but
we
do
want
to
have
you
know,
actual
specs
for
being
able
to
read
those
and
evaluate
them,
and
that
sort
of
thing
so
those
have
been
merged
for
a
while,
which
is
nice
because
they
can
kind
of
help.
C
You
inform
how
to
write
a
package
while
we're
in
this.
In
between
stage
next
thing
is
yesterday
we
went
ahead
and
broke
out
the
api
types
from
the
kind
of
large
package
manager,
implementation,
pr
and
went
ahead
and
merged
that
so
those
actual
api
types
for
what
you'll
create
in
the
cluster
are
now
present.
The
reason
for
doing
that
early
was
this.
You
know
it's
kind
of
related
to
the
rbac
manager
and
some
of
that
work
as
well
so
going
ahead
and
getting
those
in
was
helpful
in
that
regard.
C
Other
things
to
note
the
scaffolding
for
the
crank
command,
the
crank
cli
was
merged,
so
those
are
just
basically
empty
commands
right
now,
but
we
went
ahead
and
got
that
merged,
because
casey
is
helping
me
get
some
of
that
implemented,
so
he's
taking
a
lot
of
the
package
building
stuff,
which
is
really
great.
So
I
appreciate
him
doing
that.
I'm
sure
he's
on
the
call,
but
we
had
some
good
conversations
around
that
so
that'll
be
good
to
see
land
and
also
now
that
those
api
types
are
implemented.
C
We
can
go
ahead
and
follow
up
with
adding
the
commands.
Do
you
know
list
those
from
the
cluster
and
that
sort
of
thing?
And
then
the
last
thing
is
the
the
actual
implementation
pr
is
getting
pretty
close.
I
am
just
cleaning
it
up
this
morning
and
breaking
it
out
to
be
a
little
more
digestible
and
a
little
bit
more
easily
testable.
C
There
will
be
some
follow-up
pr's
to
that,
some
related,
probably
to
the
helm,
chart,
structure
and
some
related
to
hosted
cross
plane
mode,
which
will
really
just
involve
plumbing
down
an
extra
client
to
the
package
manager,
but
it
made
it
a
little
bit
easier
to
digest
with
following
that
up
in
a
separate
one,
but
we
are
pretty
close
on
that.
We
had
a
good
demo
last
week,
so
yeah
this
should
all
be
landing.
It's
pretty
much
right
on
schedule.
C
Progress
there
for
sure
yeah
and
I
noticed
move
off
it
he's
taking
the
work
around
the
the
kind
of
like
unpack
base
image
stuff,
and
so
did
you
want
to
give
an
update
on
that
move
off
it
yeah.
I.
C
E
Had
one
small
question,
but
maybe
we
can
we
can
discuss
in
the
technical
discussion
session
cool.
A
Yeah
feel
free
to
add
that
down
to
that
section
then
move
off
and
we
can.
We
can
get
that.
Have
that
conversation
when
we
get
down
there
cool
and
then
nick
has
been
doing
a
lot
of
work
on
the
some
are
back
management
on
automation.
Nick,
do
you
wanna
give
us
a
quick
update
on
the
latest
on
that
one.
G
G
Actually
because
we
would
make
admin
view
and
edit
roles
for
every
namespace
in
the
system
that
were
actually
could
be
slightly
different
from
namespace
to
namespace,
depending
on
how
our
cross
plane
was
configured
so
we're
breaking
that
functionality
out
of
the
new
package
manager
and
we're
putting
it
in
a
separate
pod
that
we're
going
to
call
the
rbac
manager.
So
there's
a
design
and
a
pull
request
for
that.
G
Where
it
sort
of
manages
less
rbac
things
than
it
might
be
able
to
without
losing
package
manager
functionality
so
that
it
just
sort
of
decouples
those
two,
so
the
pr
that
is
open
at
the
moment
is
to
introduce
the
rmac
manager
in
general
and
allow
it
to
automatically
create
our
back
rolls
for
the
new
composite
resources.
G
So
if
you
add
a
composite
resource,
we'll
automatically
notice
and
create
our
back
roles
that
allow
or
update
our
back
rolls
that
allow
the
administrators
editors,
viewers,
etc,
to
use
that
it's
only
partially
implemented
at
the
moment,
because
some
of
it
does
depend
on
the
new
package
manager
types.
So
this
pr,
I
expect
to
be
merged
soon.
Today,
maybe,
but
as
far
as
as
far
as
a
community
is
concerned,
it's
it's
not
going
to
help
until
0.13.
There's
a
follow-up
here
needed
to
make
it
fully
functional.
A
That
sounds
great,
nick
awesome
yeah.
So,
let's
see,
I
think
ryan's
on
the
call
boss
is
on
the
call.
Do
you
does
one
of
you
all
want
to
get
us
updated
on
the
latest
for
own
kubernetes,
runtime
sure.
F
They're
not
too
much
going
on
in
the
past
two
weeks,
other
than
some
bug
fixes
some
improvements
and
the
one
big
thing
I
changed
is
so
nowadays
now
the
the
components
doesn't
have
to
use.
The
same
name
rely
on
the
name
convention
of
a
crd
to
refer
to
the
workload
definition
it
is.
F
So
we
introduced
not
it's
not
a
type,
it's
not
in
the
spec
and
it's
not
in
the
strongly
typed,
but
we
use
a
web
hook
to
support
a
type
field
in
the
component
so
that
a
user
can
refer
back
to
a
workload
definition
explicitly
it's
something
so
that
we
we
untie
this
entire
disk
conventions
to
make
a
workload
definition
to
refer
to
multiple
components
possible.
No,
I'm
sorry!
It's
a
multiple
workload.
Definitions
referred
to
the
same
schema
a
possibility,
so
it's
it
opened
up
the
in
the
yeah.
F
I
I
think
I
mentioned
last
time
that
it
is
ready
to
get
into
more
stable
states
yeah.
I
think
we
are
still
on
track
on
to
do
that.
So
please
let
let
us
know
when,
when
you're
releasing
zero
points,
13
or
13
or
14,
when
we
get
there,
we
can,
we
can
make
sure
we're
all
on
the
same
page,.
B
Days
out,
to
give
time
to
add
more
robust
documentation,
given
that
everything's
landing
all
at
the
same
time,
but
yeah,
hopefully
roughly
into
the
month
time
frame,
is
what
we're
shooting
for
sure.
A
Yeah
and
ryan:
are
there
any
like
big
blockers
or
you
know
pending
things?
Do
you
think
that
need
to
get
finished
off
before
you
know
the
home
kubernetes
runtime
could
do
you
know
it's
it's
first
like
stable,
ish
release.
You
know.
F
A
Yeah,
that
sounds
great
awesome.
Okay,
let's
see
here,
I
don't
know
if
there's
any
specific
updates.
Besides
some
of
the
other
items
here
that
are
in
service
of
advancing
composition,
I
don't
know
if
anybody
wants
to
speak
specifically
to
that
wasn't
mentioned
last
time,
at
least
about
any
any
more
progress
on
moving
composition
towards
v1
beta
1
then
speak
out
now.
A
All
right
so
did
you
add
these
items
for
custom
composition
and
like
cd
gates,
integration.
E
B
And
just
a
little
bit
more
color
on
that,
so
you
know
like
move
off.
It
said:
we've
been
working
with
a
lot
over
from
aws
on
cd,
kids
and
so
he's
put
together
kind
of
an
initial
repo
that
basically
has
a
new
command
to
pack.
B
It's
called
cdk
it's
pack
and
it
would
basically
generate
a
sidecar
image
that
would
contain
the
cdks
program
and
then
through
a
simple
sidecar
protocol
which
basically
just
spins
up
like
an
http
endpoint,
that
the
custom
controller
can
talk
to
the
custom
composition,
controller,
can
talk
to
and
it'll
just
feed
in
the
inputs
to
the
composition
and
then
cdks
will
render
dynamically
behind
the
kubernetes
api
line
and
then
return
the
resulting
yamls
that
would
be
applied
into
the
system
with
print
semantics.
B
So
you
can
definitely
check
out
the
link
here
and
then
I
think
that
this
references,
the
issue,
if
you
scroll
down.
B
Yeah
1678
the
open
issue,
second
down
in
the
comments,
and
so
that
basically
just
gives
a
little
bit
more
background
on
kind
of.
What's
going
on,
yeah
super
exciting,
so
go
ahead.
E
Yeah,
I
was
just
gonna
say
the
the
final
experience
we
would
like
is
that
like
cdk's
cli
will
include
a
comment
command,
maybe
it
will
be
like
pack
or
some
something
additional
that
will
basically
print
a
compose
resource
definition,
the
cross,
plane,
type
and
one
custom
composition,
cra,
which
is
also
cross
plane
type.
And
then,
once
you
apply
those
you
will
get
your
city
gates
at
like
acting
as
controller
for
your
composition.
So
it
will
be
a
pretty
neat
experience.
B
Yeah
totally
we're
looking
forward
to
this.
This
all
make
it
easier
to
dynamically
render
like
variable
numbers
of
resources
as
well,
behind
the
api
line,
so
yeah
super
cool
to
see
the
different
flavors
of
composition
coming
online,
very
cool.
F
A
And
rock
backpacks
here
that
you
need
to
speak
about.
E
Yep,
so
you
know
we
had
an
update
with
the
update
about
the
provider
type.
So
basically,
we
deprecated
the
provider
type
and
created
a
new
provider
config
on.
We
want
better
one,
a
level,
but
it
does
not
have
the
region
field
and
so
in
some
resource
in
some
aws
resources
they
do
not
require
the
region
field
in
their
requests,
but
during
the
client
config
they
use
that
region
in
order
to
specify
which
region
it
is
so.
Basically,
it's
like
when
you
created
the
credentials
like
when
you
authorized
to
the
aws
api.
E
It
actually
decides
on
which
region
and
in
the
actual
request,
you
don't
really
see
region
at
all.
So
this
caused
some
problems
since
we
removed
the
region
from
provider
in
some
services
like
ec2
services,
I
believe
all
of
them,
for
example,
right
now
in
monster
aws.
You
can't
really
create
a
vpc
because
it'll
say
just
it
will
not
be
able
to
construct
end
point
without
region.
Basically
so
this
so
I
am
working
on
the
on
the
fix
for
the
spot,
but
yeah
we
have.
E
A
G
So
movavic
we
we
talked
about
this
a
little
bit
the
other
day.
G
E
If
you
do
specify
you've
got
like
default
region
in
the
like
in
the
default
pro
profile,
you
have
also
the
region
so
in
the
api,
when
you
configure
it,
if
you
don't
provide
that
field,
it's
basically
empty,
it
doesn't
really
return
an
error
and,
during
the
actual
request
of
creating
anything
or
describing
anything
when
it
constructs
the
url
of
the
query,
it
looks
for
the
client
config.
E
So
basically,
I
believe
like,
if
you
don't
have
any
region
in
your
local
right
now.
The
aws
cli
also
has
the
same
experience
like
it
will
require
you
to
specify
a
region
during
the
setup.
Instead
of,
like
you
know,
creation
of
the
vpc.
E
Yeah,
I
mean
I've.
I've
also
investigated
like
if,
if
it's
just
like
a
you,
are
a
property
like
if
any
of
the,
if
any
of
the
regions
would
work,
but
that
wasn't
the
case
so
it
actually,
you
know
like
in
some
sense
region,
is
treated
like
resource
group
in
azure.
E
G
Did
you
say
it
again,
I
I'm
I'm
not.
I
don't
quite
follow
what
you
mean
by
resource
group.
I
I
thought
that
you
were
saying
that
there
was
an
implication
there
that
that,
while
you
technically
can
specify
the
region,
you
must
only
pick
a
particular
region
the
same
one
as
your
account
or
something
like
that.
E
Oh
so
what
I
meant
like
it's
like
a
like
in
some
cases,
for
example,
elastic
ip-
I
wouldn't
really
expect
to
have
any
region
like
intrinsically
like
ips,
wouldn't
have
any
region
and
stuff
but
like
when
we
look
at
the
api
like
it
actually
requires
a
region
so
like
in
some
cases,
even
if
it
doesn't
really
make
sense
for
the
resource
to
have
a
region.
It
actually
does
so
like
aws
streets
is,
in
some
cases
like
a
resource
group
like
logical
grouping
so
like
in
those
cases
like
we,
we
will.
E
We
do
need
the
region,
for
example
in
iem
resources.
There
is
no
need
for
such
that,
like
without
configuring
any
region,
the
client
works
because,
like
they
are
not
bound
to
any
region,
but
in
some
services
like
ec2,
even
though
it
doesn't
make
sense
to
have
region,
it
does
require
to
specify
that.
G
D
A
All
right
cool,
so
I
think
that's
everything
for
0.13
and
progressing
towards
that
next
big
release
and
milestone
for
for
the
cross
play
project.
So
we'll
stay
on
top
of
all
that
stuff
we're
discussing
and
keep
on
moving
towards.
You
know
next
week
late
next
week,
or
you
know,
figure
out
the
hone
in
on
the
exact
day,
but
we'll
keep
we'll
keep
making
progress
towards
that
to
get
0.13
out.
A
C
Good
enough,
that's
pretty
much
it.
I
just
note
that
the
the
main
reason
for
not
having
episodes
the
past
few
weeks
is
that,
while
we're
in
this
transition
period,
it
would
be
like
kind
of
strange
to
we.
We
could
either
say
like.
C
Oh,
this
is
how
things
are
going
to
work,
and
you
can't
use
it
now
or
this
is
how
things
currently
work,
and
this
is
going
to
be
irrelevant
pretty
soon
and
there's
some
leeway
in
between
there,
but
also
just
for
the
0.13
push
most
of
them
have
been
deferred,
but,
as
jared
mentioned,
a
product
of
that
is
that
we
have
a
lot
of
good
people
lined
up-
and
I
think
I
mentioned
this
one
before,
but
we
specifically
have
source
graph
on
the
calendar
as
probably
our
next
one,
and
that
should
be
a
pretty
cool
one.
A
One
all
right
awesome,
I'm
looking
forward
to
the
next
episode
there,
all
right
so
with
the
cncf
onboarding
there,
the
linux.
A
Is
they
have
the
all
the
dns
information?
I
have
not
heard
that
it
has
been
cut
over
or
they
have
not
needed
more
information
since,
since
the
well,
the
transfer
code
and
zone
file
was
was
sent
over
there,
but
we
definitely
will
want
to
make
that
transition
to
you
know
linux
foundation
hosting
or
managing
our
dns
for
us
for
crossfit.io,
with
no
or
minimal
to
no
interruption
to
the
crossband.io
of
site
availability.
A
So
we'll
work
with
them
when
that
time
comes
quick
note
on
coupon,
north
america.
A
Historically,
all
cncf
projects
have
gotten
a
session
for
the
maintainer
track
like
an
intro
session
or
a
deep
dive
session,
and
they
made
a
bunch
of
changes
for
the
upcoming
kubecon
virtual
event
for
north
america
in
november,
where
there
is
now
only
a
single
session
for
cncf
projects
as
there's
no
intro
or
and
deep
dive
session,
and
it's
also
no
longer
available
for
sandbox
projects.
So,
unfortunately,
since
we're
sandbox
projects,
we
do
not
get
a
maintainer
track
session
for
kubecon.
The
next
upcoming
cute
con
in
november.
A
Hopefully,
we'll
get
some
talks
accepted
from
the
call
for
proposals
that
we
submitted
stuff
for
a
couple
weeks.
I
don't
know
a
month
or
so
back,
maybe
so
we'll
have
our
fingers
crossed
for
that,
but
we
do
not
get
a
maintainer
track
section
session
anymore,
since
that's
a
new
change
from
policy.
A
Something
else
I
wanted
to
talk
to
us.
I
was
on
the
phone
this
morning
with
some
cncf
representatives
for
the
for
the
rook
project,
and
they
mentioned
that
the
community
bridge
program
is
ongoing.
They
still
accept
project
ideas
for
that.
So,
basically,
the
community
bridge
is
very
similar
to
google
summer
of
code,
but
it's
just
operated
specifically
by
the
by
the
cncf.
A
So
it
could
be
a
year-round
thing
as
opposed
to
only
a
summer
thing,
and
so
you
know
it's
basically
an
opportunity
to
if
we
have
any
projects
that
would
be.
You
know
good
for,
like
university
level,
students
or
you
know,
intern
type
of
thing
with
you
know
it's
a
mentorship
opportunity
where
the
where
the
mentee
can
you
know,
work
on
a
real
project
and
submit
real
code
to
the
crossplane
project,
but
also
ramp
up
and
get
some
guidance
from.
A
You
know,
mentor
from
the
community
to
kind
of
get
their
career
started
and
you
know,
contribute
and
know
what
it
kind
of
get
the
experience
of
what
it's
like
to
be
part
of
an
open
source
project.
So
you
know
if
we
have
any
ideas
for
projects
that
might
be
a
good
fit.
You
know,
I
think
it's
it's
kind
of
in
between
there's
a
line
in
between
you
know.
It's
not
just
like
a
single
bug
fix
that
you
want
to
rip
up
somebody
on
it's
not.
You
know
a
super
complicated,
really
deep.
A
You
know
pushing
the
envelope
type
of
project,
but
kind
of
maybe
somewhere
in
between
there.
For
you
know,
I
think
it's
at
least
a
couple
months
that
the
contributor
would
be
on
board
and
participating
and
they
get
a
stipend
and
such
as
well.
So
I've
done
the
I
haven't
done
community
bridge,
but
I've
done
the
google
summer
of
code
multiple
times
now
and
the
general
experience
of
having
a
you
know.
Young
contributor,
you
know,
could
get
into
open
source
and
start
to
get
their
career
started
and
contribute.
A
You
know
meaningful
code
is,
is
always
super
rewarding,
so
it's
pretty
fun.
It
helps
the
project
how
to
grow
the
community
get
a
new
contributor,
et
cetera,
so.
A
E
A
Okay,
so
we
don't
have
any
specific
pr's
listed
here.
Were
there
any
other
community
topics
by
the
way
that
folks
did
not
get
a
chance
to
add
to
the
agenda
doc.
D
A
C
Yeah
for
sure,
so
you
know
in
terms
of
like
functionality,
it's
going
to
be
pretty
similar.
One
thing
you
can't
do
with
the
current:
well,
you
can
do
with
the
current
cli,
but
it's
not
as
robust.
I
guess,
or
it's
not
using
the
ex.
The
new
package
format
is
build
and
push
those
packages
as
easily.
C
So
that's
going
to
be
a
real
focus
of
the
new
one
as
well.
As
you
know,
the
the
package
types
are
changing,
so
there
will
be
explicit
provider
and
configurations,
but
in
terms
of
of
you
know
the
the
usage
of
it
will
be
pretty
similar,
but
it
will
be
distributed.
You
know
inversioned
with
crossplane,
so
a
little
kind
of
like
similar
to
how
cubecontrol
is
but
yeah
it
should.
It
should
allow
us
to
be
a
little
more
robust
in
our
offerings
and
and
the
cli
in
the
future.
G
Yeah,
it
may
not
actually
change
very
much
from
the
current
experience
at
the
moment
we
have.
We
have
a
repo
called
crew-
cuddles,
sorry,
not
cool
cli,
which
adds
a
sub
command
to
coupe
cuddle
cross
plane,
that's
actually
mostly
just
all
shell
scripts.
So
one
thing
we
wanted
was
to
be
able
to
move
those
to
be
written
and
go
build.
You
know,
use
our
libraries
from
from
crossplay
etc.
G
So
so
that
will
be
deprecated,
as
dan
said,
it
doesn't
have
much
if
any
functionality
that
wouldn't
be
covered
by
this,
this
new
one
and
we're
still
figuring
it
out,
but
it's
it's
likely
that
the
user
experience
will
be
the
same.
That
it'll
still
be
cut
across
playing
whatever
some
commands
sort
of
thing.
D
Cool
all
right
yeah
I
was,
I
had
a
request
or
a
feature
request
on
it.
That's
been
there
for
a
while,
because
I
was
interested
in
importing
existing
resources
instead
of
having
to
fully
type
it
out.
Yeah.
C
Yeah
yeah
I've
heard
that
from
a
couple
of
people-
and
I
think
that's
something
we'd
definitely
want
to
support.
You
know
per
provider,
it's
you'd
kind
of
have
to
interact
with
some
back-end
facility
or
plug-in
to
be
able
to
do
that
to
know
how
to
basically
get
that
information.
C
You
know
from
from
the
existing
and
then
represent
it
and
then
have
it
hydrated,
basically
from
the
the
cloud
api.
So
it
might
be
interesting
to
think
about
how
we
could
have
some
sort
of
like
plug-in
for
that
or
if
we
had
some
sort
of
like
endpoint
in
the
cluster
that
you
could
talk
to.
If
you
had
that
provider
installed
to
help
with
that,
but
yeah.
C
That's
definitely
a
good
point
that
we
should
go
ahead
and
scrub
all
the
issues
in
crossplane
cli
and
make
sure
they're
represented
either
by
moving
them
over
or
you
know,
opening
ones
for
other
functionality
in
the
main
cross,
plane,
repo,
so
I'll
make
sure
to
go
through
that.
G
Yeah,
I
think
that
that
import
one
is
importing
resources.
Bringing
them
into
the
cluster
is
definitely
something
that
we
would
like
as
well.
I
forget
what
it
might
even
be
tagged
to
help
wanted.
As
dan
says,
the
problem
is
mostly
just
that
doing
it
in
a
sustainable
way
is
quite
hard
architecturally.
It
may
not
make
sense
to
have
our
cli
tools
start
to
have.
D
Yeah
I
figured
because
I
already
I
kind
of
pulled
that
thing
and
realized
had.
I
was
just
bash
scripts
and
I
even
tried
to
write
my
own,
but
then
I
did
realize
yeah
that's
a
lot
of
work
because
I'm
only
working
with
aws
and
I
realized
you
guys-
would
have
to
deal
with
like
azure
and
gcp
and
all
these
other
ones
too
right.
C
Yeah
one
thing
to
mention
there,
though,
is
that
you
know.
If
if
we
make
progress
on
ungenerating
these,
then
it's
possible.
We
could
have
an
interface
and
generate
the
same
kind
of
thing,
for
you
know
importing
resources
as
well,
but
yeah,
I
think,
that's
a
little
farther
down
the
line,
but
definitely
something
that
would
be
great
to
support
cool.
A
Right
on
kelly,
thanks
for
bringing
that
up-
and
you
know
getting
it's
always
good-
to
have
your
feedback
on
a
number
of
things
too,
by
the
way.
So
I
appreciate
that
for
sure
thanks
all
right,
so
yeah,
I
think
we
can
head
on
to
the
optional
time
for
deeper
technical
discussions
section.
So
in
this
section
here
you
know,
as
mentioned
it
is
optional.
So
you
know
these
are
more.
A
You
know
minutiae
details
about
specific
technical
issues
going
on
right
now,
so
anybody
who
wants
to
drop
off
is
more
than
welcome
to
before
we
kind
of
dive
out
and
dive
down
into
some
of
these
lower
lower
level.
Conversations
here.
D
E
Yeah,
so
actually
the
like
the
questions
answered
by
danielle
there,
so
I
just
want
one
to
make
sure
like
in
which,
in
which
step,
we
do
it
because,
like
in
the
in
the
format,
doc
that
nick
put
up
it
was
like
you
were
saying,
the
unpack
should
filter
resources
via
this
path
and
right
now,
the
implementation
that
I
have
does
that.
E
E
C
Yeah
yeah
and
nick.
Obviously,
since
you
worked
on
the
format
doc,
there
feel
free
to
jump
in
here.
But
my
thought
is,
you
know
one
of
the
advantages
of
having
it
be.
The
you
know
named
crossplan.yaml
is
that
we
can
actually
just
like
get
that
file
before
parsing
the
whole
thing.
So
what
I
imagine
is
on
the
kind
of
like
crank
side
of
it
that
we'd
actually
just
open,
crossband.yaml
file,
read
that
and
then
we'd
copy
over
in
that
step.
C
For
the
reasons
I
mentioned
in
the
comment
there
and
then
potentially
in
the
unpack
image
you
could
just
use.
You
know
like
the
file
system
back
in
for
the
parser
and
just
do
with
whatever's,
given
there
and
say
like
I
was
given
something
bad,
you
know
if,
if
it
doesn't
work
for
you,
there.
G
I
will
say
that
the
intent
of
the
ignored
I
mean
you
know
I
didn't
didn't,
spend
days
and
days
thinking
about
this
feature.
To
be
honest,
so
you
know
maybe
it
just
shouldn't
be
there
or
whatever,
but
the
intent
of
the
ignoring
was
you
have
a
directory
on
disk
and
you've
got
a
bunch
of
example
yamls
in
there
or
something
like
that.
That's,
like
here's
an
example
of
how
to
install
this
thing.
You
probably
don't
need
to
put
that
into
the
oci
image
that
delivers
the
package
because
it's
never
going
to
come
out.
G
E
Yeah
yeah,
I
agree
one.
E
There,
though,
is
that
the
oci
image
will
be
like
from
what
I
can
tell.
The
crank
will
generate
a
docker
file
and
then
like
this
docker
file
will
be
built
and
that
will
include
like
the
whole
package
but
like
in
that
docker
file.
It
could
be
a
little
bit
challenging
to
say,
like
hey,
this
directory
is
excluded,
so
maybe
I
don't
know
like
I
don't
think
copied
method
has
some
exclusion
arguments,
but
I
guess
we
can.
We
can
figure
it
out
somehow.
G
D
A
Thanks
that
all
sounds
reasonable,
nick
and
mavaca
did
you
all
get
enough
time
you
think
earlier
about
the
aws
region?
Discussion,
or
did
you
like,
like
feel
a
little
rushed
and
not
really
get
quite
some
closure
on
that?
Or
do
you
feel,
okay
with
it.
E
G
Okay,
that
sounds
good
yeah.
I'd
prefer
to
take
this
offline.
I
was.
I
was
so
that
that
solution
sounds
good.
The
only
thing
that
is
really
that
I
and
before
I
could.
I
have
a
one-on-one
after
this
anyway,
I
don't
understand
how
this
works
from
the
aws
api.
I
don't
I
I
keep
hearing
that
the
client
knows
the
region,
but
but
my
my
binary
on
disk
on
my
laptop
knowing
what
region
of
things
should
be,
doesn't
communicate
that
to
aws.
G
A
Got
it
cool
just
want
to
make
sure
you
all
have
the
time,
for
that
sounds
good,
okay,
any
any
other
items
in
the
for
the
agenda
today
that
were
not
in
the.