►
From YouTube: 2020-06-08 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
g18
2020
cross,
flane
community
meeting.
We
are
in
the
middle
or
I
guess
towards
the
latter
half
of
the
0.12
release
cycle
here.
So
we
let's
do
a
check-in
on
that.
Since
that
would
be
the
next
release.
You
know
we
typically
shoot
for
a
monthly
cadence
around
the
middle
of
the
month.
So
that'll
be
that's
coming
up
next
week
or
the
week
after
sorry
ended
this
week
or
the
week
after.
A
So
Nick
started
a
project
board
for
us
at
the
organizational
level,
so
something
that's
kind
of
tricky
with
bigger
projects
when
you
have
multiple
repositories,
is
that
you
know
when
you
keep
the
issues
it
next
to
the
code
that
they
are
pertinent
to.
Maybe
you
have
issues
scattered
across
a
lot
of
repositories
in
the
organization,
so
Nick
had
the
good
idea
to
create
a
project
board
at
the
organizational
level,
and
so
you
can
add
issues
to
this
0.12
focused
projects
here
and
you
know,
get
the
status
of
them.
A
Is
it
going
across
the
board
and
the
typical
Kanban
style?
So
these
are
a
set
of
issues
that
we're
working
on
and
tracking
that
are,
we
expect
to
be
included
in
these
0.12
milestone,
release
one
thing
that
is
good
about
every
she
says
they
just
not
able
to
get
any
audio.
Is
anybody
else
having
audio
issues.
A
Yeah,
maybe
maybe
Rishi
check
your
your
settings,
see
if
the
audio
outputs
is
give
me
your
headphones
or
your
external
speakers,
or
if
it's
going
to
some
other
bluets.
You
know
like
a
Bluetooth
device
that
your
family
is
listening
to
me
too,
on
in
the
rest
of
the
house
and
and
you're
not
able
to
hear
me,
it
could
be
one
thing
or
or
quit
the
zoo
meeting
and
come
back.
That
often
has
has
beneficial
results.
A
Okay,
so
yeah,
so
we're
tracking
issues
for
the
0.12
released
on
this
board.
Here
you
know
we
can
add
more
issues
to
it
that
other
folks
are
working
on,
or
you
know
kind
of
discuss
some
of
these,
but
this
is
kind
of
a
good
way
to
get
a
overall
aggregated
view
of
what
we're
working
on.
In
the
scope
of
this,
your
that
12
release
yeah.
B
I
just
add
a
bit
of
context
there
as
well.
Jared
I,
know
that,
or
we
are
close
we
could
have
been
out
from
our
usual
deadline
or
usual.
We
have
around
the
15th
to
release
point
twelve
o
point.
Eleven
was
a
pretty
big
release
for
us
and
we
are
somewhat
going
back
into
a
bit
of
a
planning
phase
for
what's
gonna
happen,
the
next
few
releases
and
what
priorities
are
so
this
this
board
went
always
a
little
tentative
made.
Might
change
a
little
bit
over
the
next
week
or
two.
A
Yeah
totally
ended.
Something
else
actually
he's
wanted
say:
I
totally
forgot
about
is
that's
one
of
the
beneficial
things
about
monthly
police
cadence
is
that
you
know
things
that
hey.
This
is
things
that
were
aspirationally
want
to
include
in
0.12,
but
there's
probably
very
few
things
that
we
would
hold
the
release.
For
you
know
if
it's
not
ready,
that's
okay,
we
can.
It
can
pick
up
the
next
release
in
the
next
month,
since
you
know,
there's
released
trains
leaving
every
month.
A
So
you
know
gonna
have
to
stress
out
too
much
to
get
everything
included
here,
and
this
is
giving
a
shape
of
the
release
and
over
time,
it'll
continue
to
get
more
accurate
as
status.
We
keep
this
board
up
to
date.
Status
of
the
issues
will
remain
updated,
but
yeah.
If
something
is
gonna,
be
included
in
the
0.12,
it
could
always
pick
up
the
next
0.13
release,
thanks
for
putting
that
together,
Nick.
A
That's
definitely
super
useful,
so
I
wanted
to
just
do
a
high-level
check
in
on
some
of
the
big
features
or
areas
of
investment
for
0.12.
So
what
of
the
is?
You
know
cogeneration
and
in
accelerating
or
expanding
the
surface
area
of
manage
resources
that
we
support,
KC
or
Nick.
Do
you
want
to
give
a
update
on
on
that
and
that
investment
for
this
milestone?
I,
don't
know
if
KC's
on
the
call
might
be
just
you
Nick
yeah.
B
I
can
give
a
quick
update.
In
short,
we
we've
assessed.
We
have
it
with
this
bunch
of
doctorates
floating
around,
but
I'm.
We
haven't
yet
got
any
of
'mentally
a
public
pool
request
which
we
need
to
do
soon.
We've
assessed
a
few
different
potential
ways
to
speed
up
the
development
of
writing
new
managers,
ulcers
or
new
providers
entirely
for
crossplane.
B
We
suspect
the
most
promising
one
is
going
to
be
to
take
a
look
at
building
an
abstraction
layer
for
terraform
providers
or
in
some
way
reusing
the
existing
code
of
terraform
providers.
I'm,
not
sure
if
it's
going
to
be
a
perfect
experience,
so
we
may
end
up
using
that
as
a
bootstrapping
process,
if
it's
possible
at
all.
Presumably
it
is
but
there's
other
projects
have
built
on
top
of
terraform,
but
we
may
use
that
as
a
bootstrapping
process
to
effectively
deliver.
B
There,
one
we're
investigating
building
on
top
of
terraform
somewhat
under
the
assumption
that
that
won't
be
there.
You
know
that
we
won't
build
on
terraform
for
a
month,
but
again
we
don't
know
yet.
We
need
to
learn
a
little
bit
more
and
we're
also
generating
code
natively,
we're
investigating
generating
code
written
for
the
current
patents
that
we
use
in
cosplay
today.
A
Also
Nick
thank
you
for
giving
that
update
on
that
one
yeah
and
that'll
be
really
interested
to
see
what
we
learned
from
that,
and
you
know
what,
through
the
lens
of
how
we
can
effectively
and
a
quality,
increase
the
scope
of
supported
resources
in
cross,
plane,
okay
and
then
another
area
that
it
was
a
huge
part
of
the
0.11
release,
was
infrastructure,
definition
in
composition
and
publishing
your
own
structure,
API,
etc.
Moffett.
Do
you
want
to
give
us
an
update
on
the
investments
that
we're
gonna,
make
it
0.12
in
that
area?.
D
Yeah
sure
so
we
have
the
default
and
enforced
composition,
features
that
will
make
it
to
0.12
there's
a
PR
open.
So
this
is
basically
in
the
infrastructure
definition.
You
will
be
able
to
refer
to
a
composition
to
be
default
in
case
there
is
no
selector
on
the
requirement
or
the
ported
composite
resource,
and
also
the
unforced
composition
feature
is
that
you
can
refer
to
a
composition
in
the
infrastructure.
D
Definition
and
crossplane
will
make
sure
all
instances
will
use
that
specific
composition,
which
would
enable
you
know,
like
you,
can
in
display
that
you
can
create
infrastructure
definition
and
also
the
composition
and
enforce
it.
Then
the
resulting
new
CRD
is
essentially
a
managed
resource
without
any
selection
or
something
so
that
is,
you
know
a
new
feature.
D
D
D
With
the
composition,
because,
like
the
number
of
layers
are
not
know
static,
you
can
have
like
you
know
five
different
layers
and
then
some
manage
resources
like
most
of
them
have
a
limit,
but
like
some
of
them
have
really,
you
know
shortened
limit
for
the
name.
For
example,
DC
service
account
is
like
30
characters
maximum.
A
D
Yeah
yeah
yeah:
you
have
to
do
that
manual
step,
so
I
think
I
mean
we
can
still
migrate
the
sample
stacks
without
having
that
automated,
but
it
won't
be.
You
know
much
useful.
If
you
have
the
you
know,
WordPress
flow
automated
somewhere,
so
I
would
I
would
prefer
that
we
get.
We
get
those
definitions
pre-installed
so
that
you
just
don't
really
want
to
really
have
to
care
about
them.
Yeah
that
makes
that.
A
Make
sense:
cool,
okay,
thanks
morphic
for
that
update
on
composition,
clear
0.12,
they're,
like
eye
on
these
you're,
that
twelve
project
board?
Here
we
have
a
couple
of
in
flight
designs
and
discussions
that
are
going
on
for
the
supports
like,
for
instance,
resource
dependency,
and
you
know
versioning
mechanism
for
ohm
as
well.
Does
anyone
on
the
call
one
to
give
a
quick
update
on
the
status
of
those
or
other
features
that
we
might
be
investing
in
for
implementation
in
Cross,
Plains
earwax
wells
or
is
it
does
speak
for
themselves?
Yeah.
E
So
I
can
add
some
few
details
about
yeah.
So
the
first
thing
I
think
we
may
want
to
release
meant
to
make
it
part
of
the
release,
is
the
reversion
design
for
the
components
alone,
so
the
PR
is
already
there
I.
Can
we
add
a
decoder
right,
there's
already
a
working
progress,
PR
poor
request
to
show
the
property
prototype
of
holiday
works?
Well,
one
small
differences.
We
decide
to
use
the
controller
reversion
in
this
implementation
because
more
like
ready,
so
you
guys
can
take
a
look
at
the
implementation
side.
A
E
The
second
issue
is
it's
not
very
Russian.
We
just
brought
this
idea
because
we
found
a
interesting
facts
inside
Alibaba,
so
there
are
some
team
they're
trying
to
defy
their
own
workloads
based
on
the
example
kubernetes
building
money
and
I
mean
kubernetes
default
workloads
or
based
on
some
other
project
like
open,
open
crews.
I
know
you
guys
know
about
Odin
Cruz
is
more
like
the
ones
the
version
of
kubernetes
workload
controllers.
So
anyway,
those
team
they're
trying
to
you
know
defy
user-facing
workloads
based
on
those
workloads.
E
So
it's
not
so
this
process,
like
the
separate
fields
from
existing
workloads
into
two
parts,
the
first
part
it
just
like,
maybe
sinkhole
workload
like
container
rights
workload
or
it's
maybe
just
as
simple
as
hot
spec
for
for
developers
raising
stuff.
They
only
accepted
all
the
other
fields
into,
for
example,
trades
on
scopes,
or
anything
like
that.
So
the
idea
that
they
want
to
provide
a
very
simple
interface
to
to
to
their
developers
and
that
actually
might
remind
us
more
like
so
right
now
they're
implementing
operators
for
that.
E
So
there
are
code
controllers
for
workloads
or
controls
for
trade.
So
this
actually
might
ask
you
think
about
is
it
is
something
like
a
pattern
of
decomposition
you
they're,
basically
like
divide
or
decompose
a
existing
CRT
into
multiple,
smaller
pieces.
I,
don't
know
if
it's
a
common
pattern
in
community
we're
not
sure
about
that,
but
this
these
things
are
not
about
myself
like
bring
up
this
discussion
of
you
guys
to
see
what
this
thing.
E
A
C
B
D
The
one
picture
perfect
hooks
I
think
this.
This
probably
won't
make
it
to
0.12,
but
I
will
try
to
get.
You
know
some
some
something
prototype
for
you
know
of
this
like
how
it
would
look
like
the
idea
here
in
in
this.
Is
that,
like
maybe,
if
we
can
integrate
well
with
packages,
then
we
can,
you
know,
make
sure.
Just
you
know,
providers
or
like
other
packages
that
are
installed
with
cross
playing,
can
use
the
same.
You
know
TLS
certificates
and
all
that
stuff.
A
Yeah
and
I
included
note
too,
but
that's
gonna
over
time
become
more
important
for
being
able
to
support
CRD
conversions.
You
know,
as
we
update
do
really.
Sup
dates
need
to
do
some
sort
of
created
a
migration,
etc
for
series
changing
and
getting
new
versions
and
every
thanks
to
the
conversion.
What
books
become
more
and
more
important
than.
C
A
A
standard
way
to
do
that
so
that
you
know
everyone
can
take
advantage
of
that
with
the
easy
framework
is
just
all
the
better
for
the
for
the
project
in
the
ecosystem,
cool
yeah,
so
exciting
stuff
in
0.12.
All
this,
this
community
and
this
team
works
pretty
hard
and
continues
making
really
cool
investments
to
move
the
project
in
the
in
the
future
set
forward.
So
looking
forward
to
0.12.
A
Does
anyone
have
let's,
let's
go
back
real,
quick
too
targeting
a
date
for
a
future
freezer,
the
release
etc?
So
you
know
we
normally
do
middle
of
the
month,
so
the
middle
of
the
month.
This
time
exactly
another
month
is
Monday
June
15th,
it
seems
like
there's
a
fair
amount
of
stuff
in
flight
and
I.
Don't
want
to
artificially.
A
A
Let's
pencil
that
in
and
you
know
we
could
be
somewhat
flexible,
but
that
doesn't
sound
like
a
bad
idea
to
me.
A
The
last
release
was
fun:
Dan,
like
dude,
separating
up
the
divide
and
conquer
approach,
for
you
know
all
their
release,
steps
and
stuff
like
that
that
was
that
was
fun
friends
working
together,
okay,
cool,
let's,
let's
move
on
then
to
the
community
topics.
So
first
one
we
had
here
on
the
agenda
is
that
I.
Think
two
weeks
ago,
or
almost
two
weeks
ago
we
had
our
cross
playing
Community
Day,
which
was
really
awesome.
We
had
some
fantastic
speakers.
A
You
know
from
a
lot
of
different
projects
and
focused
in
the
ecosystem.
Kelsey
Kelsey
Hightower's
keynote
was
great.
You
know.
Everyone's
participation
was
really
good
and
there's
some
really
good
and
interesting
concepts.
There
I
I
now
know
what
Amazon's
CD
cate-cate
says
and
I'm
actually
pretty
stoked
on
it.
That
was
a
really
cool
demo
for
Ben,
so
yeah.
This
is
great
all
around
we.
If
you
wanted
to
catch
up
with
some
more
of
the
content
there
I
got
a
link
to
the
live
stream
of
tweets
that
we
did.
A
That
was
basically
you
know,
links
and
information
about
all
the
contents
and
then
the
full
3/4
hour
or
whatever
recording
is
available.
Now,
at
this
link,
that
is,
that
does
still
require
registration
to
get
into
that,
but
the
on
the
we
partnered
with
zoom
to
host
the
event
for
technical
support
and
do
everything
and
they
that
team
is
working
through
the
post-processing.
A
Now
to
spice
up
all
the
speakers
to
remove
dead
air
to
get
make
sure
the
screen,
sharing
and
content
is
accurate
and
polished,
and
everything
like
that,
so
the
zoom
team
is
working
on
the
post-processing
and
when
that
is
complete,
then
we'll
be
able
to
publish
those
more
bite-sized,
focused
chunks
of
content
like
each
speaker
up
to
YouTube.
So
thank
you
for
everyone's
patience
as
we're
you're
waiting
for
that
post-processing
to
get
complete.
A
A
A
That
has
the
full
proposal
and
all
of
the
content
here
around
why
we
think
the
cross
plane
is
well
aligned
to
CN
CF
and
the
project
charter
mission,
history,
etc
and
stats,
and
all
that
so
that's
available
for
full
perusal
and
hit
these.
You
can
add
some
little
reactions
and
emotions,
emoticons
emojis
to
it
as
well.
If
you
want
to
we
also
last
week,
went
ahead
and
presented
to
the
special
interest
group
for
app
delivery.
Harry
was
so
kind
to
invite
us
to
come,
speak
there
and
give
us
a
venue
to
present.
A
So
the
there's,
a
bunch
of
helpful
links
here
in
the
agenda
document
for
the
slide
deck
that
we
presented
to
the
cig
and
the
meeting
notes
from
the
sig
as
well
as
well
as
the
the
video
recording.
So
if
you
wanted
to
catch
up
with
the
presentation
to
the
app
delivery
sig
along
with
all
the
questions
Q&A
session
and
everything
that
we
did,
these
are
some
easy
links
for
that.
A
So
then,
the
next
phase
of
the
CMC
F
submission
process
is
where
the
cig
assessment
phase
here
so
the
app
delivery
and
which
Harry
is
a
chair
of
will
be
going
through
the
assessment
process.
That's
sort
of
a
lightweight:
do
you
know
pre
due
diligence
and
then
they
will
make
their
recommendation
recommendation
to
the
technical,
Oversight
Committee.
A
So
if
there's
anything
that
is
needed
from
the
project
and
maintainer
team,
you
know
the
stake
will
will
ask
us
for
that
and
we're
happy
to
provide
anything,
that's
needed
or
clarify
any
questions
or
anything
that
comes
up
from
the
special
interest
group
as
needed,
so
just
reach
out
to
us,
Harry
or
since
you
know
a
lot
about
the
project.
You
can
answer
those
questions
on
your
own.
If
you
have
them
yeah.
E
So
I
think
the
review
has
already
started
and
alloys
will
act
at
the
contact
person
for
cross
pens.
So
if
you
have
any
question
regarding
to
the
progress,
you
can
ping
alloy
a
stone,
the
Salonika
directly
and
is
very
kind
and
there's
no
lot
of
detail
the
reviews
that
I
guess
you
know
everything
instantly
kind
of
snow,
so
I
guess
it
just
started,
there's
no
very
deep
dive
into
the
course
my
project
for
now
but
yeah.
A
That
sounds
good
here
and
then
yet
we
can
and
we're
available
for
anything
sue
if
it
boys
needs
it
news
anything
where
we're
happy
to
jump
in
and
get
response
this
right
away.
So
great,
alright
yeah,
that
was
fun.
There
was
a
that
sig
that
delivery
sig
is
full
of
kind
kind
and
nice
people,
so
that
was
that
was
a
fun
experience
going
to
talk
to
y'all.
A
C
Header
in
here,
yeah
I'm,
sorry
too
earlier,
adding
some
peers
from
the
provider
database.
But
so
we
have
couple
of
years
under
provider
a
tip
list
which,
like
needs
attention
towards
their
reviewing
an
ad
set
and
longer
that's
for
the
services
such
as
route,
53,
SQS
and
a
certificate
manager,
and
as
soon
as
they
should
be
ready
or
version.
C
B
A
Okay.
If
there
aren't
any
further
community
or
broad
topics
here,
then
we
can
move
into
the
optional
time
here
for
to
have
deeper
technical
discussions.
So
any
folks
that
want
to
drop
off
from
the
general
call
are
more
than
welcome
and
and
then
hashed
in
you
can
have
the
floor
here
for
your
cross
plane
packages,
refactoring,
update,
discussion,
cool.
F
You've,
probably
interacted
with
the
packaging
kind
of
format
a
little
bit
and
it
might
be
a
little
confusing
about
what
the
different
files
are
doing
and
kind
of
what's
happening
behind
the
scenes,
but
essentially
the
the
big
picture
is
that
crossplane
is
opinionated
about
what
types
of
things
can
be
installed
into
the
cluster
and
the
reasoning
for
that
is
so
you
don't
stomp
on
existing
CR
DS,
you
don't,
you
know,
have
containers
running
as
root.
You
don't
you
know
basically
violate
any
of
these
rules.
We
have
around
things
that
can
be
installed.
F
So
obviously
there
are
you
know:
various
template,
engines
and
packaging
for
kubernetes
manifests
I'm
in
the
ecosystem,
helm,
customized,
etc.
You
know
when
it
boils
down
to
it
pretty
much
everything
we're
installing
is
some
CR
DS
and
a
controller
or
multiple
controllers,
and
so
you
know
we
do
want
to
be
opinionated
in
some
ways
about
how
those
are
installed
and
we'd
also
like
to
make
the
installation
process
easier.
So
we
have
some
safeguards
where
you're
not
just
having
to
helm,
install
things
and
hope
it
doesn't
break
anything
because
there
aren't
really
many
safeguards
around
that.
F
So
basically,
that's
the
general
overview
for
this
conversation.
Where
we
want
community
feedback,
obviously,
because
both
contributors
and
users
kind
of
have
to
interact
with
this
in
in
a
variety
of
ways,
so
yeah
I,
guess
I'd
kind
of
open
the
floor
to
anyone
who
first
of
all
has
questions
and
second
of
all,
has
opinions
about
what
they
like
the
experience
to
be
or
if
they
think
you
know,
there
should
be
some
sort
of
packaging
or
there
shouldn't
I,
think
anything's
on
the
table
for
us
to
discuss
here.
You.
A
Know
I
think
a
note
on
that,
too.
Is
that
I
believe
that
the
design
doc
for
packages
has
stayed
up
to
date
as
well.
So
it
is
a
bit
heavy
in
terms
of
you
know
the
amount
of
content
in
here,
and
some
of
it
is
aspirational
as
well,
not
fully
implemented,
but
the
general
gist
of
you
know
what
files
go
into
a
package
like
what
is
the
format
of
it?
A
What
is
the
expectation
for
the
content
of
those
files
etc
is
captured
in
this
design
document
so
that
you
know
it's
not
a
completely
in
the
dark
format
that
we've
had
this.
This
design
document
here
that
you
know,
has
the
content,
but
might
not
be
necessarily
easy
to
parse
for
folks
that
are
new
to
the
idea
as
well.
F
Yeah
another
really
important
part
of
this
is
upgrade
of
controllers
and
Ciardi.
So
that's
what
that's
pretty
much
the
driving
thing
I'd
say
maybe
like
permissioning,
is
really
important
in
terms
of
our
back
that
these
things
are
given
as
well,
but
you
know
we
haven't
had
an
upgrade
story
so,
basically,
on
all
of
our
release.
Notes,
it's
like
yeah
we'd,
like
to
you
know,
make
it
easy
to
upgrade
to
newer
versions,
but
there
isn't
really
a
way
right
now.
F
C
This
could
hear
me
yeah
okay,
so
my
question
is:
is
this
the
proposal
for
packaging
cross
plane,
or
is
it
also
proposing
a
generic
solution
to
package
anything
you
want
it.
F
Would
be
a
packet?
Well,
that's
kind
of
the
second
part,
that's
a
little
bit
of
an
open
question,
but
it
would
be
packaging
things
installed
by
cross
plane
right,
so
Archer
I
know
you've
had
some
interaction
with
you
know,
installing
the
local
OAM
stuff
via
helm,
chart
verse
with
the
remote
installing
it
via
an
add-on,
but
basically
just
a
you
know,
specialized
type
of
package
and
there's
like
two
different
experiences.
There
one
may
be
more
familiar
one
bait,
maybe
a
little
more
streamlined
but
yeah.
F
C
B
Think
we
did
assess
it
at
some
point
and
I
believe.
The
reason
we
ended
up
going
with
our
own
packaging
format
was
that
it
seemed
that
scene
up
was
quite
broad
in
what
it
supported.
If
I
recall
correctly.
I
haven't
personally
deeply
looked
up
sort
of
just
fully
my
understanding
of
this,
but
my
understanding
is
that
see.
Nav
allows
you
to
package
basically
anything
using
cni
image
or
song
as
a
image
basically
to
to
deliver
things.
C
C
A
Yeah
it
takes
for
thanks
for
training
that
art,
sir.
What
one
thing
to
note,
too,
is
that
this
isn't
as
much
a
proposal
as
it
is
what's
already
out
there
from
across
then
this
is
full.
This
is
not
fully
implemented
in
terms
of
all
the
features
are
implemented,
but
this
is
exactly
how
you
know
in
cross
play
and
how
you
install
any
provider
like
provider,
you're,
a
sure
provider,
AWS
many,
the
sample,
stacks,
etc.
A
A
Yeah
yeah,
if
you
install
provider
Azure,
then
you
this
is
exactly
what
was
going
on
under
the
covers
there.
Okay.
C
A
You
know
one
one
aspect
of
the
of
the
design
here.
That's
aspirational.
That
I
think
has
a
fair
amount
of
value,
though,
is
this
whole
concept
around
like
CRD
instead
of
installations,
where,
instead
of
you
know
saying,
hey
I,
want
the
provider
Azure
package
to
be
installed
in
running
in
my
cross,
plane,
control,
plane,
you'd,
be
able
to
say
I
need
this
particular
CRD
like
I
need
the
cosmos,
DB
CRD,
or
something
like
that,
and
so
you
don't
have
to
know
where
it
lives.
A
Or
you
know
what
package
exists
or
what
package
that
package
depends
on
or
anything.
You
just
know
that
you
have
a
need
or
desire
for
creating
cosmos,
DB
instances
and
so
specifying
I
want
cosmo.
Deviances,
give
me
the
you
know
the
machinery
controllers,
dependencies,
etcetera
everything,
that's
needed
for
my
control
plan
to
be
able
to
provision
and
manage
cosmos,
DB
instances.
Then
you
know
this
package
fulfillment
dependency
resolution.
Installation
machinery
would
be
able
to
handle
that.
A
So
that's
something
that's
not
implemented
right
now,
but
from
the
very
beginning
of
this
design
was
was
part
of
part
of
the
at
the
aspirational
elements
of
it.
That
I
think
has
a
lot
of
value.
That's
that's
something!
That's
interesting!
That
I,
don't
think
that
sort
of
type
resolution
thing
I,
don't
think
exists
in
other
tools
in
the
ecosystem.
B
Yeah
I
think,
as
was
alluded
to
before
one
of
the
big
questions
that
we're
trying
to
answer
the
moment
is
what
the
scope
of
this
packaging
format
is.
I'm,
not
sure
we're
not
sure.
Yet
whether
we
are
getting
into
the
game
of
general
kubernetes
package
management
that
you
would
use
to
you
know,
potentially
other
projects
would
start
using
this
as
a
way
to
package
themselves
up
and
sort
of
support,
anything
in
communities
that
whether
this
is
going
to
be
something
that
we
spoke
more
specifically
to
just
extending
cosplayed.
F
You
either
have
to
have
you
know
things
packaged
up
in
a
way
that
declare
their
defendant
dependencies
in
a
uniform
way,
or
you
have
to
do
some
sort
of
analysis
of
you
know
an
arbitrary
thing
to
determine
where
you
know
what's
here:
DS
is
introducing
which
one
it
relies
on
and
that
sort
of
thing
so
there's
a
little
bit
of
conflict.
There
I
think
between
those
two
ideas.
It
might
be
an
interesting
thing
to
to
talk
about
further
they're,
probably
probably
in
a
different
discussion
than
this
one,
but.
A
F
There
are
a
whole
handful
of
issues
around
like
individual
pieces
of
the
current
packaging
system
that
are
more
like
you
know,
I
want
it
to
be
able
to
update,
or
you
know
the
install
that
gamal
is
dangerous
or
something
like
that.
So
there's
a
handful
of
those
I
think
after
we
have
some
additional
conversations
and
determine
if
we
either
are
just
going
to
like
keep
the
current
thing
and
do
some
revisions
or
go
down
a
new
path
and
I
definitely
think
would
be
appropriate
to
have
a
new
issue
that
is
like
you
know.
F
A
Got
it
and
that
could
be
an
artifact
of
three
or
further
discussions
that
we
have,
and
you
know,
be
able
to
kind
of
have
a
have
an
idea
about
a
direction
and
then
open
that
up
for
for
specific
feedback
that
that's
often
can
help
out
b2b
more
successful
or
productive
is
instead
of
open-ended.
You
know
solicitation
for
feedback
on
on
something
that
people
don't
have
a
lot
of
experience
with.
A
If
there's
more
of
a
concrete
proposal
that
you
know
you
can
solicit
feedback
for
that
people
can
weigh
in
on
they
understand
you
know:
what
is
what
does
it
scope
here?
What
are
what
is
the
goals?
You
know
what
is
some
of
the
details
about
it,
then
that
could
that
could
be
a
good
mechanism
for
soliciting
feedback.