►
From YouTube: 2022-06-16 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
june
16th
2022
cross
playing
community
meeting.
The
agenda
document
is
open
and
the
link
to
it
is
can
be
found
in
the
zoom
chat.
So
the
document
is
still
open
for
folks
to
add
any
items
that
they
want
to
go
over
here.
So
we'll
start
as
usual,
with
a
milestone,
checkup
and
making
progress
on
the
next
releases
and
versions
of
crossplane.
A
So
since
the
last
community
meeting,
we
haven't
needed
to
do
any
patch
releases,
so
we
don't
have
any
specific
releases
to
call
out
here.
In
this
section
we
are
in
the
middle
of
the
1.9
release
cycle.
I
think
kind
of
almost
yeah
directly
right
in
the
middle
of
it.
So
yeah
we
haven't
done
any
patches
in
the
past
two
weeks
or
no
bugs
came
up
since
the
patches.
A
We
were
talking
about
in
the
last
community
meeting
and
then
we're
about
a
month
left
halfway
through
the
cycle
here
until
the
the
1.9
release.
A
So
you
can
follow,
along
with
the
scheduled
releases
on
the
release,
calendar
and
the
links
here
in
the
found
in
the
agenda
document,
but
we're
working
towards
the
middle
of
july
about
one
month
from
now
to
target
the
1.9
release.
A
We
have
you
know
the
1.9
project
board
and
road
map
that
I
think
is
mostly
up
to
date.
I
think
there's
probably
some
efforts
from
folks
in
the
community
that
are
not
yet
captured
on
the
191.9
project
board.
So
if
folks
are
working
on
something
and
want
to
include
that
in
the
project
just
go
ahead
and
ping
me
and
I'll
be
happy
to
add
it
to
the
project.
A
If
that
may
require
like
organizational
permissions,
so
just
ping
me
and
I'll
be
happy
to
add
anything
to
the
to
the
milestone
that
we're
working
on
the
ones.
We
just
recently
sergeant
wrapped
up
a
couple
of
important
features
that
are
in
the
1.9
time
frame.
A
Here
there
are
these
two
in
the
done
column
we'll
go
into
some
more
details
about
those
later
on
in
the
agenda,
because
I
think
they
are
somewhat
important
so
we'll
get
into
that
a
little
bit
later,
and
then
there
is
a
community
effort.
Still
that
max
is
driving,
I
believe,
about
patching
from
common
data
sources.
That
is
both
that's
in
progress
right
now
from
both
the
design
and
api
changes
perspective,
as
well
as
the
implementation.
A
So
that's
going
to
require
a
bit
of
iteration
to
get
the
api
to
a
spot
that
we
are
feeling
good
about.
I'm
getting
it
right
on
the
first
time
here
since
we're
extending
the
you
know
any
extensions
to
the
crosstalk
cleaning
api
as
a
1.x,
you
know
mature
project.
We
want
to
be
very
conscious
about
how
we're
extending
the
api,
what
changes
we're
making
we
want
to
get
it
right.
So
definitely
thank
you
for
the
efforts
from
max,
as
well
as
the
patients
while
we're
working
through
and
talking
through.
A
Yes,
so
yeah,
if
you
know,
if
folks
want
to
speak
up
now
about
efforts,
they're,
they're,
they're,
working
on
1.9
and
then
also,
if
you
want
to
pay
me
later,
that's
fine
as
well,
something
I
just
thought
of
is
and
we'll
talk
about
this
in
more
detail
later
on.
But
we
do
have
some.
We
started
some
mentorship
projects
for
the
linux
foundation
just
a
couple
weeks
ago,
just
very
recently,
so
the
efforts
from
our
mentees
of
those
projects.
A
We
should
probably
get
those
onto
the
1.1.9
board,
also
so
that
we
have
some
more
visibility
on
those,
also
cool
anything
that
folks
want
to
bring
up
now
for
1.9
and
crossplane
core
functionality.
Before
we
move
on
to
providers.
A
All
right:
okay,
let's
let's
go
ahead
and
move
on
to
providers
then
so
I
think
something
definitely
to
call
out
here
and
zoom
is
once
again
in
my
way.
So
let
me
drag
this
to
another
screen
only
for
zoom
to
move
it
back
when
it
feels
like
it.
So
it's
definitely
something
to
call
out
here.
Is
the
provider
aws
release.
A
Okay,
there,
it
is
the
better
aws
release
for
0.28
came
out
less
than
a
week
ago,
but
there
has
been
a
regression
that
was
identified
within
that
release,
that
we
are
that
it's
probably
better,
it's
better
to
hold
off
from
installing
0.28.0.
A
Until
this
regression
is
fixed,
it
has
to
do
here's
the
issue
here.
It
has
to
do
with
the
imuser
resource
type
and
the
there
will
be
tags
that
continually
get
added
in
the
reconcile
loop
to
that
im
user
and
continues
essentially
duplicating
them
and
growing
that
list
of
tags.
A
So
this
is
a
regression
that
is
it's
unfortunate
and
you
know
I
think
we
should
do
maybe
a
bit
of
a
postmortem
on
you
know,
reflection
on
how
this
regression
or
this
behavior
got
introduced
and
what
we
can
do
as
a
community
to
to
prevent
that
from
happening
again
in
the
future.
But
this
is
being
worked
on.
I
believe
right
now-
and
you
know
this
will
be
patched
in
0.28
in
a
dot
one
patch
and
then
once
that
is
out
then
then
and
tested
a
little
bit.
A
Then
we'll
go
ahead
and
make
a
recommendation
for
provider
aws
users
to
move
to
the
new
dot
28
release
any
other
color
or
details.
To
add
about
that,
I
haven't
been
actively
working
or
involved
in
that
release
or
that
particular
issue
there.
But
I
that's
my
summary
of
an
understanding
of
it.
But
if
anybody
wants
to
add
more
details
do
feel
free.
A
All
right,
any
other
releases
of
providers
to
call
out
or
talk
about
right
now,.
A
All
right,
then,
I
wanted
to
call
out
one
new
provider
that
is
being
donated
to
the
cross,
plane,
contrib
organization,
so
there's
a
provider
jet
for
pallets.
That
is
pretty
much
in
its
entirety,
so
it
had
been
worked
on
in
another
organization
and
then
now
this
in
its
entirety,
is
being
submitted
to
crossplane
contrib
in
a
new
repository
for
provider
jet
pallets.
So
you
know
mostly,
I
took
a
review
pass
on
this
and
mostly
this
looks
fairly
complete
for
an
initial
implementation.
A
A
Oh
looks
like
this
got
closed
and
reopened.
Okay,
okay,
I
think
I
see
what's
going
on
there,
but
yeah,
so
not
a
lot
of
of
deep
implementation,
things
to
talk
about
with
this
provider
in
terms
of
the
feedback
but
more
build
and
structural
stuff,
so
yeah
the
we'll
be
driving
this
to
its
first
release,
as
as
the
the
latest
new
provider
within
the
ecosystem
in
the
crosslinking
triple
org
yuri.
Do
you
want
to
catch
us
up
on
some
of
these
provider?
Terraform
things?
B
Yeah
sure
so
just
to
discuss
them
because
they
were
mentioned
in
a
couple
of
previous
meetings,
so
I
started
to
work
today
on
the
single
signal
handling
issue.
Basically,
the
problem
is
sat
like
whenever
we
update
a
provider
terraform
with
a.
A
B
Version
supports
are
getting
deleted
and
if
the
reform
is
active
within
a
port
at
that
point
in
time,
then
the
state
is
getting
locked
right
so
and
to
the
observing
workspace
in.
A
B
Unusable
state
out
of
that,
so
I
started
to
begin
and
I
realized
that
actually
we
are
setting
the
local
network
reconciliation
loop
and
then
I
came
to
realizations
that
actually
tear
from
plan
actively
locking
the
state,
even
on
like
on
terraform
terraform
plan,
really
the
only
operation
right.
So
this
is
very
simple
pr,
which
is
a
disabled
location
mechanism
for
read-only
plan,
and
there
are
like
upstream
terraform
discussions
linked
in
this
pr.
B
But
the
thing
is
that
like
it
should
mitigate
most
of
the
cases
of
the
lock
now
so
like
yeah.
I
remember
when
I
was
working
for
some
experiments
on
a
provider.
B
B
So
now
I
understand
why,
because
the
plan
was
working
as
well,
so
basically
every
every
cycle,
it
was
locked
and
obviously
spawned
like
a
in
most
cases
of
pot
recreation,
this
kind
of
unusable
state
after
this
pr
it
will
be
better
and
yeah
next
step
will
be
advanced
signal
handling,
which
will
also
properly
catch
the
case
when
actually
terraform
applies
running
this
in
a
boat
so
like
it
will,
it
should
wait
for
for
a
terraform
application,
but
it's
going
to
be
more
tricky
because
there
are
multiple
layers
in
it
like
a
grace
period,
injection
and
actual
handling.
B
So
but
I
is
that
that's
for
this
one
diff
plan
and
bob
active
contributor
to
provider
from
he.
He
was
very
interested
in
this
one.
Unfortunately
he's
not,
he
didn't
join
today,
but
I
already
think
with
him
asynchronously
in
slack,
and
we
discussed
the
proposal
that
so
it's
a
it's
another
link
in
the
document
jared.
Can
you
please
open
it?
Yeah.
B
Yeah,
thank
you
so
standard
terraform
product
error
from
debugging,
so
like
a
it's,
pretty
tricky
from
a
consumption
standpoint
and
development
standpoint
as
well,
because
currently
it
exposes
like
an
okay
in
k17
stream.
Only
an
error,
but
this
is
very
it
just
like.
Has
its
standard
error
part,
it's
very
short
chunk
of
what
is
happening
and
the
whole
context
is
hidden
so
very
frequently
to
actually
understand
what
is
happening
on
terraform
level.
B
You
need
to
get
into
the
part
find
the
workspace
with
a
associated
unique
identifier
copy
it,
because
you
need,
like
you,
know,
to
not
to
recrea
to
catch
the
state
and
not
so
like
avoid
the
situation
when
your
into
the
workspace
and
controller
will
recreate
it
on
the
next
reconciliation
loop,
all
that
stuff
and
then
manually
run
terraform
from
the
vision,
support
and
understand,
what's
happening,
as
you
can
imagine,
it's
totally
inconvenient
and
brutal
scenario,
but
currently
the
only
way
to
get
there
to
actually
isolate
the
problem
and
potentially
the
situation.
B
What
is
happening
with
your
terraform
code
within
a
within
a
controller?
So
that's
why
we
discussed
what
we
we
can
do.
C
B
Faces
the
same
problem
as
me:
so
potentially
we
can
extend
the
workspace
crd
status
and
include
the
logs
there
and
it
might
be
ugly,
but
you
at
least
like
set
the
directions
there,
and
it's
obvious
welcome
to
the
discussion.
If
you
guys
you
if
you
have
any
experience
like
with
us
on
ideas
where
to
put
this
kind
of
looks
it's
basically
like
this.
You
know
ctr
from
cli
stream
log,
but
it
can
be
maybe
generic
case
when
you're
dealing
with
visa
class
within
the
controllers.
B
I
definitely
would
appreciate
any
ideas,
so
I've
seen
this
stuff
before
when
I
was
in
my
previous
company,
we
were
using
a
rancher,
experimental,
terraform
controller
to
drive
the
terraform
kubernetes
way
it
never
reached
any
like
maturity,
but
they
were
like.
You
know,
to
not
expose
like
a
huge
stream
of
plain
text.
They
at
least
like
include
it
into
base64
and
put
it
into
the
part
of
the
cd
status.
So
we
might
try
the
same
approach.
So
that's
a
update
on
a
pro
editor
from
stuff.
A
Cool
yuri
thanks
for
sharing
some
of
those
details
and
and
updates
on
on
that
particular
provider
and
and
the
collaboration
that's
going
on
at
repo.
Also
thanks
a
lot
all
right.
So
then
I
think
that's
everything
for
providers
section
unless
folks
want
to
add
anything
else,
feel
free
to
interrupt
me,
but
I'll
keep
moving
on
here.
A
So
the
just
a
quick
couple
of
links
from
recent
content
like
blogs,
presentations,
live
streams,
etc.
So
there's
a
couple
of
of
summaries
that
came
out
of
kubecon
eu
that
were
mentioned
in
crossplane,
so
I
put
links
to
both
the
both
of
those
ones
in
there.
A
So
you
catch
up
with
everything
that
was
going
on
in
valencia,
as
well
as
some
of
the
details
about
crossplane
as
well,
that
is
coming
from
the
greater
ecosystem,
and
then
victor
was
speaking
at
get
ops
days
recently.
Victor.
B
C
A
Awesome
that
sounds
good
victor,
because
I'm
sure
that
would
be
very
interesting
for
folks
to
watch
and
get
access
to
if
it's
been
published.
So
thanks
for
following
up
with
that,
all
right,
sweet,
so
yeah-
and
you
know
if
anybody
else
has
other
content
or
your
blogs
or
anything
that
they've
published,
feel
free
to
add
it
to
the
edge
of
the
dock
as
a
link
here
as
well.
So
it's
got
more
visibility
all
right.
A
So
I
was
talking
earlier
about
the
the
mentorship
programs
that
we
have
started
that
are
underway
for
the
foundation's
mentor
program
for
the
summer
term.
Here
so
they're
we're
in
week,
two
right
now
and
so
we're
starting
to
work
with
the
mentees
and
get
into
some
of
the
foundational
knowledge,
and
you
know,
background
prerequisite
stuff.
So
they
can
then
start
on
the
projects
that
they're
going
to
be
working
on.
So
rika
and
parole
are
two,
the
two
mentees
that
are
working
on
crossplane
this
summer.
A
I
think
here
at
the
community
meeting
sereka,
if
you
want
to
say
hi
to
folks
in
the
community
here
you're
more
than
more
than
welcome
to
do
so
and
introduce
yourself
a
little
bit.
If,
if
you
want
to
do
that.
A
Oh,
maybe
you
don't.
We
don't
have
audio
right
now
for
for
rika,
but
both
she
and
pro
will
be
around
the
community
this
this
whole
summer.
As
a
start,
we're
hoping
that
they'll
stick
around
for
the
in
the
community
and
be
contributing
after
that,
as
well
of
course,
but
yeah
I
feel.
Hopefully,
everyone
will
make
them
feel
welcome,
and
you
know
pitch
in
as
well
for
for
helping
them
get
acclimated
and
growing
within
the
cross
plane
project
too.
A
So
the
two
projects
here
are
they're,
both
like
qa
sort
of
focus
like
quality
bars
for
pull
requests.
Essentially,
so
ricco
is
working
on
one
where,
if
there's
breaking
changes
in
the
crd
pro
request
will
notify
you
of
that.
So
we
can
take
the
appropriate
steps
to
do
like
release,
notes
or
maybe
redesign
the
api,
or
do
something
so
that
we
can
deal
with
breaking
changes
and
crds
and
make
sure
that
we're
doing
the
right
steps
there
if
they
come
up.
A
So
some
automation
around
that
will
be
very,
very
helpful
and
then
parole
is
working
on
making
sure
that
package
polls
from
private
registries
will
continue
working
in
our
high
quality.
We've
had
a
couple
of
things
over
the
past-
I
don't
know
maybe
a
year
or
so,
where
private
polls,
first
in
certain
environments,
stopped
working
or
had
some
had
some
potential
regressions
in
them
for
various
reasons.
A
So
staying
on
top
of
you
know
that
scenario,
as
you
know,
consistently
working
and
being
verified
will
be
really
helpful
for
the
community
as
well.
A
lot
of
people
rely
on
private
registries
to
store
their
you
know,
platform,
configurations
and
custom
providers
and
all
that
sort
of
stuff.
A
So
it
is
definitely
an
important
scenario
that
we
want
to
make
sure
it
stays
at
high
quality,
so
welcome
to
the
community,
rick
and
pool
for
you
know
both
of
your
efforts,
you're
going
to
be
helping
out
the
project
with
this
summer
and
we're
definitely
excited
to
have
you.
A
The
kubecon
call
for
proposals
from
north
america
for
detroit
was
that
was
completed.
A
If
you
have
one
that
you
want
to
share
with
people
feel
free
to
add
to
the
agenda
document
a
link
to
your
proposal
right
here,
so
that
we
can
check
it
out
and
get
excited
about
it
together.
A
If
you
want
to
keep
that
to
yourself
until
you
find
out
if
you're
accepted
or
not
that's
totally
reasonable,
and
you
know
we're
looking
forward
to
hearing
about
all
the
different
talks
that
gets
accepted
or
will
be
part
of
cuba,
north
america.
I
think
the
latest
number
that
I
heard
about
kubecon
europe
and
valencia,
like
including
you
know
more
indirect,
mentions
and
references
and
dives
into
crossplane.
The
last
last
number.
I
heard
that
there
was
14
different
talks
and
tracks,
etc
that
were
talking
about
prospering
and
valencia.
A
So
that's
a
whole
lot
of
stuff
going
on
for
crossplane
and
then
you
know
demonstrating
that
we're
continuing
to
grow
and
expand
their
breadth
and
our
scope
within
the
ecosystem.
A
So
you
know
I'm
hoping
to
do
something
similar
for
people
in
north
america,
and
you
know
we're
happy
to
give
people
a
chance
to
share
what
they're
working
on
and
what
they're,
what
they're
submitting
for
that
too,
so
feel
free
to
add
that
to
the
document.
If
you
want
to
also.
A
All
right,
so,
let's
move
on
then
to
looks
like
we
added
something
to
the
agenda
here
for
provider
aws
issue.
I
don't
know
if
I
am
super
familiar
with
this
one.
So,
let's
see
it
looks
like
you
went
ahead
and
added
this
here.
This
is,
it
looks
like
it's
from
you
on
the
agenda
and
here
as
well.
Do
you
want
to
give
a
little
quick
background
context
on
this
one
here,
yeah.
D
So
I
have
a
customer
who
is
trying
to
deploy
database
resources
into
the
china
region,
and
you
know
some
of
the
basic
ones
like
s3
and
all
that
works.
But
if
you
are
trying
to
use
like
a
global
scoped,
you
know
resources
like
im
or
rap53.
D
They
don't
work,
at
least
until
that
the
pr
was
merged,
and
then,
after
that
pl
is
merged.
We
can
actually
get
it
to
deploy
using
the
configuration.
You
know
switzerland
in
this
in
this
comment
that
I
made
so
my
question
I
don't
know
I
guess
my
question
to
the
community
is:
is
this
the
you
know
expected
configuration
that
we
want
people
in
china
to
use?
So
you
know,
if
you
know
people
in
china
wants
to
use
or
deploy
like.
I
am
resources
right.
D
They
don't
have
to
use
this
type
of
configuration
right,
whereas
in
you
know
global
and
just
just
database
partitions,
you
don't
have
to
do
that.
So
I
just
want
to
kind
of
get
clarification
on
that
you
know.
Is
this
expected?
Is
this
something
that
we
should
change
any
opinions.
A
Yeah
a
really
good
question
and
I
appreciate
the
example
they
are
providing
here
as
well
to
to
give
more
context
about
a
solution
that
seems
to
be
working
but
you're.
Wanting
broader
guidance
of
if
this
is
the
recommended
approach.
A
The
floor
to
folks
to
see
if
they
have
some
opinions
on
if
this
is
this,
is
the
recommended
approach
or
not
here,
maybe
aaron,
maybe
victor
plenty
of
other
folks
here.
Does
anyone
have
an
opinion
that
they
want
to
share
about
this
approach?.
B
The
only
recent
things
that,
when
I
faced
the
bus
partition,
was
during
stabilization
of
one
of
the
resources
and
in
an
associated
terraform
example.
The
partition
was
read
by
a
data
resource,
so
just
a
high-level
idea
that
when
we
implement
observe
only
resources,
it
might
contribute
to
the
overall
solution
of
this
problem.
So
we
could
retrieve
this
partition
dynamically.
D
Yeah,
so
I
was
looking
at
the
code
as
well
and
you
can
actually
do
it,
but
within
the
code
you
it's
actually
setting
the
region
explicitly
and
that's
where
the
program
actually
is
coming
in.
So
you
know
I
can
make
a
pr
and
try
to
you
know,
make
it
so
that
this
doesn't
happen,
but
I
I
guess
I
don't
know
what
the
intention
of
these
you
know
these
changes
are
made
right
like
I
do
we
want.
D
B
Yeah
I
just
wanted
to
understand
properly.
Does
it
mean
that
currently,
the
standard
that
will
partition
is
hardcoded.
D
Is
a
global,
constant,
that's
being
used
to
provide
this
iem
android
53
resources.
A
Yeah
so
this
this
brings
up
a
pretty
good
question
and
I
don't
I
don't
have
myself
an
an
answer
about
there
being
if
there
is
a
better
way
to
do
this
than
what
you're
doing
right
now
so
yeah.
Hopefully
we
can
follow
up
on
this
issue
with
folks
that
might
be
more
familiar
with
it
to
see
if
there's
deeper
or
further
recommendations
with
this
or
if
you
know
what
you've
got
here
is,
is
the
the
right,
the
the
the
recommended
approach
for
right
now.
D
Okay,
do
you
know
what
I
have
like
the
names
of
people
that
I
can
maybe
kind
of
take
it
offline
with.
A
Yeah
christopher
hart
here
so
harkery,
it
would
be
probably
a
good
resource
that
could
help
out
with
that.
I
bet.
A
Yeah
I'd
feel
free
to
just
mention
him
on
this
issue,
so
we
can,
you
know,
have
that.
Have
that
visible
for
other
folks,
too
yeah
awesome
yeah,
thanks
for
bringing
that
up.
D
A
Okay
and
then
I
wanted
to
dive
in
also
to
a
little
bit
of
functionality
that
was
added
to
crossplane
core
recently.
So,
sir
again,
if
you
are
online,
if
you
want
to
give
us
a
quick
overview
of
some
of
this
functionality,
that
was
in
fairly
high
demand
from
folks
that
were
running
kind
of
blocked
on
adopting
crossland
without
this
functionality.
C
Yeah,
thank
you.
Thank
you
jared.
Actually,
this
pr
addresses
two
issues
in
the
cross
plane
run
time.
The
one
of
them
is
the
related
to
circular
dependencies.
C
When
we
try
to
use
the
references,
we
cannot
recreation
fail
span
using
the
having
circular
dependencies
using
these
references,
and
another
issue
is
that
the
resolving
references
only
once
this
fear
addresses
them
by
adding
new
reference
resolution
and
result
policies
and
the
result
policies
are
the
always
and
if
not
present,
and
it's
related
as
you
can
think
that
the
resolving
references
only
once
if
you
set
the
always
policy
for
the
references,
this
reference
will
be
resolved
for
every
reconcile
loop
and
the
resolution
policy
is
related
with
the
circular
dependence
issue
and
we
have
two
choices,
and
one
of
them
is
the
required
and
another
one
is
optional.
C
If
the
required
show
chose
is
chosen,
which
means
that
reconcile
will
fail
if
the
reference
cannot
be
resolved,
this
is
actually
the
current
behavior
and
we
are
adding
a
new
api,
and
if
this
optional
choice
will
be
selected,
that
means
this
reference
will
be
tried
to
chosen
it's
right
to
resolving.
And,
however,
if
we
cannot
do
this,
this
reconciliation
loop
will
be
continued.
So
this
is
the
idea
of
this
prg
and
it
opens
it
provides
a
new
api
for
the
references
these
apis
are
about
the
policies.
C
And
yeah,
I
also
you
can
also
find
a
few
examples
about
the
pr
description:
how
can
they,
how
can
we
use
them
and
how
can
we
apply
and
resolve
issues.
A
Yeah
thanks
for
those
details,
they're
gonna,
you
know,
as
I'm
saying
that
I
think
this
is
really
important,
because
it
it
was,
you
know,
quite
quite
literally,
blocking
some
people
from
being
able
to
proceed
with
adopting
crossplane
and
be
using
it
successfully.
So
I'm
glad
we
got
this
fixed
in,
and
so
something
to
note
too
is
that
this
would
need
to
be
consumed
from
various
providers
that
they
want
to
pick
up
this
functionality.
A
So
sergeant
has
a
pr
here
which
basically
gets
that
latest
fix
that
he
put
into
crossplane
runtime
and
then
generates
the
you
know.
It
essentially
adds
these
policies
in
this
functionality
to
all
the
existing
resources.
So
that's
that's
an
explicit
thing
that
would
need
to
be
done
for
the
providers
that
want
to
consume
this
functionality.
Sergey.
A
Can
you
comment
on
any
sort
of
the
like
api
compatibility
or
you
know
upgrade
or
you
know
any
changes
that
need
to
be
provided,
as
consumers
need
to
be
aware
of
with
with
these
additional
changes?
There's
no
there's
no
compatibility
like
breaking
changes,
but
this
is
not
a
breaking
change
right.
It's
additive.
C
Yes,
yes,
actually,
yes,
we
are
protecting
the
current
behavior
if
the
user
can
will
not
set
these
policies,
so
this
is
not
pretty
cheap,
as
you
said
that
if
the,
if
user
tries
to
use
the
policies
again,
this
will
only
change
the
resolution
and
result
policies,
so
the
general
pipeline
will
not
be
affected
again,
however,
and
also
will
not
be
affected.
The
current
behavior
of
this
reconciles
and
resources.
A
Awesome
great
so
there's
not
a
you
know:
like
state
provider,
aws
aws
picks
up
oops
wrong.
One
aw
at
provider,
aws
picks
up
this,
this
new
functionality,
and
then
you
know
the
next
release
goes
out
there.
Will
the
folks
won't
need
to
take
any
steps
to
to
deal
with
this
change
like
they
will?
If
they,
you
know,
want
to
use
the
policy
willing
to
add
some.
You
know
configuration
to
do
that,
but
otherwise,
though
it'll
be,
it
should
be
no
issues
with
upgrading
or
migrating
right.
D
Thank
you
yeah.
I
actually
tested
this
like
I
built
my
own,
you
know
crossbane
on
provider
aws
and
everything
and
it
works
really
well.
So
thank
you
so
much
for
this.
Thank.
A
A
Fantastic
sweet,
so
jesse
added
a
a
link
here
to
to
the
the
proposal
that
he
submitted
to
to
kubecon
north
america.
So
folks
can
check
that
out.
Some
exciting,
exciting
stuff
on
you
know:
supply
chain,
verification
for
packages
and
such
so
thanks
for
adding
that
jesse.
A
Hopefully
that
one
gets
selected
and
we
can,
we
can
hear
that
talk
in
in
detroit
yeah.
A
Right
on
cool,
so
yeah,
so
I
think
that's
everything
that
was
on
the
agenda
so
far
do.
Does
anybody
want
to
bring
up
anything
else
then,
before
we
adjourn
for
the
week.
A
All
right:
well,
then,
we
can
go
ahead
and
adjourn
here
thanks
everybody
for
coming
to
discuss
all
the
the
various
topics
on
the
agenda
and
we'll
keep
working
towards
the
1.9
release
and
getting
those
other
providers
released,
also
and
good
to
see
everybody
today.