►
From YouTube: Cloud Custodian Community Meeting 2023-07-25
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 in both GitHub Discussions and in HackMD:
- https://github.com/orgs/cloud-custodian/discussions
- https://hackmd.io/@c7n
Check out our Slack for more info! http://slack.cloudcustodian.io
A
All
right,
the
recording's
running
hello,
everybody
Welcome
to
the
cloud
custodian
community
meeting
for
July
25th
in
the
meeting
chat,
putting
the
the
notes
for
today's
call
and
sharing
the
screen.
A
So
everybody
can
see.
Okay,
I
was
just
getting
the
notes
together.
So
I
don't
have
a
lot
of
high
points
to
bring
up
up
front
other
than
introductions.
If
anyone
wants
to
we've
got
mostly
returning
faces
here
but
feel
free
to
say,
hi.
A
Well,
I
will
say
hello
to
all
of
you,
okay
for
the
items
here.
Just
still
we're
going
to
keep
this
note
until
we
until
we
move
on
from
python37,
we'll
keep
the
note
in
there
that
we're
moving
on
this
year,
and
it's
pretty
much
all
I
have
here
until
issues
in
PR
time.
So
as
anyone
have
any
particular
issues
or
PR's
they'd
like
to
call
out
for
review
for
discussion.
A
A
So
there
are
no
reviews
for
this.
I'll
take
a
look
at
that
one
I
already
started
because
yes,
I
was
picking
up
from
previous
work.
So
this
is
someone
just
someone
that
you
work
with.
A
B
That
old
po
has
a
two
two
or
three
changes,
and
we
only
need
one
of
one
of
it,
which
is
to
filter
the
maintenance
mode.
So
we,
you
know,
we
we
just
created
one
dedicated
for
maintenance
mode
and
submit
it.
Okay,
yeah.
A
Yeah,
that
sounds
good,
so
the
I
do
owe
a
comment
on
this.
I
started,
looking
back
through
the
old
through
the
old
PR
and
where
I
was
looking
was
here
this
this
piece
where
we're
pulling
all
the
maintenance
actions.
I
just
didn't,
know,
I
think
there
there's
a
case
where
we
might
have
where
that
can
only
return
100
at
a
time,
and
we
might
have
more
than
that,
so
we
might
need
to
paginate
that
or
or
when
we
call
this
thing
pass
in
the
list
of
IDs.
A
So
I
should
just
have
a
comment
on
that
because
it
looks
like
we
can.
We
can
return
up
to
100,
but
we
can
also
pass
up
to
100
IDs.
So,
but
aside
from
that
change,
I
think
this
looks
cool.
A
You
know
yeah,
who
knows
I,
who
knows,
if
you're
actually
going
to
have
100
RDS
instances
that
need
maintenance,
probably
not
I,
hope
not
it's
a
bad
day
yeah,
but
who
knows?
Okay,
cool,
hopefully
you're,
not
testing
that
case,
but
yeah
thanks
for
bringing
that
one
up.
A
I
would
say,
one
of
the
things
we
should
have
pointed
out
before
was
that
we
had
a
release,
and
there
were.
This
should
have
been
in
the
agenda
that
we
had
some
breaking
changes.
So
one
folks
who
were
following
along
in
either
the
the
deaf
channel
on
slack
or
or
the
issues
there
was
a
change
Upstream
with
photo
with
photo
3
changing
the
user
agent.
So
if
anyone
happens
to
be
relying
on
certain
user
agent
naming
patterns,
that's
going
to
be.
A
That
would
be
a
breaking
change
and
and
there's
an
issue
here
with
all
the
details.
So
that's
in
in
this
latest
in
this
latest
release
and
then
for
anyone
who
happens
to
be
using
the
Oracle
provider.
I
know
it's
still
classified
as
Alpha,
but
there's
just
some
changes
going
on
to
kind
of
simplify
standardizing
the
on
the
action.
Syntax.
B
A
C
You
go
yeah
I
mean
I
was
just
I
typed
it
up
in
the
chat
here.
It
only
affects
if
you're
using
cloudtrail
to
clock
track
custodian
policies
like
if
you
had
your
own
next
on
cloud
trail,
Splunk,
Athena
whatever,
and
you
were
acquiring
it
to
determine
what
it's
more
of
an
operator
concern
than
a
pot.
It's
not
a
backwards,
it's
not
a
backwards
compatibility
concern
for
running
custodian
or
running
policies.
It
is
more
question
for
operators
that
were
using
cloudtrail
to
introspect
custodian
actions
because
our
user
agent,
and
that
changed.
A
Yeah
I
I
think
where
I've
seen
it
you're
right
using
cloudtrail
for
searching
if
you're
ingesting
it
somewhere,
trying
to
find
out
which,
if
you're
tracking
for
for
your
own
history
like
which
policies
were
were
responsible
for
for
which
actions
or
something
that
can
be
it's
it's
useful
to
dig
into
the
cloud
show.
Data
I
also
feel
like
I've
seen.
People
use
event
filters
on
event-based
policies
that
tied
in
that
expected
a
certain
user
agent
pattern
to
try
to
catch
custodian
actions,
but
that
that
feels
pretty
Edge
Casey
too,
but
yeah
anytime,
you're
you're.
B
C
B
Okay,
I'll
take
a
closer
look
and
and
and
and
see
if
it
traffic
to
us
as
far
as
it
doesn't
change
any
behavior
in
the
in
the
cloud
trail
type
in
in
the
the
the
Run
mode.
I
think
we
are
good
yeah.
Thank
you.
A
Yeah
you'd
call
that
it's
just
worth
it.
It's
yeah,
it's
just
one
of
those,
those
things
that,
if
you
were
looking
at
it,
you
would
have
seen
this
type
of
user
agent.
That's
going
to
change.
If
you
don't
look
at
the
user
agent,
you
don't
use
it
to
for
any
sort
of
filtering
tracking
triggering.
Then
you
won't
care.
A
Okay,
yeah,
so
Kapil
I
was
just
calling
out
the
piece
about
the
release,
the
the
AWS
change
and
then
the
Oracle
one
for
the
actions
for
whoever's
using
Oracle
anything
else
noteworthy
other
than
the
normal
additions
and
fixing.
C
Enough
for
the
last
release,
but
for
the
next
release
it
looks
like
the
housing,
significant
changes
with
the
dynamic
notified
buffers
and
a
few
other
things.
It
feels
like
nice
releases
shipping
shaping
up
to
be
have
some
significant
changes,
I'm
going
to
currently
also
working
on
release,
automation
for
it.
C
So
as
a
current
PR
up
in
testing,
but
I'm
hopeful
that
we'll
be
able
to
we
we've
been
late
by
week
for
I,
guess
the
last
two
or
three
releases,
mostly
unrelated
stuff
and
packaging
ecosystem
worlds,
but
helpful
too
get
back
on
track.
Let's
say
in
August,
but
yeah
yeah.
A
Cool
thanks,
so
that's
that's
really
discussion.
We
so
we
already
talked
about
the
the
pending
maintenance
filter,
we'll
look
at
that.
One
look
into
that
one,
a
little
bit
more,
some
release,
notes
any
other
issues,
PRS
to
call
out
or
questions
and
concerns
it's
kind
of
fair
game
to
anyone.
At
this
point.
Thank
you.
A
A
A
So
thanks
for
Tears
Kapil
for
working
on
that
one
but
like
if
you'll
mentioned,
that's
kind
of
a
pretty
core
change.
So
that
looks
like
a
big
thing
should
be
a
good
one.
Sounds
good.
A
And
what
was
the
other
thing
we're
calling
out
as
a
as
a
big
change
coming
up?
Well,
there's
the
release,
the
release,
automation,
stuff,
that's
more
on
the
on
the
under
the
covers
workings.
A
Yeah
I
don't
know
that
other
ones
of
these
are
jumping
out
the
flow
log
stuff
I
know
that
just
came
in
that
I
think
is
interesting
only
because
we're
we're
changing
syntax
but
Kapil
you've
got
some
something
like
a
nice
little
compatibility,
shim
layer
in
there
to
transform
the
syntax,
which
seems
pretty
nifty
I,
don't
know
if
that's
worth
talking
about
at
all.
C
No
I
think
in
terms
of
one
other
big
item
that
I'd
like
to
resurrect
is
the
auto
lender
layer
stuff,
but.
C
I
feel
uncomfortable
handy
commitment
on
it
at
the
moment,
but
yeah
so
that
might
that
might
fall
out
to
September
release
space
on
timing.
A
I
did
see
that
there
was
a
I,
saw,
PR
open
and
then
get
closed.
Look
like
because
of.
B
C
Of
has
a
corporate
CLA
I
ping
them
about
they've
got
two
people
I,
think
that
have
contributed
that
aren't
that
had
this
issue,
so
I
try
to
Ping
them
about
adding
them
adding
to
their
corporate
cncf
CLI,
but
I
will
try
to
touch
base
with
them
tomorrow.
They're
I
think
Eastern
European
on
TZ.
So
this
requires
a
time
zone
shift
for
as
far
as
I'm
attending
this.