►
From YouTube: 2022-08-25 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
august
25th
2022
cross,
plane
community
meeting.
I
know
there's
a
number
of
folks,
mostly
the
istanbul
people
that
are
doing
a
get
together
and
a
team
event
thing,
and
so
they
won't.
They
won't
join
here.
So
we're
missing
a
little
bit
of
attendees
from
that
today,
but
thanks
everybody
else
for
attending
and
we'll
go
through
the
agenda
document
everything's
recorded,
so
folks
can
catch
up
later
on.
So
I
wanted
to
start
checking
in
on
milestones.
A
First,
as
usual,
I
saw
a
number
of
commits,
or
things
merged
into
or
backboarded
into,
the
release
branches
like
1.9
1.8
1.7,
the
currently
some
three
current
supported
releases.
So
I
wanted
to
see
if
there
was
also
a
plan
or
an
intent
with
those
merges
to
then
do
a
patch
release
to
get
those
outs.
Some
of
them
were
docs
changes,
but
this
one,
the
most
recent
one
here
was
for
supporting
package
pulls
from
harbor.
Specifically
that
looked
like
that
was
not
to
go
to
change.
A
So
I
wanted
to
check
to
see
if
we
were
planning
on
doing
a
patch
release.
Dan
was
driving
that
one-
and
I
don't
think
dan
is
here
today,
so
I'm
not
sure
if
we
have
an
answer
to
that,
but
I'm
kind
of
assuming
there's
a
patch
release
coming
since
we
backported
a
code
change
into
a
release
branch,
it
wouldn't
make
sense
just
to
backboard
it
not
release
it.
So
I'm
assuming.
B
A
So
then,
there's
the
1.10
release,
which
we
are
also
making
progress
on
you-
can
follow,
along
with
all
of
the
progress
and
things
that
are
in
scope
here
on
the
crossplane
releases
board.
We
still
we're
we're,
maybe
halfway
or
so
into
the
release
cycle.
We
still
have
a
month
and
a
half
or
almost
two
months
until
the
release.
So
there's
still
plenty
of
time
here.
A
Probably
one
of
the
biggest
things
to
note
and
to
call
out
in
terms
of
progress
is
that
the
long-standing
pr
to
for
the
design
of
supporting
patching
from
common
data
sources
by
max
been
driving
that
and
nick
has
been
providing
a
lot
of
feedback
that
pr
the
design
has
been
approved
now.
So
I'm
expecting,
then,
because
that's
a
highly
highly
requested
feature,
so
I'm
expecting
then
for
progress
on
the
implementation
to
be
made
because
max
had
a
kind
of
parallel
implementation,
pr
alongside
the
design.
A
So
now
that
the
design
is
approved
and
finalized,
I
expect
max
to
probably
make
fairly
quick
progress
on
the
implementation
of
it.
So
I'm
I'm
expecting
this
to
be
in
the
1.10
release
at
this
point,
since
we
have
almost
two
months
left,
the
design
is
approved-
and
I
know
max
is
fairly
motivated
on
this
feature
as
well.
So
I
would
be
surprised
if
it's
not
included
in
1.10.
A
Obviously,
that's
not
a
guarantee,
but
there's
clear
progress
here
and
max
is
motivated
so
that
one,
I
think,
is
really
exciting
and
there's
a
lot
of
demand
for
it.
So
I
know
a
lot
of
folks
are
waiting
on
that
one.
It
will
be
in
its
first
release.
It
will
be
behind
an
alpha
feature
flag.
So
you'll
have
to
take
a
specific
step
to
enable
that
feature
in
the
main
cross,
plane
deployments,
and
then
there
will
certainly
be,
I
think,
a
good
opportunity
for
feedback
on
that
feature.
A
The
design
for
it
is,
it
underwent
a
lot
of
discussion,
but
you
know
once
it
gets
out
there
and
people
start
using
it
then
we'll
have
some
feedback
on
the
real
world
and
see
if
there's
some
use
cases
we
missed
and
such
so
feedback
from
using
that
alpha
feature
will
be
very
useful
in
the
1.10
time
frame.
A
There
is,
let's
see
what
else
to
bring
up
here.
I
think
everything
that's
in
progress
here
is
on
the
board
and
updated,
so
there's
a
fair
amount
of
things
in
flight
right
now.
Let's
see
what
to
call
out,
I
think
that
constant
custom,
compositions
or
composition
functions
that's
still
in
progress,
but
it's
progress
on
that
is
going
to
kind
of
ramp
back
up
again,
I've
taken
a
little
bit
of
a
break
for
it,
while
we're
having
a
number
of
competing
priorities
right
now.
A
I
don't
know
I'm
not
going
to
make
any
promises
on
that
one
being
included
in
1.10,
but
progress
will
be
ramping
back
up
on
it
and
you'll
see
more
you'll,
see
that
see
more
attraction
on
that
one
again,
and
obviously
lots
of
good
opportunities
for
feedback
in
that
as
well.
A
A
I
think
another
one,
that's
definitely
top
of
mind
for
me,
and
I
kind
of
reconfirmed
a
little
bit
that
this
is
a
priority
as
well
is
you
know,
we've
had
this
composition,
revision
functionality,
where
you
can
consciously
roll
out
updates
to
your
compositions
across
your
environments.
It's
still
in
an
alpha
state
right
now,
and
there
are
some
issues
with
it.
A
So
in
order
to
mature
that
to
beta
level
and
ready
for
folks
to
start
using
in
production,
there's
a
number
of
things
that
we'll
be
followed
up
on,
and
I
think
that
this
is
a
priority
to
be
able
to
get
this
in
the
hands
of
people
and
be
able
to
you
know
kind
of
be
able
to
have
more
control
about
how
they
update
their
platforms
over
time.
I
think
that's
really
important,
and
so
that
is
a
priority
for
the
project
as
well
and
we'll
be
getting
some
attention
too.
A
So
I've
got
that
one
at
the
top
of
the
backlog
and
then
observe
only
resources
is
something
that's
important,
as
well,
or
at
least
extension
points
for
it.
So
that's
near
the
top
of
the
backlog
in
my
mind
as
well
too,.
B
But
if
what
is
oh
go
ahead
now,
what
is
observe
only
crossband
resources?
I
don't
think.
A
Yeah,
if
yeah
the
best
way
to
describe
that,
if
you're
already
familiar
with
terraform,
I
think
they're,
like
data
sources,
I
think,
is
what
they're
called
terraform.
I'm
not
a
very
experienced
terraform
person
at
all,
but
basically
it's
the
concept
of
being
able
to
bring
in
an
external
resource
like
a
database
or
a
cluster
or
whatever
it
may
be,
into
purview
of
crossplane,
where
it's
reconciling
in
the
sense
that
it's
doing
observe
on
it.
It's
getting
data
from
it,
it's
bringing
into
the
environment,
but
it's
not,
it
doesn't
have
right
access
to.
A
It
won't
make
any
changes
to
the
resource,
so
you're,
basically
bringing
it
into
the
control
plane.
So
then
other
resources
can
refer
to
it
or
get
information
from
it
or
get
the
status
from
it
or
whatever
it
may
be.
So
it's
basically
being
able
to
have
the
the
crossband
to
know
about
the
existence
and
get
information
about
a
resource
but
not
be
able
to
make
changes
to
it.
I
think
that
hotly
can
highly
require
requested
as
well.
That's
a
really
popular
feature.
A
Okay,
so
yeah,
so
that's
making
lots
of
progress
on
1.10.
Things
are
getting
getting
moved
across
the
board
there
and
folks
are
more
than
welcome
to
weigh
in
on
priority,
and
you
know
things
that
they'd
like
to
see
as
we
go
throughout
the
in
between
community
meetings.
Also,
let's
see
so
I
didn't
to
spend
much
time
on
this
section
yet
for
recent
provider
provider
releases
and
such
I
know
that
there
was
a
patch
release
in
provider
aws
so
christopher.
A
If
you
want
to
talk
to
that
one
real,
quick
and
then
we'll
see
if
there's
other
recent
provider
releases
also.
C
Yeah
we
we
implemented
with
the
last
release
flow
logs
in
vpcs,
and
there
was
an
issue
with
self-introduced
override
fields,
so
we
skipped
the
fields
in
the
generation
and
afterwards
yeah
there
were
not
was
not
part
of
pre-create.
So
there
was
an
issue
if
you're,
using
this
fields
from
the
custom,
structs
and
yeah,
I'm
currently
on
the
next
release.
So
I
guess
in
one
hour
something
like
this:
we
see
the
next
release
in
provider
aws.
Normally
we
want
to
cut
this
yesterday,
but
there
was
one
open
pr.
C
We
emerged.
I
guess
10
minutes
ago
for
enhancing
eks
things,
that
you
can
reconfigure
security,
kms
stuff
for
the
eks
cluster
that
you
can.
After
the
creation
you
can
add
the
kms
keys
to
the
cluster
and
we've
re-merged
this,
and
now
we
cut
the
release.
I
guess
the
new
branch
I
created
and
now
the
ci
jobs
are
running.
C
So
I
guess
I
need
one
hour
roundabout
to
make
all
the
checks
and
publish
the
release.
C
There
will
be
a
big
change
for
the
glue
space,
so
everything
related
to
glue.
There
was
a
big
pr
drive
by
deutsche
bahn
and
there's
a
few
braking
changes
inside
for
fields,
but
we
will
make
this
yeah
visible
in
the
release.
Notes.
A
Will
there
be
some
some
sort
of
migration
steps
there
christopher
about
how
to.
C
Absorb
migration,
yeah
yeah,
we,
we
will
publish
the
migration
steps
if
you're,
currently
using
the
things.
A
Awesome
christopher,
thank
you
for
paying
attention
to
that
man
other
other
recent
releases
from
providers.
I
didn't
really
took
a
look
at
it,
so
anybody
know
I'll
stop
their
head
of
other
provider
releases.
A
Okay,
cool
and
there's
some
other
things
in
the
community
we'll
talk
about
later
on
in
the
agenda,
all
right
great.
So
let's
keep
on
moving
and
making
progress
here.
So,
let's
move
on
to
the
community
topics
section.
So,
as
always,
we
have
our
content
section
first,
so
a
couple
of
blog
posts
and
presentations
etc.
As
usual,
and
I
feel
like
this
came
out
on
the
day
of
the
community
meeting
last
week
or
last
time,
but
I
don't
think
it
was
like
before
the
community
meeting
happened.
A
So
here
is,
I
think,
a
super
useful
and
fairly
technically
in-depth
article
that
nick
wrote
about
all
the
work
we've
been
doing
within
the
kubernetes
control
plane
and
within
upstream
kubernetes
as
well
to
be
able
to
handle
situations
where
crossfit
providers
are
huge
and
they've
got
hundreds
and
hundreds
of
thousands
of
you
know,
custom
resource
definitions
and
the
kubernetes
api
control
plane
has
not
handled
that.
Well,
so
we've
made
a
number
of
improvements
there.
A
B
A
Yeah,
a
lot
of
the
stuff
that
nick
writes
is
very
good,
so
yeah
thanks
for
validating
that.
It's
not
just
me
that
thinks
that
so
we
got
a
couple
other
this
one's
a
first
first
look
from
someone
from
the
community,
that's
coming
from
terraform
and
checking
out
crossplane
and
giving
their
opinions
on
it.
Some
good
insight
there,
which
is
really
really
good.
This
is
worth
noting.
A
Now
I
think
too,
because
there's
been
a
long
standing
issue
where
the
object
model
of
crossplane
did
not
play
well
with
argo
cd,
and
you
know,
owner
references
and
and
relationships
between
entities
of
composed
resources
and
the
composite
resources
and
claims
and
all
that
sort
of
stuff.
A
So
the
argo
cd
has
enabled
some
new
functionality
in
terms
of
tracking
annotations,
to
be
able
to
understand
relationships
between
objects,
and
so
nate
has
updated
his
blog
post
here
about
how
to
enable
that
and
how
to
get
crossplay
and
inargo
to
play
well
together
and
then
nate
is
also
driving
in
addition
to
the
docs,
the
official
crosstalk
documentation
to
be
able
to
explain
this
as
well
as
well,
beyond
just
a
blog
post.
A
A
We
use
it
internally,
it
upbounds
also,
so
it's
good
to
see
this
happen
and
then
suicide
did
a
post
as
well
about
combining
some
of
their
product
line
with
ross
plain,
and
so
that's
definitely
an
interesting
look
as
well,
so
that
link
is
available
for
you
all
cool,
so
any
other
blog
posts
or
presentations
or
videos
or
anything
folks
are
more
than
welcome
to
add
us
that
list.
A
So
we
get
some
visibility
there
as
well,
and
the
cross
plain
twitter
account
is
always
happy
to
retweet
and
get
some
visibility
for
stuff
that
folks
are
doing
within
the
community
and
associated
with
cross
planes,
so
feel
free
to
reach
out
to
us
and
we'll
always,
you
know,
make
some
noise
about
stuff.
You
guys
are
doing
too
all
right,
so
linux
foundation
mentorship
summer
term
projects
last
we're
in
the
last
week
of
that
of
this
now
of
summer
term.
Final
evaluations
are
on
august
31st.
I
think
so.
A
These
two
mentees
rahika
and
parole.
I
think
pearl's,
on
the
call
today
too
so
we'll
let
her
speak
to
her
project
when
we
get
there.
But
the
r2
mentees
have
been
working
really
hard
on
these
two
projects
and
we've
been
giving
updates
on
them
in
each
community
meeting.
While
we've
been
going
through
the
summer
term,
there,
and
so
rika
is
finishing
up
a
unit
test
for
being
able
to
evaluate
breaking
changes
in
crds.
A
The
functionality
we
focused
on
was
was
was
detecting
fields
from
being
being
removed
from
one
version
to
another,
so
she's
wrapping
up
a
unit
test
there
to
take
that
functionality
and
then
we'll
be
able
to
expand
it
in
the
future
to
have
more
rules
and
more
knowledge
of
breaking
changes
and
then
also
kind
of
get
that
integrated
into
prs
across
providers
also,
and
then
parole
is,
I
believe,
on
the
call
so
parole.
A
Are
you
available
to
go
ahead
and
give
us
an
update
of
the
progress
that
you've
made
and
what
you
want
to
finish
up
in
your
last
week
on
your
project.
D
Yeah
sure
I
can
do
that
so
am
I
audible
just
checking.
D
Yeah
so
as
of
now,
we
have
made
some
of
progress
in
adding
logging
statements
to
the
already
existing
tests
for
provider
upgrades
and
focusing
on
the
main
period
of
the
project,
that
is
to
add
tests
for
pulling
private
packages
from
registries
that
are
supported
by
class
cross
plane.
We
have
the
tests
written
and
the
pr
is
up
and
we
are
working
on
having
it
tested
against
an
automated
workflow.
D
There
are
some
failures
in
that
which
we
are
currently
working
to
get
rid
of,
but
that
aside,
the
test
and
the
logging
statements
are
already
in
place.
The
workflow
is
in
place,
but
just
that
we
need
to
check
what
went
wrong
with
the
workflow
stuff.
A
Yeah
fantastic,
and
so
I
think
this
is,
and
what
we
would
like
to
do
here
at
in
the
last
week
is
get
this
unit
test
working
here.
So
we
have
a
full
end-to-end
flow
running
on
a
regular
basis.
That's
testing
the
latest
crossbane
builds
and
making
sure
that
it
can
still
download
packages
from
private
registries.
We
have.
The
google
artifact
registry
is
the
first
implementation
here
and
so
being
able
to
we've
had
a
number
of
regressions
over
time
with
not
being
able
to
connect
and
access
private
repositories.
A
So
that's
a
really
important
one
for
us
to
prioritize
and
make
sure
we're
catching
any
regressions
very
early
on
before
the
broader
community
finds
them.
So
yeah
parole's
done
a
great
job
on
this.
I'm
really
excited
to
get
this
to
a
good,
finishing
point
here.
So
we'll
finish
up
getting
that
workflow
debugged
and
this
test
running
successfully
and
yeah.
It's
been
a
great
time
working
with
both
parole
and
rohika
this
summer
and
so
excited
to
get
that
finished
up.
A
Oh,
this
is
in
cross
plain
slash
test.
Yeah,
we
have
a
number
of
yeah
of
workflows.
There
that's
run
on
a
periodic
basis.
You
can
see
them
all
in
the
github
workflows
file
folder
there,
where
you
know
testing
the
providers
like
aws,
gcp
and
azure
all
can
upgrade
from
the
last
version
to
the
latest
in
in
their
main
branches
and
and
then
we
got
this
new
private
package
pull
one
and
then
we
also
have
crossplane
itself
being
able
to
upgrade
to
the
latest
version
so
yeah.
A
So
it's
it's
good
to
and
pearl's
done
things
beyond
just
that
private
package
test
there
she's
been
helping
us
debug
and
get
some
reliability
and
logging
and
observability
into
the
other
integration
tests
as
well.
In
this
repo.
B
A
Cool
so
kubecon
north
america
over
in
detroit,
nothing
really
new
to
mention
I
I
did
now
find
at
least
it's
on
the
schedule
site
that
you
can
link
to
search
results.
So
now
I
have
updated
that
link
of
everything
that
mentions
crossplane
is
directly
in
the
search
here,
so
you
can
find
it
more
easily.
A
You
will
also
note
that
everything
that
mentions
crossplane
is
checked
marked
and
on
my
schedule
so
we'll
see
if
I
can
hit
all
of
these,
there
might
be
some
conflicts,
but
I
ambitiously
would
like
to
see
every
single
one
of
these
and
looking
forward
to
seeing
folks
in
detroit
as
well,
if
you're
able
to
make
it.
A
All
right,
so
nick
has
spent
some
time
and
nick's,
not
here
right
yeah,
so
nick
has
spent
some
time
recently
on
some
repository
project,
maintenance,
hygiene,
sort
of
related
stuff.
So
a
number
of
things
that
we've
done
first
one,
I
think
probably
the
most
important
one-
is
that
we
have
added
a
new
role
to
the
governance
of
the
project.
A
So,
in
addition
to
you
know,
steering
comedian
maintainers,
we've
also
added
a
new
reviewers
role,
so
this
reviewer's
role
essentially
is
a
way
to
expand
the
number
of
folks
that
we
have
reviewing
prs.
So
we
can
improve
the
efficiency
of
pull,
requests,
getting
feedback
and
getting
to
a
good
state.
A
So
reviewers,
essentially
we'll
you
know
we'll
have
we
have
some
automation
to
assign
a
reviewer
to
each
pull
request
that
is
opened
in
core
crossplane,
at
least
for
now,
and
so
those
reviewers
will
provide
feedback,
take
a
look
and
kind
of
help
lighten
the
load
from
from
the
maintainers
right
now.
So
there
are,
I
think,
some
more
opportunities
for
folks
to
become
reviewers
within,
like
from
the
broader
community-
and
I
like
this
because
it's
a
not
only
is
it
helping.
A
You
know
improve
our
pr
review
efficiency,
but
it
is
also
a
path
to
becoming
a
maintainer
on
core
cross
plane
as
well,
where
you
can,
you
know,
start
giving
some
good
feedback,
having
good
insights
into
the
architecture,
helping
and
enabling
new
contributors
and
then
become
eventually
a
maintainer
yourself
also.
So
I
think
this
is
a
cool
opportunity
and,
if
folks
are
interested
in
becoming
a
reviewer
and
core
cross,
plane
then
feel
free
to
reach
out
to
me
and
to
nick
and
we'll
we'll
talk
to
you
about
that.
A
The
other
hygiene
related
thing
to
note
is
that
we
did
add
a
bot
for
looking
at
stale
issues.
So
that's
something
that
we've
we've
seen
a
little
bit
now
on
other
projects.
I'm
involved
in
we've
eventually
done
this
there
too,
where,
if
there's
old
issues
that
are
out
of
scope,
you
know
they
haven't
been
touched
in
at
least
90
days
or
no
comments,
no
interactions
with
them
at
all.
Then
the
bot
will
mark
them
as
stale
and
make
a
comment
on
it.
A
And
then,
at
that
point
you
have
a
folks
have
an
opportunity
to
comment,
and
you
know
ask
the
the
stillbot
to
you
know
to
not
not
close
it
out
if
you
think
there's
a
week
in
between
when
it
gets
marked
as
still
and
when
it
gets
closed.
A
So
if
you
have
issues
that
are
still
important
to
you
and
you
get
a
notification
that
has
been
marked
to
still,
you
know
go
ahead
and
comment
on
the
issue
and
you
know
give
us
some
some
reasoning
for
you
know
if
you
still
want
that
issue
to
exist.
If
you
think
it's
still
think
it's
a
priority
any
of
that
sort
of
stuff.
So
it's
kind
of
a
bit
of
a
forcing
function
to
continue
to
get
eyes
on
on
issues
as
they're
as
they're,
maybe
languishing
or
not
getting
any
attention
from
the
community.
C
Is
this
also
something
we
can
introduce
and
provide
aws,
for
example,
because
we
have
very
old
issues
running
there,
and
I
don't
know
if
they're
really
up
to
date
or
not.
A
Yeah,
I
think
so
christopher,
because
I
think
you
know
there
may
be
some
like
enabling
at
the
organizational
level
to
give
it
permissions
first,
but
then
it's
a
simple
configuration
file
that
gets
checked
into
the
repository,
so
you
can
see
the
config
we
have
in
corecrossplane
and
then
just
basically
copy
that,
and
so
we
can
add
that
into
the
new
provider's
repos
that
we
want
so
yeah.
A
I
think
that's
great,
if
you,
you
know,
as
a
maintainer
on
provider
aws,
if
you
think
that's
good
for
that
repository
though,
and
you
think
that
would
help
the
the
community
for
that
particular
repo.
Then
yeah
absolutely
go
ahead
and
add
that
and
if
you
need
any
help
with
getting
like
organizational
setup
of
like
if
the
steel
bot
isn't
yet
set
up
there,
then
I
can
help
out
with
that
too.
Man.
A
Great
dude
awesome,
yeah,
so
yeah
you
see
things
so
a
few
things
are
ramping
back
up
again,
and
you
know
like
a
big
part
of
that
is
organizing
our
project
and
making
sure
that
we're
focusing
on
the
most
important
things
so
we'll
continue
to
see
that
of
how
can
we
make
the
project
more
efficient?
How
can
we
help
contributors?
A
You
know
be
enabled
to
be
you
know,
building
and
and
pushing
the
project
forward,
so
we'll
keep
doing
that
as
we're
going
through
the
the
milestones
the
rest
of
the
year
christopher
this
is
this
is
absolutely
you,
my
friend.
Let
us
I
think
you
demoed
this,
maybe
a
couple
I.
B
C
Source
the
first
version,
so
it's
the
very
basic
implementation
of
it.
So,
for
example,
if
you
click
on
examples,
if
you
want,
you
can
have
a
look,
and
I
don't
know
pick
one
rds
yeah
and
I
know
sorry,
it's
it's
it's
the
example.
Can
you
go
back
to
the
root?
It's
only
the
the
final
example.
Can
you
go
to
the
root.
C
Sorry
go
to
com
positions,
got
it
correct
and
now
pick
one
of
them
I'll.
C
Yeah
and
you
can
click
the
generate
yummy,
a
short
recap,
so
in
general
you
can
generate
now
compositions
out
of
crds
from
a
provider.
So
in
line
five,
for
example,
you
can
see
this
is
a
crd
from
a
provider
aws
in
this
example,
and
we
have
a
few
options
to
configure,
for
example,
connection
secret
keys.
We
want
to
have
in
the
claims,
for
example,
which
are
the
default
compositions,
a
few
labeling
things
and
which
are
our
group
names
versions
and
purposes,
for
example,
and
then
everything
is
generated.
C
So
if
you
go
back,
you
can
see
the
composition
is
completely
generated
and
the
definition
is
completely
auto
generated
out
of
a
crd
from
provider
and
there
are
a
few
other
options
for
patching,
etc,
etc.
So
overriding
the
external
name
or
not,
for
example,
patching
things,
patching
labels
annotations
whatever
there's
a
lot
of
things
in
this
repository
and
yeah.
A
Yeah
there
we
go
battle
tested,
do
you
is
there?
What
was
it
in
the
generate
file?
Yes,
is
this
schema
for
this
documented
so
far,
so
you
so
have
an
idea
of
all
the
fields
you
can
set
in
their
values
and
stuff.
B
C
A
C
Okay,
cool
cool;
yes,
there's
a
lot
of
things,
so,
for
example,
one
more
example:
can
you
go
back
and
open
the
cams
key
for
example,
then
you
can.
C
And
the
interesting
part
now
is:
we
want
to
enforce,
for
example,
here
override
fields,
and
we
want
to
have
the
enable
key
rotation
enable
true,
and
if
we
set
also
ignore
true,
it's
the
the
our
our
customers
or
our
tenants
are
unable
to
change
this
field
because
for
governance
reasons
we
want
to
have
this
field
enforced,
so
you
can
enforcing
fields
without
tenants
can
change
it.
C
A
So
does
that
make
it
immutable
christopher
or
is
that
like
it
doesn't
expose
it
in
the
claim.
C
So,
on
the
on,
it's
not
exposed
that
the
tenants
can
change
it,
but
we
have
also
a
version
that
it's
really
immutable
with
cubano
policies
in
the
background.
Okay,
so
normally
our
generation
is
a
little
bit
more.
We
have
also
cubano
policies
normally,
but
we
need
to
clean
up
a
little
bit
things
if
we
really
can
open
source
it,
because
there's
a
lot
of
company
yeah.
C
It
takes
a
little
bit
time
to
open
source
the
things
and
clean
up
that
everyone
can
use
it
and
we're
really
happy
to
see
a
merch
request
or
pull
requests
here.
If,
if
other
folks
wants
to
use
this
because
we
can
learn
from
each
other,
what
are
the
interesting
parts
in
the
composition,
generation.
A
Yeah,
fantastic
and
understanding
like
what
are
the
use
cases
or
what
you
know,
what
are
the
what's
missing
functionality
that
people
want
to
see
as
well
so
yeah,
I
I
can
imagine
like
community
rallying
around
this
and
adding
some
new
stuff
to
it
for
sure.
B
I
just
noticed
cuddle
tests
how
they
work.
Are
you
generating
cattle
for
the
compositions
or.
C
Either
at
the
moment,
we're
not
really
generating
them,
but
what
what
we're
trying
to
achieve
in
the
tests
is
we
applying
the
compositions
and
our
examples?
And
then
we
are
trying
to
check
the
managed
resources
generated
in
the
cluster
if
they.
So
if
we
have
our
composition
claims
and
then
we
have
yeah
create
them
in
the
cluster,
and
we
check
then
afterwards
in
an
assert
file.
C
B
Yeah,
so
at
the
moment
you
need
to
populate
this
test.
Suite
manually
is
that.
C
B
C
So
if
jared
can
go
one
back,
there
is
other
folder
for
the
assert
files.
For
example,
can
you
go
to
resource
yes
and
there's
a
third
yama?
So
currently
this
is
handwritten
yes,
but
yeah.
We
want
to
try
also
generating
the
things,
because,
if,
if
we
create
a
claim,
we
want
to
check
if
all
our
patches
are
on
the
on
the
on
the
resources
from
the
providers
are
as
expected.
A
Awesome
yeah
so
thanks
again
christopher
for
driving
this
and
then
you
know
like
doing
that.
Developments
within
you
know
your
employer,
but
then
donating
it
to
the
community
in
the
ecosystem.
So
we
have
it
to
share
and
rally
around
that's
super
cool
and
really
appreciate
it
for
sure
awesome.
Awesome
man,
I'm
going
to
skip
over
fuss
testing
because
we
kind
of
talked
about
it
a
little
bit
last
week
but
dick
muafik
is,
is
the
the
owner
and
driver
of
that
so
I'll
sync
up.
D
A
Waffek
offline
about
that
one,
oh
and
then
that
appears
to
be
the
full
agenda
here.
Any
other
agenda
items
that
folks
want
to
bring
up
discuss,
get
some
opinions
on.
A
C
C
I
don't
know
in
the
test
mode
that
we
can
create
a
vpc,
for
example,
and
the
provider
for
us
generates
a
vpc
id
that
we
can
use
the
vpc
id
then
to
to
reference
this
to
other
resources,
because
at
the
moment
our
tests
are
like
lack
of
features.
I
would
say,
because
if
you,
if
you
need
a
real
id
from
a
resource
yeah,
you
can't
test
this
without
creating
the
resource
in
the
in
the
cloud
provider,
for
example
yeah.
C
So
if,
if,
if
there
is
someone
in
the
community,
I'm
currently
working
on
something
like
this,
this
would
be
really
helpful
for
us,
because
all
resources
we
have
today
with
reference
each
other-
I
don't
know
and
not
gateway
with
the
subnet
group.
We
have
not
real
unit
tests
at
the
moment
because
we
can't
do
anything
without
the
live
environment.
Then.
A
Wait
so
christopher
so
you're,
saying
like
like
a
test
sort
of
mode
for
the
the
provider
where
it
would
like
like
create
a
vpc
object
in
the
kubernetes,
the
kubernetes
api,
but
not
reconcile
that
then,
with
like
the
live
environment,.
B
B
C
Yes,
yes,
we
tried,
but
it's
really
really
difficult,
because
it
depends
a
little
bit
on
how
our
endpoint
configurations
are
working
on
the
provider
level.
There
are
a
lot
of
issues
at
the
moment
if
you
want
to
use
a
local
stack
and
fair
enough.
The
local
stacks
thing
there's
also
not
all
resource
cover
we're
currently
using
for
eks
setup,
so
yeah.
A
B
Has
nothing
to
do
with
virtualization,
it's
just
intercepting
the
api
calls
right
and
then
able
to
reproduce
it
back
so
use
something
like
honey,
moon
or
something
like
a
gogo
link
tooling,
which
was
able
to
intercept
the
api
calls
and
basically
dump
all
of
them
into
json,
and
then
repeat
them
like
in
a
consistent
manner.
So
I
was
able
basically
basically,
like
you
know,
to
nci
cuts
external
integration
point
off
and
mock
it
out
with
this
thing.
So,
potentially,
you
could
like
recreate
it
with
a
edible
s
record.
C
That
might
an
interesting
projector,
yeah,
okay,
cool
yeah-
if,
if
nobody
yeah,
if
nobody
in
the
community
has
something
like
this,
we
will
definitely
invest
a
few
hours
of
our
time
to
see
if
it
is
possible
because
it
could
helps
our
testing
with
all
the
resources
we
have
because
a
little
bit
background
in
our
setup,
we
have
more
than
300
resources
rendered
for
our
ecash
setup,
and
it's
very
difficult
today
to
find
out
if
the
update
of
a
provider
will
break
something
without
the
tests.
C
A
Cool
yeah
definitely
a
cool
idea,
and
I
see
the
value
of
it
as
well,
especially
as
the
scope
of
you
know.
Effective
resources
within
your
environment
grows
too
so
yeah,
like
I
haven't,
heard
anybody
working
on
that.
But
I,
like
yuri's
idea
of
you,
know
kind
of
like
the
recorded
playback.
You
know
api
request
thing.
I've
seen
that
in
other
type
of
tests
as
well
for
other
projects.
So
that's
a
good
idea
and
yeah.
Definitely
you
know
whatever
you
do
find
in
christopher.
A
You
have
please
do
share
with
the
community,
because
that
could
be
valuable,
too
cool
yeah
thanks,
awesome,
well,
sweet!
So
yeah.
I
think
that's
everything.
So
I
think
we
can
go
ahead
and
adjourn,
but
as
always
great
to
see
everybody
and
then
we'll
keep
sinking
a
sinking
async
on
slack
together
too
see
you
all
in
two
weeks.
The
next
meeting
too.