►
From YouTube: Cloud Custodian Community Meeting 20210914
Description
Our community meeting is public and we encourage users and contributors of Cloud Custodian to attend! You can find the notes for this meeting on our github repo: https://github.com/cloud-custodian/community/discussions
To get an invite to the meeting join the google group and you'll receive one via email: https://groups.google.com/g/cloud-custodian
A
September
14th
2021-
and
this
is
the
clock
custodian
community
meeting.
The
code
of
conduct
is
in
effect
and
just
a
reminder
that
we
do
record
these
and
put
the
archive
on
youtube.
Thank
you.
Everyone
for
showing
up,
I
know
we're
conflicting
with
a
lot
of
apple
announcements
and
event.
Participation
has
been
very
light
today
across
the
board.
A
So
thank
you
for
taking
the
time
I've
got
the
agenda
here
and,
as
always,
you
can
find
our
meeting
notes
in
hackmd
and
I'll
make
sure
I
toss
that
url
in
chat,
and
it
is
also
on
the
meeting,
invite
and
I
put
the
permanent
url
and
all
that
good
stuff
in
the
notes,
and
then
I
always
post
a
follow-up
to
the
to
the
mailing
list.
So
with
that,
let's,
let's
get
started
here,
introductions
and
announcements.
Does
anybody
want
to
introduce
themselves?
A
I
looks
like
everyone-
here's
been
here
before
so
unless
anyone
has
any
burning
introductions
that
they
want
to
do
we'll,
go
ahead
and
move
on
to
the
next
one,
our
regular
agenda
items
so
regular,
weekly
docs
print
sessions.
This
is
something
liz
and
I
have
been
doing
on
fridays.
A
We've
started
keeping
an
actual
agenda
now
of
the
things
that
we're
working
on
and
I'll
get
to
the
calendar
page
and
stuff
like
that
when
we
get
to
that,
but
we've
been
working
basically
about
an
hour
a
week,
just
finding
something
in
the
docs
that
needs
to
be
fixed
and
working
on
it.
Liz
you
had
review
and
edit
documentation
for
server
side
filtering
any
updates
there,
I'm
pretty
sure
we're
halfway
or
in
the
middle
of
doing
this,
but
nothing
to
show
yet.
B
Yeah,
no
there's
nothing
to
show
yet
for
this,
because
I
need
to
do
a
little
bit
of
research
first
to
make
sure
I
completely
understand,
what's
going
on
with
server-side
filters
before
I
start
taking
apart
the
documentation
so
that
it's
step
one
and
what
I'm
thinking
I'd
like
to
do
is
when
I've
got
a
handle
on
it,
then
put
it
on
agenda
for
one
of
our
dark
sprints,
so
are
interested
in
contributing
to
the
documentation
for
server
side
filters,
because
perhaps
you
have
run
into
something
there
where
you're
like.
B
I
could
fix
that.
Keep
an
eye
on
the
doc
sprint
agenda
for
that
to
come
up,
but
I
won't
be
the
next
and.
A
Then
I've
got
the
tracking
issue
there
for
everyone.
If
you
want
to
follow
in
on
that,
okay
and
then
the
big
news
for
this
week,
probably
the
highlight
of
the
week
is
the
governance's
code
day
with
cloud
custodian
is
now
live
for
the
day
before
kubecon
plus
cloud
native
con.
I've
got
the
link
here
and
we've
got
some
speakers
here,
including
emily
freeman
from
aws.
That's
going
to
be
great
and
some
other
pending
speakers
just
waiting
for
them
to
get
their
final
approvals
and
things
like
that.
So
definitely
check
that
out.
A
Just
a
reminder.
We
would
really
appreciate
it
if
you
would
register
so
we
can
keep
track
of.
You
know
how
many
people
are
attending
and
all
that
good
stuff,
but
also
just
a
reminder
that
the
event
is
100
free
and
you
do
not
need
a
kubecon
ticket
and
we
are
going
all
virtual
now
right
or
will
there
be
a
presence
physically.
C
No,
I
think
they're
going
virtual,
because
it
was
just
too
much
back
and
forth
and
if
a
few
of
us
go,
we
can
always
do
a
reception
in
los
angeles
like,
but
I
don't
know
how
everyone
will
comfortable
about,
but
most
of
the
attendees
we
talked
with
speakers.
They
were
not
traveling
to
kubecon,
so
we
decided
to
make
it
virtual
and
just
keep
it
simple
and
not
make
it
too
complicated.
Yeah.
Some
of
the
speakers
are
posted,
we're
still
waiting
for
approvals
from
the
rest
of
the
approved
speakers.
C
So
as
soon
as
they're
up
we'll
publish
their
name
and
schedule
as
well.
This
week.
A
Yep
and
I'll
probably
send
a
separate
mail
for
the
schedule
itself,
just
to
make
sure
that
people
see
that.
So.
Thank
you
so
much
to
those
of
you
that
submitted
talks
really
appreciate
the
level
of
high
quality
submissions
that
we
got.
We
think
it's
going
to
be
a
really
great
day,
umerica
appeal.
Any
final
comments
on
this.
D
D
A
Helps
pick
this
swag
george.
Is
it
me?
I
believe
it
is
yes
excellent,
awesome
all
right
and
with
that
those
are
really
the
only
two
major
announcements
that
we
have
for
this
week.
I
I
have
two
pr's
that
I'd
like
to
bring
to
our
slash
issues
that
I
like
to
bring
to
the
attention
and
then
the
notes
here
I'm
going
to
keep
the
section
for
the
links
to
the
clock
or
governance's
code
day
and
then
our
upcoming
cloud
custodian
days,
which
will
be
resuming
in
november
and
those
are
the
the
workshops
and
whatnot.
A
Yeah,
we
sure
did
so:
we've
been
making
fixes
to
the
rst
files
in
the
repo
and
those
are
all
getting
up
to
date.
However,
the
published
html
files
on
the
website
do
not
match
what
is
in
the
rst.
D
It's
not
that
it's
totally
broken
but
you're
correct,
there's
a
problem
there
so
currently
and
we
should
get
rid
of
drone
drone-
is
actually
the
thing
that
builds
the
docks
from
github
pages.
Like
does
this
things
run,
it
publishes
the
github
pages
and
our
drone
server
is
currently
using
a
let's
encrypt
dns
thing
and
that
basically
bars
every
90
days
and.
B
D
Ci
that
clock
is
currently
barfed,
which
means
it
needs
to
hop
on
a
server
to
go
fix,
which,
oddly
enough,
I
don't
have
credentials
for
at
the
moment.
D
To
get
that
resolved
live
in
the
next
24
hours,
we
should
potentially
look
at
just
moving
this
get
rid
of
drone
and
move
it
to
github
actions.
To
do
that,
it
will
need
extra
credentials
to
write
back
to
the
repo
okay.
B
D
Besides
that,
I
think
it
is
something
that
is
has
served
its
purpose
and
is
probably
more
concerned
now
than
it
is
a
help.
D
Yeah
they're
not
gonna,
get
an
issue
already
out
there
or
get
rid
of
drugs.
D
D
Should
keep
it
going
but
to
unblock
this
immediate
issue
with
regards
to
getting
the
docs
updated.
B
A
A
Branch
again
yeah,
I
was
going
through
all
of
that
stuff,
so,
okay,
moving
on
to
the
second
one,
is
new
events
page
with
the
calendar
todd
I
believe,
you're,
the
one
that
filed
an
issue
that
would
like
to
see
the
calendar
and
whatnot
be
more
easy
to
find.
So
what
I've
done
is
I've
pr
to
calendar
widget,
we
it'll
be
just
cloud
custodian
events
and
then,
on
that
page
I
embedded
just
a
kind
of
traditional
google
calendar.
I've
went
ahead
and
created
a
google
calendar
copy.
A
This
meeting
the
docs
meeting
and
all
that
kind
of
stuff
and
it'll
be
nice
and
available
there
on
the
website
and
if
you
want
to
subscribe
to
it,
you'll
just
be
able
to
click
a
button.
Additionally,
there's
a
bunch
of
fancier
calendar
widgets,
and
I
want
to
put
a
schedule
for
clock
custodian
day
and
do
all
of
that
kind
of
stuff.
But
this
initial
pr
is
mostly
just
adding
the
calendar
events
I
do
need
to
come
after
this
merges.
A
A
From
a
general
perspective,
I
I
also
have
another
pr
in
flight
that
will
change
the
readmes
to
all
just
point
to
this
one
page
so
that
we're
not,
I
didn't,
want
you
to
have
to
follow
a
chain
from
reaper
to
repo
to
end
up
here
so
I'll.
I'm
also
working
on
that
any
comments
or
anything
here.
Marco
helped
me
out
with
a
lot
of
the
html.
A
D
A
A
Got
you
got
you,
and
I
know
I'm
also
cognizant
of
the
fact
that
at
some
point
we'll
get
a
fancier
cncf
powered
site
and
all
that
stuff.
So,
as
I
was
doing
investigating
on
like
the
fancier
calendar
widgets,
I
don't
want
to
add
any
interdependencies
or
or
any
of
that
stuff.
So
that's
why
it's
it's
kind
of
basically
the
default
iframed
google
calendar,
which
will
will
be
serviceable
for
now
any
other
feedback
on
this.
A
A
A
A
All
right,
and
with
that,
that's
our
issue
and
pr
things
that
I've
added
here
do
we
have
any
other
agenda
items
most
everything
on
the
backlog
is
noted
and
not
no
progress
to
report
this
week.
A
D
For
committers
I've
gotten
one
thing
that
I'm
trying
to
play
around
with,
which
is
make
ci
faster.
I'm
obsessed
with
this
because
you
don't
be
obsessed
with
it.
It
gets,
gets
ugly,
real
fast
and,
I
think,
switching
out
to
poetry.
Currently,
our
talks
builds
do
not
seem
to
take
advantage
of
our
this.
D
The
cashing
and
get
of
action,
so
switching
out
to
poetry
should
definitely
we
should
be
able
to
get
under
five
minutes
for
a
full
matrix
run
and
it'll
also
help
us
unify
windows,
but
the
rest
of
osx
and
linux
runs
so
still
helpful
on
that,
but
still
work
through
it,
and
then
I'm
hopeful
to
get
through
a
few
more
pr's
on
the
backlog
for
reviews
john's
not
here,
but
he
also
did
the
actual
merge
on
something
which
is
great.
D
So
if
there's
an
approved
pr
there,
don't
don't
be
afraid
to
to
to
do
the
merge
on
the
maintainers
out
here
all
right.
That
was
it
for
me.
A
D
I
mean
total
end
to
end
is
probably
about
10
minutes.
That
10
minutes
is
so
we
run
about
20,
I
want
to
say
18,
oh
a13,
on
the
ci
matrix
build.
We
currently
do
about
a
three
by
five
matrix
for
python
versions,
os
x,
linux,
and
then
we
do
a
separate
one
for
windows,
one
that
ends
up
taking
a
simple
amount
of
times.
Actually,
the
doc
swings
build
that
we
do
so.
Currently
we
do
docker
build
and
sphinx
builds
per
pr.
D
The
and
then
unit
test
runs
and
then
some
additional
things
around
some
of
the
go
line
tools
we
have
and
then
the
static
analysis,
security
bits
around
semgrep
and
bandit
some
the
static
analysis
tools
are
actually
pretty
fast,
all
the
other
ones.
My
skilling
ones
are
dealing
with
some
form
of
software
installation
around
our
dependency
set,
and
currently
they
don't
aren't
able
to
take
advantage
of
cash
around
the
fact
that
we've
already
installed
these
defenses
haven't
changed
and
that
takes
about
two
minutes
30
seconds.
D
So
looking
for
a
net
decreased
time
on
insults
about
10
minutes
30
seconds
with
regards
to
sphinx
itself,.
D
Tbd,
I
think
there
there's
and
syncs
and
docker,
I
think,
are
the
other
two
outliers
in
terms
of
getting
it
back
down
to
like
a
four
minute
to
three
to
four
minutes.
Ci
time,
we'd
have
to
look
at
doing
those
either
async,
but
we.
D
As
lightly,
we
moved
them
to
pr
just
because
there
were
issues
with
regards
to
prs
that
would
break
break
image,
publishing
what
I
would
potentially
look
to
do
for
the
docker
ones
at
least
would
be
to
not
not
do
that
ci
job
or
short
circuit
that
ci
job
if
there
hasn't
been
a
change
to
the
actual
docker
image,
because
the
rest
of
them
like
the
rest
of
the
build
machinery,
as
far
as
the
actual
build
for
the
docker,
is
roughly
just
going
off
of
what's
in
ci,
so
there's
no
per
se
differential
value
for
having
that
there
it
does.
D
There
is
a
light
functional
test
as
a
result
of
the
docker
image
build
against
aws,
and
I
think
it's
maybe
one
against
gcp
as
well,
so
that
light
functional
testing
is
potentially
something
we
should
probably
potentially
want
to
move
out,
but
effectively.
The
notion
for
the
things
that,
besides
the
matrix,
build
when
we're
unifying
the
matrix,
build
we're
going
to
decrease
the
time
for
the
matrix,
build
for
the
things
that
are
outlined
beyond
that.
D
We'd
look
at
trying
to
make
them
more
differential
as
far
as
only
running
for
when
they
need
to
run
the
dock.
Build
is
probably
it
will
see
a
decrease
in
time.
It'll
probably
go
to
seven
minutes,
but
the
rest
of
ci
should
just
be
green
at
that
point,
in
which
case
you
know,
unless
you
misplace
misplaced,
a
colon
or
quote
in
sphinx
in
your
doctrine,
things
are
okay.
As
for
improving
since
times
that
is
probably
a
dedicated
look
at
stinks
itself,
I
think
we're
trying
on
version
right
now.
D
We
can
look
at
what
not
an
update
to
ladies
and
greatest
helps
at
all.
Generally,
it
has
not.
We
we've.
We
ourselves
haven't
covered
significant
speed,
regressions
in
sphinx,
which,
when.
D
They've
been
very
responsive
on
fixing,
but
I
do
it.
This
is
the
thing
currently
we're
not
too
coupled
to
fix.
We
have
some
restrictor
text
most
of
the
reference
docs,
that
we
are
things
that
we
generate
outside
of
sphinx,
so
we
get
twitch
generators
or
something
else,
but
that's
a
longer
topic
for
potentially
a
different
discussion.
The
only
other
topic
that
I
had
pending
for
the
community
meeting
was
the
cncf.
Ezcla
is
one
of
those
orwellian
naming
conventions
where
the
easy
part
of
the
cla
is
not
easy.
D
D
Not
well
suited
to
our
purpose,
I
would
seriously
consider
either
switching
out
to
the
sap
cla
tool,
so
I
bought
and
or
switching
out
to
dco
we've
had
challenges
with
dco
and
in
the
past
with
regards
to
a
lot
of
our
contributing
population,
not
necessarily
being
familiar
with
git
and
dco
particular
and
doing
science.
The
sign
offs
on
it,
so
sap
bot
would
potentially
be
a
thing.
I'm
going
to
try
to
separately
schedule
some
time
with
the
cncf
eccli.
D
Sorry,
linux
foundation
clc
easy
cli
people
to
try
to
understand
with
them
what
you
sap,
cla
bot,
yeah
at
cla.
Otherwise,
okay,.
A
D
And
I'm
gonna
at
least
try
to
give
blue
explanation,
people
a
chance
to
see
if
they
can
cover
off
on
the
basics
of
usability
and
and
whatnot
that
we're
looking
for
in
this
community,
I'm
starting
to
feel
like
the
easy
cli
bot
is
not
easy
and
it's
actually
hurting
hurting.
Our
ability
to
have
the
contributors
have
an
easy,
onboarding
path.
D
It
is
not,
you
know,.
A
D
A
I'm
glad
no
one
has
opinions
on
clas
all
right
and
with
that
that
comes
to
the
end
of
agenda
wrapping
it
up
going
once
going
twice
all
right.
Thank
you.
Everyone
for
coming
and
watch
the
list
for
the
notes
and
the
video
on
youtube
thanks.
Everyone
have
your
35
minutes
back
thanks.
Everyone.