►
From YouTube: 2020-12-07 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
looks
good
all
right
well
welcome
to
cross
playing
community
meeting.
It
is
december
7th
2020
and
we
are
about
a
week
out
from
or
exactly
a
week
out
from
the
v
1.0
release,
which
is
obviously
a
really
big
milestone
for
a
cross
plane.
So
we're
going
to
be
looking
at
a
few
things
to
just
kind
of
round
out
that
release
today.
So
I'm
going
to
go
ahead
and
share
my
screen
and
share
the
agenda
doc
here,
please
feel
free
to
add
your
name
to
the
agenda
doc.
A
If
you
haven't
already.
I
think
I
got
a
number
of
folks
already
before
we
got
started
and
also
reminding
you
that
this
meeting
is
governed
by
the
cncf
community
standards.
So
please
do
be
excellent
to
each
other
and
respectful
of
one
another,
all
right.
So
we'll
start
off
here,
as
we
always
do
with
the
milestone
checkup.
So
before
we
start
recording
I'll,
go
and
mention
again
since
we
didn't
get
on
the
recording.
A
Phil
mentioned
this
blog
post,
which
is
really
awesome
that
he
put
together
and
we
post
about
last
week
a
pretty
extensive
blog
post
that
details
a
lot
of
the
stuff
that
has
happened
with
crossplane
over
the
year,
as
we
just
turned
two
years
old
phil.
Since
you
were
chatting
before
we
started
the
recording.
Did
you
wanna
mention
anything
for
posterity
here.
B
Oh
yeah,
just
really
great
to
see
kind
of
the
community
coming
together.
Tons
of
you
know,
progress
on
the
providers
and
the
code
gen,
and
you
know
I've
even
you
know,
with
kind
of
like
cd
tapes
on
top,
so
you
know
really
great
effort
and
that's
all
built
around
kind
of
the
v10
core.
That's
about
to
be
released
next
monday,
like
damn,
was
mentioning
so
yeah.
It's
just
a
super,
exciting
time
to
be
part
of
the
project
and
a
lot,
a
lot
of
good
momentum
and
stuff.
So
yeah.
A
For
sure
yeah,
it
was
definitely
fun
for
me
to
scroll
through
this
and
remember
all
the
awesome
things
that
happened
and
yeah
take
a
look
at
some
of
the
stuff,
so
definitely
give
that
a
read.
Next,
let's
go
ahead
and
take
a
look
at
our
road
map
here,
and
I
can't
remember
this
is
up
to
date.
Right
phil.
I
think
you,
you
merged
an
update
recently
for
this
yeah.
B
There
are
a
couple
things
that
are
probably
going
to
get
pushed
out
until
after
1
0,
like
bi-directional
packaging.
I
think
we
did
get
claim,
update
propagation
or
that's
on
its
way
support.
I
think
we're
trying
to
get
that,
but
I
don't
know
if
you
have
an
update
on
that
from
nick
and
then
1609.
I
think
we're
probably
going
to
find,
if
that's
not
an
easy,
add
I'm
going
into
to
100
and
that
shouldn't
really
impact
the
apis
validation.
B
Web
books
is
also
likely
to
slip
out
of
10.
nick's.
Actually
just
got
a
new
house,
so
he's
been
like
kind
of
moving
and
then
there's
been
some
other
things.
So
it's
kind
of
been
you
know
some
of
these
like
lower
priority
things.
I
might
be
keeping
being.
C
B
Out
but
we'll
see
how
that
progresses
over
the
next
week.
A
Cool
yeah.
That
sounds
good.
One
thing:
that's
not
here
that
I
think
and-
and
I
would
defer
to
nick
to
say
this
for
sure.
I
think
that
we
will
support
requesting
additional
r
back,
as
in
your
cross-plane
packages,
which
is
especially
useful
for
some
of
the
new
providers
they're
trying
to
do
some
in-cluster
stuff,
because
by
default
you
only
get
r
back
for
things
that
you
install
so
right.
A
If
you
create
provider
aws,
you
install
your
aws
crds,
and
your
controller
in
that
package
is
automatically
given
r
back
for
that.
However,
if
you
want
to,
you
know,
create
deployments
or
manage
some
crds
from
another
package,
or
something
like
that,
then
you're
gonna
need
our
back
on
those
as
well.
So
I
believe
nick
has
that
in
flight
now
he
was
chatting
about
that
at
the
end
of
last
week.
A
So
keep
your
eyes
open
for
a
pr
on
that,
and
I
guess
along
what
we
were
just
looking
at
there
on
the
road
map.
We
can
take
a
quick
look
at
the
project
board
for
folks
who
aren't
familiar.
The
project
board
here
is
where
we
track
the
actual
issues
and
prs
for.
What's
going
into
a
given
release,
note
that
this
is
at
the
project
level,
not
the
crossplane
crossplane
repo.
So
if
you
go
to
the
crosswind
oregon
project,
you'll
find
this
and
we're
making
pretty
good
progress
here.
A
I
think
some
of
this
can
probably
be
updated,
and
some
of
these
are
more
I'm
kind
of
like
meta
tracking
issues
as
well.
I
don't
think
unless,
if
someone
wants
to
talk
about
anything
specifically
here,
I
don't
think
that
there's
too
much
to
talk
about.
That's
not
gonna,
be
mentioned
later
in
open
prs.
A
All
right
also,
when
we
looked
at
the
road
map
a
bit
ago,
we
saw
some
of
the
the
focus
areas
so
I'll
just
kind
of
briefly
go
over
what
we're
doing
in
each
of
these,
and
also
defer
to
folks
who
are
working
on
them
more
specifically
to
provide
more
information
when
we
say
hardening
and
stabilization.
A
A
lot
of
that
is
around
the
composition
and
package
manager,
kind
of
model,
you'll
notice
that
last
week
in
master,
we
removed
v1
alpha
1
apis
for
those
that
we
were
serving
both
v1
beta,
1
and
v1.
Alpha
1.,
so
v1
alpha
ones
will
be
not
present
in
the
1.0
release,
but
we
should
have
v1
apis
of
those.
A
So
the
goal
there
is
that
folks
go
ahead
and
move
to
the
v1
apis
and
we
will
maintain
stabilization
and
backwards.
Compatibility
on
those
we've
also
started
to
increase
our
testing
story,
which
I
may
chat
about
a
little
bit
later.
But
overall,
just
you
know
getting
some
production.
Readiness
on
different
cross-plain
components.
A
Next
is
composition.
I
think
phil
already
mentioned
most
the
main
points
on
that.
I
know
later
on.
I
added
simon's
pr
here,
which
is
about
requiring
different
or
the
spec
field
in
xrds,
so
we'll
talk
about
that
a
little
bit
later,
I
guess,
nick
or
phil
would
probably
be
the
most
appropriate
to
check
in
and
see.
If
there's
any
additional
things
you
think
we
should
mention
about
composition
here.
C
But
the
way
the
claim
propagation
is
in,
it's
gonna,
be
in
the
1.0.
A
B
I
mean,
I
guess
I
will
kind
of
mention
just
one
experimental
thing
relating
to
composition,
so
this
is
really
going
to
be
more
of
like
a
beyond
100
thing,
but
we're
exploring
custom
compositions
for
use
with
like
cdks
the
sidecar
and
so
we're
basically
focused
on
getting
kind
of
like
the
core
composition.
B
A
Yeah,
absolutely
thanks
for
calling
that
out.
That's
a
good
point,
along
with
some
of
the
custom
composition,
stuff,
we've
also
kind
of
looked
at
a
function
package
model.
So
right
now
we
have
configuration
and
provider
packages
and
we're
kind
of
thinking
about
a
new
package
type
that
would
potentially
basically
expose
an
endpoint
and
be
called
by
various
basically
scaffold
operators
in
in
core
cross
plane.
So
custom
composition
is
a
great
example
of
that
right.
So
you
have
some
logic
that
you
bundled
up
into
a
container.
A
You
install
that
into
cross
plane
and
it's
given
the
appropriate
permissions
and
then
cross-plane
calls
out
to
that
to
perform
compositions.
Potentially
you
can
also
see
other
applicability
for
things
like
day.
Two
operations,
if
you
wanted
to
you,
know,
provide
your
custom
logic
in
whatever
language
you
want
for
a
you
know,
database
migration
or
something
like
that.
So
if
you
have
thoughts
on
that,
there's
a
lot
of
conversations
going
on
around
that
right
now.
A
A
Go
ahead
and
link
the
pr
here,
so
this
is
move
office,
custom,
compositions,
design,
doc.
If
you
scroll
down
here,
we
have
a
thread
going
right
here
that
describes
some
of
these
different
approaches.
So
if
you
have
thoughts
I'll
go
ahead
and
just
link
to
that
specifically,
please
feel
free
to
drop
those
in
there
we'll
make
sure
those
are
considered
in
the
design.
A
One
that's
currently
open
right
now
has
to
do
with
the
default
registry
name
which
I'll
talk
about
later
on,
but
pretty
much
we're
mostly
good
to
go
on
that
front.
Please
do
let
me
know
if
you'd
like
to
test
out
specific
features
of
that
for
your
use
case,
so
that
we
can.
You
know,
make
sure
that
we
have
a
good
coverage
of
everything.
Folks
want
to
do
provider
acceleration
I'll
go
ahead,
and
let
casey
chat
about
that,
maybe
for
a
little
bit
and
then
move
off
it
as
well.
D
Yeah
I'll
start
with
aso,
that's
basically
on
hold,
while
matt
is
out
for
the
month
of
december,
but
he
pre-recorded
a
talk
to
play
back
in
community
day.
So
we'll
have
that
and
also
be
talking
about
what
we're
doing
on
terraform.
On
the
terraform
side,
I
have
resources
generated.
D
I
have
a
small
exclusion
list
for
resources
that
have
duplicate
nested
object
names,
because
right
now
we
need
to
do
something
a
little
bit
more
complex
to
detect,
which
of
those
are
actually
structurally
identical
and
and
which
ones
are
actually
different
and
rename
the
ones
that
are
different
so
but
there's
491
that
we're
generating
schemas
for
and
and
then
also
we
have
encoders
for
all
those
that
go
from
the
crd
type
to
the
terraform
type
and
so
for
the
terraform
provider
runtime,
which
I
wrote
earlier
for
the
gcp
prototype.
D
We
kind
of
need
three
pieces
to
have
a
fully
working
provider
and
those
are
you
know,
encoding,
terraform
structures
from
cross
point,
crds
and
decoding
from
terraform
back
to
crossplane,
and
then
comparison
functions
that
we
use
to
implement
updates,
and
so
we
have
the
encode.
And
then
we
need
the
decode
and
the
comparison
to
kind
of
bring
all
these.
D
You
know
400
some
odd
resources
into
a
reconciler,
I'm
pausing
a
little
bit
on
that
to
focus
more
end
to
end
to
build
out
the
other
parts
of
the
provider
like
how
we
you
know,
do
the
external
connector
and
so
forth,
just
to
get
feedback
on
the
whole
experience
of
using
one
of
these
generator
providers.
D
D
So
take
a
couple:
resources
build
out
all
those
other
parts
that
we
need
for
a
complete
reconciler,
and
then
you
know
put
that
out
there
for
people
to
start
taking
a
look
at
and
then
you
know
and
then
we'll
get
back
to
decoding
and
in
comparison,
a
code
generation
to
kind
of
kind
of
finish
off
the
the
alpha
of
of
this
project
and
yeah
I'll
hand
it
over
to
move
off
to
talk
about
ack.
C
Yeah
sure
so
hdk
just
got
a
big
overall
in
terms
of
refactoring.
We
changed
a
few
things
about
crosstalk
pipeline
and
I've
been
trying
to
get
it
work
again,
and
that's
done
so
we're
back
on
track.
As
of
now.
I
think
we
only
have
the
sagemaker
api
not
generated
for
crossplane
and
I'm
planning
to
get
it
like
done
in
the
next
days
and
then
go
back
to
making
update
work
in
a
way
that
will
you
know,
reconcile
the
resources.
C
As
you
know,
most
of
the
ack
resources
right
now
do
not
support
updating
it's
create
and
delete
because
of
the
few
unsupported
functions
that
we
have
like
is
up
to
date
and
also,
like
you
know
many
of
ack
resources.
They
just
don't
have
update
at
all,
supported
in
sdk2,
so
yeah,
I
think
at
the
end
of
the
week
we
should
have
like
right
now
we
have
like
54
or
something
in
terms
of
like
number
of
resources.
A
Nice
yeah
sounds
awesome,
well
cool
yeah.
Thanks
for
that
update.
I
don't
know
if
we
have
any
oem
specific
stuff
today,
I
don't
think
we
have
any
of
the
oem
maintainers
on
the
call,
but
with
the
release
schedule
we
already
mentioned
we're
releasing
a
a
week
from
today
and
with
some
of
this
code
generation
stuff,
I
think
that's
probably
a
good
segue
into
talking
about
the
cross-playing
community
day
event
and
I'll.
Let
phil
kind
of
cover
all
that.
B
Cool
yeah,
if
you
just
want
to
pop
open
that
community
today
link
yeah,
so
we
basically
had
our
community
today
on
the
first
one
back
in
may
of
this
year,
and
so
this
one's
focused
on
kind
of
modernizing,
with
an
api
center
control
plane.
So,
as
you
all
know,
you
know
crossblind's
built
on
top
of
the
kubernetes
api
machinery,
which
is
an
api
centric
control
plane
designed
for
extensibility.
B
We
got
a
ton
of
really
awesome
speakers,
many
of
who
are
on
the
call
here
so
really
looking
forward
to
kind
of
a
great
session
kind
of
hearing.
You
know
from
kelsey
and
joe
beta
and
brennan
burns,
and
many
others
on
kind
of
like
the
future
state
of
where
we're
heading
kind
of,
I
guess,
as
an
industry
and
then
all
the
cool
stuff
that
we've
been
up
to
so
yeah,
really
looking
forward
to
it
and
that's
kind
of
a
free
virtual
event
on
the
15th
right.
B
The
day
after
we
released
1.0,
so
yeah,
definitely
looking
forward
to
celebrating
with
everybody
in
the
community
and
really
thankful
for
all
the
contributions
and
stuff
that
people
are
making.
A
For
sure
yeah
it
should
be
a
lot
of
fun,
a
lot
of
really
awesome
folks,
speaking
at
that
event,
so
definitely
please
sign
up
for
that
and
come
hang
out
with
us
as
we
kind
of
celebrate
the
1.0
release
all
right.
I
guess
that
was
kind
of
a
community
topic
and
I
know
we
have
the
beyond
1.0
here.
I
guess
we
can
pop
open
the
roadmap
again
here
and
see
if
there's
anything
folks
want
to
talk
about.
A
But
definitely,
as
folks
are
are
you
know,
looking
at
the
features
that
are
coming
out
in
1.0
think
about
things
that
you'd
like
to
you
know
be
followed
up
with
in
the
subsequent
release,
obviously
we'll
be
going
into
the
holidays
after
the
1.0
release,
so
things
will
probably
slow
down
a
little
bit,
but
you
know
we'll
we'll
stay
on
our
regular
cadence
of
getting
a
new
release
out
there,
and
so,
if
there
are
things
that
you
are
interested
in,
please
you
know
raise
issues
for
those
or
or
let
us
know
you
want
to
work
on
them
all
right.
A
Let's
see
what
issue
is
this?
Did
we
already
chat
about
it?
Oh
yeah.
I
think
this
is
the
cdk
stuff
phil.
Was
there
anything
else
you
want
to
mention?
I
know
you
already
went
pretty
in
depth
on
this
or
you
know
you
just
talked
about
custom
composition,
so
anything
you
want
to
add
here.
B
Yeah,
I'm
just
really
excited
about
their
collaboration.
You
know
kind
of
with
a
lot
and
italy
on
the
aws,
cdks
team
and
move
office
kind
of
bringing
together
like
multi-language
support
and
across
playing
on
top
of
the
kubernetes
api,
so
kind
of
looking
at
this
from
two
perspectives,
one
in
terms
of
stat
generation
that
cdk
supports
today.
B
But
then
we
made
significant
improvements
on
kind
of
the
ability
to
import
all
of
the
cross
plane
resources
into
cdks,
with
the
enhancement
that
dan
made
to
the
doc.crds.dev,
a
site
that
basically
scans
all
of
your
scans,
github
repos
for
crds
and
then
basically
provides
documentation
and
now
actually
has
like
a
raw
endpoint.
That
allows
you
to
get
the
mana
festival,
the
crds
for
a
given
version,
and
so
that,
basically,
plus
this
really
awesome
ux
overhaul.
That
was
done
recently
by
coder.
C
B
Herbert
she
coder
one,
and
so
you
know
this
basically
then
gets
fed
into
a
cdk's
import
command
where
you
can
just
specify
you
know,
github
colon
and
then
your
repo
and
version
and
then
I'll
go
ahead
and
import
that
and
so
there's
a
couple.
B
You
know
vrs
that
we
did
to
kind
of
make
that
you
know,
play
nice
and
can
be
nice
and
clean
and
everything,
and
so
got
that
up
and
running
against
platform
refaws
on
friday
and
basically
validated
that
working
end-to-end
and
did
a
little
code
gen
on
the
side
too,
for
importing
and
converting
the
existing
yamls
into
typescript
resources,
and
so
the
work
ahead
is
basically
kind
of
get
that
cleaned
up.
It's
kind
of
like
an
l1
import.
B
They
have
the
concept
of
like
l1,
l2,
l3
abstractions,
where
l1
is,
is
effectively
just
the
basic
marshalling
structures
that
are
equivalent
to
the
animal
l2.
Basically
providing
you
know
like
typescript
and
language
helpers,
that
kind
of
make
it
cleaner
to
create
a
given
resource
and
then
l3,
which
is
basically
kind
of
you,
know
like
a
composed
abstraction.
B
On
top
of
you
know
the
the
existing
resources
and
so
I'll
be
spending
time
over
the
next
couple
days
to
kind
of
get
the
l2
and
perhaps
an
l3
resource
for
cross-plane
core
as
part
of
a
new
cross-plane
crd
project
that
we're
just
kind
of
bootstrapping
and
then,
if
there's
time,
a
lot
has
been
working
on
a
cdk
sidecar.
B
So
he
just
got
done
publishing
a
repo
for
that
called
cdk's
operator
out
of
his
own
github
account
and
mobik's
been
working
on
kind
of
a
custom
composition,
prototype
and
so
the
the
idea
there
is
that,
in
addition
to
the
static
generation
that
you'd
be
able
to,
when
you
say
hey,
I
want
to
add
a
composition
to
my
my
package
and
cross
playing
in,
like
typescript,
just
add
a
flag
to
say
and
run
this
behind.
The
api
line
run
this
in
kubernetes
and
that
would
allow
dynamic
evaluation
of
that
cdks
program.
B
To
do
things
like
you
know,
grab
cider
ranges
from
external
sources,
using
whatever
libraries
you
want,
as
well
as
like
having
conditional
output
looping
for
if
you
want
multiple
subnets
things
like
that.
So
yeah
really
looking
forward
to
this,
and
it's
it's
nice
to
see
it
being
able
to
be
built
on
top
of
the
kubernetes
api,
as
opposed
to
an
alternate
to
the
kubernetes
api.
So
really
nice
kind
of
ecosystem
fit
with
cdks
and
kind
of
the
first
class
multi-language
support
that
we
have
planned
for
across
playing.
A
Awesome
well
thanks
for
that
update.
Let's
see,
do
we
have
anything
else,
let's
go
down
a
little
bit
more.
I
think
that
was
all
for
the
beyond
1.0.
It
doesn't
look
like
we
have
any
community
topic
topics.
I
know
we
already
talked
about
the
community
day
coming
up.
I
did
add
these
two
pr's
here
and
there's
a
number
of
other
ones
open
as
well.
That
I
think
just
need
some
review
from
folks,
but
it
looks
like
simon
who
I
don't
think
was
able
to
join.
A
The
call
today
wanted
to
be
able
to
specify
a
required
spec
and
was
unable
to
in
an
xrd.
So
that's
something
to
look
for
or
to
look
into,
and
it
looks
like
he's
already
taken
the
initiative
to
open
a
pr
there,
so
I
can
take
a
look
at
that
after
maybe
nick
would
also
want
to
look
at
that.
One,
oh,
it
looks
like
looks
like
you
already
have
awesome
eight
minutes
ago.
A
Nick
is
addressing
him
before
we
get
to
him
in
the
agenda
all
right,
and
then
this
one
was
one
from
me
at
the
end
of
last
week.
So
basically,
this
is
around
the
default
registry
naming
so
the
underlying
package
that
we
use
to
pull
crossplane
packages
in
core
cross
plane.
It's
called
go
container
registry
in
go
container
registry.
A
A
It
was
initially
motivated
by
probably
defaulting
to
the
upbound
registry,
where
most
packages
live,
the
source
was
getting
appended
with
index.docker.io
and
that
was
causing
if
you
declared
your
dependency
in
your
crossplane
package.
As
you
know,
crossplane
slash
provider
aws.
If
it
was
then
getting
added
as
index
dot,
docker
dot,
io,
slash,
cross,
plane,
slash
provider
aws,
then
we
weren't
saying
that
you
know
the
equivalent
package
was
present,
but
the
installation
and
resolving
obviously
didn't
work
either
because
it
was
trying
to
add
the
same
package
again
so
anyway.
A
What
we
do
now
in
this
pr.
It's
not
a
huge
change,
but
upstream
we've
added
the
ability
to
be
able
to
supply
whatever
default
you
want,
and
so
you
can
see.
I've
just
removed
the
index.docker.io
so
when
we're
actually
using
the
dependencies
and
adding
them
to
the
lock,
we
just
default
to
nothing.
A
So
if
you
don't
provide
a
registry,
we
don't
add
it
to
the
lock
with
one
which
just
makes
it
a
little
more
one-to-one
with
how
you
supply
your
dependencies
and
then
we
will
still
default
to
pulling
from
docker
when
we
actually,
you
know,
download
the
package
into
the
package
cache,
but
this
avoids
the
issues
that
were
shown
in
the
building
of
the
configurations
we
use
in
our
docs
here,
where
they
weren't
resolving
correctly,
because
they
were
specified
as
crossblind,
slash
provider,
alibaba
and
it
was
becoming
index.docker.io
so
anyway,
kind
of
a
small
change,
but
definitely
really
important
to
get
in
to
make
sure
that
this
is
functioning
properly.
A
So
I
just
want
to
surface
that,
so
we
can
get
some
reviews
on
that.
Did
anyone
else
have
any
pr's
they
wanted
to
discuss.
A
All
right,
I
know,
there's
a
few
other
ones
here
from
cosro,
and
I
comment
on
one
of
them,
one
of
them
exposing
metrics,
which
we
definitely
want
to
go.
I
think
that
one's
pretty
much
ready
to
go,
and
then
he
also
opened
one
for
memory
profiling
in
debug
mode,
which
I
think
sounds
like
a
cool
feature,
and
it
looked
pretty
good
to
me
but
didn't
give
it
too
much
of
a
pass.
A
So
if
anyone
else
wants
to
look
at
that
or
I'll
also
follow
up
after
this
call
and
take
a
peek
at
it
as
well
yeah,
so
I
think
that's
pretty
much
all
we
have
for
today.
I
will
give
anyone
a
chance
here
to
bring
anything
up
for
our
optional
discussion
time,
but
if
we
don't
have
anything,
we
can
go
ahead
and
finish
up.
C
Hey
then,
I
have
a
question
so
regarding
the
impact
on
the
providers
for
this
release.
D
A
So
from
the
provider
perspective,
I
just
you
know,
I'm
familiar
with
what
you've
done
in
in
the
ibm
cloud
provider.
So
far
you
should
be
good
to
go.
We
probably
will
bump
your
crossplane
runtime
dependency,
but
I
can't
think
of
anything
that
would
break
the
work
that
you've
done
so
yeah.
You
can
release
that
you
know,
or
we
can
release
that
on
any
cadence,
especially
going
forward
with
1.0.
A
You
know
all
versions
should
be
backwards
compatible,
so
so
there
shouldn't
be
too
much
to
worry
about,
but
we'll
definitely
make
sure
to
circulate
anything
and-
or
you
know,
help
update
any
providers
if
something
is
needed.
Okay,.
A
And
another
thing
to
note:
your
your
integration
tests
are
running
against
the
latest
master
cross
plane.
So
as
long
as
they're
passing
that
we
at
least
know
it
can
install
correctly
and
that
sort
of
thing,
yeah.
A
Cool
awesome
all
right.
Well,
if
no
one
else
has
anything,
I
think
we
can
go
ahead
and
call
it
a
day
thanks
everyone
for
joining,
if
you
hadn't
yet
added
your
name
to
the
roster
here,
please
feel
free
to
do
that.
Otherwise
we
can
go
ahead
and
call
it
a
day
thanks.
Folks,
thanks
dan
have
a
good
one.