►
From YouTube: Cloud Custodian Community Meeting 2021-07-13
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 It's our first-ever community meeting! Thank you to all who attended!
Read the minutes for this meeting
https://github.com/cloud-custodian/community/discussions/17
Join our community!
https://github.com/cloud-custodian/community
A
The
first
ever
cloud
custodian
community
meeting-
I'm
gonna,
be
your
host
for
this
first
meeting.
My
name
is
george
castro
and
thank
you.
Everyone
for
showing
up,
I'm
gonna,
go
over
some
quick
formatting
and
then
we'll
get
into
some
introductions
and
then
we'll
get
started
here.
So
all
of
the
meeting
docs
here,
I'm
gonna
plan
on
taking
them
all
I'll,
be
using
markdown
and
I
will
be
checking
these
into
github
on
a
regular
basis
and
posting
those
results
to
the
list
so
that
everyone
has
that
information.
A
I've
got
the
meeting
url
at
the
same
place
in
the
notes
every
time,
so
you
can
just
click
through
as
well
as
a
time
zone
converter.
So
if
you
click
through
here
it
will
I've
elected
to
choose
some
locations
around
the
world.
A
So
if
you
want
to
add
your
favorite
location
or
where
you're
at
my
my
intent
here
is
to
just
kind
of
maintain
when
time
zones
happen
for
contributors
and
things
like
that
and
keep
this
always
up
to
date,
the
idea
being
you
could
just
click
through
and
always
get
to
the
meeting.
I'm
gonna
be
your
host
today.
Ideally,
I
would
love
to
get
us
to
a
point
where
we
can
have
guest
hosts
and
things
like
that.
A
Celebrity
hosts
and
all
sorts
of
fun
things
like
that
and
then
I'll
be
adding
the
permanent
link
to
the
notes
where
this
will
live
in
github,
as
well
as
url
to
the
actual
youtube
recording
that
we
have.
So
each
of
the
notes
have
that
and
then
we'll
do
the
obvious
things.
I
keep
a
playlist
of
all
the
meetings,
so
you
can
catch
up
when
you're
on
the
road,
all
that
kind
of
good
stuff,
and
with
that
the
first
thing
we
have
is
some
agenda
items,
so
I
figure.
A
The
first
thing
that
we
could
do
is
basically
do
some
introductions.
Obviously
this
is
our
very
first
one,
so
I
wanted
to
take
some
time
to
get
to
know
each
other.
I
kind
of
picked
a
format
for
this
meeting
with
an
open
agenda.
However,
I'm
not
really
wedded
to
any
of
those
things
and
we're
kind
of
just
going
to
just
start
having
these
and
making
adjustments
as
we
see
fit.
I
know
lots
of
us
come
from
other
open
source
projects
or
you
know
have
seen
how
other
projects
run
meetings
and
things
like
that.
A
So
there's
really
lots
of
different
ways.
You
could
do
it.
I
figured
I
would
start
with
this
style
and
then
we
could
adjust
based
on
our
culture
and
how
we
see
fit,
and
things
like
that.
So
with
that,
I
figure
we'll
do
introductions.
So
let's
give
it
about
36
seconds
per
person,
I'm
going
to
introduce
myself
and
then
I'm
going
to
pick
someone
and
then
that
person's
going
to
introduce
themselves
and
they're
going
to
introduce
themselves.
A
So,
let's
start
with
your
name
where
you're
from
and
maybe
what
you're
looking
to
get
out
of
the
community
meeting
or
maybe
cloud
custodian
itself.
Obviously
some
of
us
are
using
this
kind
of
stuff.
So
just
tell
us,
I
don't
know,
I
guess
why
you're
here,
without
making
it?
Why
you
why
you're
here
and
yeah
also
don't
forget
to
mention
your
pronouns,
so
I
am
george
castro.
He
him
his.
A
I
live
in
ann
arbor,
michigan
and
I've
just
recently
spent
the
last
few
years,
working
in
the
kubernetes
and
kubeflow
communities,
and
I've
started
at
stacklit
now
to
kind
of
help.
Organize
things
like
this
and
do
stuff
like
this
in
the
notes
later
I'll
show
you
how,
where
I
keep
my
notes
and
my
board
and
basically
my
job
is
to
help
all
of
you
have
a
good
time
and
get
what
you
need
out
of
the
project.
So
with
that
todd,
since
you
arrived
early,
I'm
going
to
pick
you
to
go
next.
B
I
guess
he
him
whatever
I
don't
know
and
I
actually
work
at
23andme
and
we
started
using
cloud
custodian
a
couple
years
ago
and
I
ended
up
contributing
a
lot
of
code
and
so
I'm
like
the
sole
maintainer
and
sole
runner
of
that
infrastructure
at
our
company.
And
so
then,
at
one
point,
capill
asked
me
if
I
wanted
to
be
a
co-maintainer
for
the
aws
site,
because
that's
the
part
that
we
use
so
yeah,
so
I've
been
working
with
it
for
a
couple
of
years.
B
Oh
I'll
pick
aj
because
he's
one
of
the
few
folks
that
I
have
actually
interacted
with
recently.
C
Oh
thanks,
so
I
am
aj.
C
I
have
I've
used
cloud
custodian
in
the
past
at
at
work,
as
it
probably
sounds
like
a
similar
situation
to
what
todd
did
or
is
doing
and
similar
path
used,
it
loved
it
used
a
lot
internally
and
started
contributing
and
found
my
way
to
stack
it
from
there
and
now
I'm
trying
to
work
on
it
more
so
from
this
meeting,
I'm
just
hoping
to
find
out
where
everybody
else
is
coming
from
and
help
focus
the
effort
in
a
good
direction
and
from
there
let's
go
to
liz.
D
Hi,
my
name
is
liz
pronouns.
Are
she
her?
I
come
to
cloud
custodian
through
stacklet,
actually,
where
I
am
a
developer
advocate,
so
I
am
actually
totally
brand
new
to
open
source
and
more
or
less
actually
the
cloud
custodian
and
as
your
developer
advocate,
I
am
here
to
listen
and
advocate
and
help
bill's
community.
So
hoping
I
will
be
hanging
out
with
you
all
a
lot
more.
Oh
and
I
am
in
san
francisco
california.
D
E
Hey
everyone,
marco,
he
him!
I
live
in
the
washington
dc
metro
area.
I've
been
using
cloud
and
cloud
stuff
for
a
while.
You
know
container-based,
stuff
and
cloud.
I
come
through
to
the
clockwise
editing
community
by
way
of
kapil
and
stacklit,
and
I've
been
using
it
on
and
off
for
probably
last
year
now
and
so
here
to
help
learn
more
about
how
the
community
needs
to
grow
and
what
we
can
do
to
assist
I'll
I'll
pick
alfred.
E
Hello,
I'm
alfred.
I
used
to
work
at
capital,
one
where
I
first
learned
about
cloud
custodian
and
from
there
moved
to
aws
and
then
afterwards
to
stacklit
I'd
like
to
just
attend
these
meetings,
to
keep
a
finger
on
the
pulse
and
you
know
have
an
awareness
of
the
current
state
of
what's
going
on
with
c7n
and
and
the
contributors.
F
F
Like
four
years
now,
work
mostly
on
the
aws
provider
as
well
as
just
general
core
stuff,
looking
to
stay
more
active
on
the
contributing
side
of
things
with
this
meeting,
I
think
it
will
help.
You
know,
keep
keep
the
steady
push
progress.
I
guess,
apparently,
I
stacked
it
previously
blue
capital,
one
so
yeah.
Looking
looking
forward
to
all
the
great
stuff,
I
will
throw
it
over
to
jameson.
G
Thanks
honey,
I'm
jamison
roberts,
he
him!
I
live
in
castle
rock
colorado
and
I've
been
using
cloud
custodian
for
several
years.
G
Here,
came
from
a
company
called
transamerica
aegon,
where
we
had
a
large
implementation
of
cloud,
custodian
and
kind
of
started,
contributing
to
the
community
and
open
source
a
few
years
back
and
yeah
trying
to
stay
on
top
of
the
community
within
getter
and
the
different
channels
to
kind
of
see
what's
up
and
what
new
users
are
up
to,
and
so
out
of
this
meeting,
I'm
just
dropping
in
here
to
kind
of,
listen
and
see
what
the
community
has
thoughts.
G
You
know
around
features
issues
all
that
kind
of
stuff
see
where
I
can
be
helpful
and
kind
of
you
know
things
that
we
can
work
on
to
make
clock
studying,
even
better
so
yeah.
Currently
I'm
working
at
stacklet
as
a
solutions
architect
and
develop
lots
and
lots
of
policies,
so
I'm
gonna
actually
pass
it
along
to
good
buddy
mine
fawn,
who
I've
been
talking
to
for
a
while.
H
Hey
jameson
good
to
see
you
fellas,
I've
actually
missed
you
quite
a
bit.
You
know,
but
I'm
here
I
won't
cry
too
many
tears,
but
any
case
yeah
founder
sword
with
palo
alto
networks
definitely
gone
through
quite
a
bit
of
work
with
the
stackler
team
and
been
a
big
fan
of
cloud
custodian
for
several
years
and
still
the
promoter
of
it.
H
I
use
it
pretty
much
every
day
for
very
specific
ad
hoc
queries,
supporting
security
incident
investigations
by
the
infraspect
team
and
I
hope
to
contribute
in
my
individual
capacity
since
I'll
probably
be
a
little
bit
limited
in
my
official
capacity
to
contribute,
but
I
love
the
stacklet
crew,
a
big
fan
of
the
founders
and
now
looking
forward
to
this,
and
thanks
for
kicking
this
off.
I
appreciate
this.
This
is
awesome
now,
who
will
I
sunny?
H
Oh
he
him.
Oh
sorry,
I
already
went,
but
I
think,
losing
track
here.
I
Yeah,
I
can
go
yeah,
so
wayne
witzel
here,
like
many
others
via
via
stacklet,
and
my
main
reason
for
attending.
Is
I'm
interested
in
getting
and
starting
to
get
into
some
of
the
kubernetes
support
for
c7n
and
just
kind
of
starting
to
hang
out
and
absorb
some
of
just
the
baseline
c7
and
knowledge
so
that
I
could
hopefully
potentially
start
to
contribute
to
the
kate
support
upstream.
I
J
Thank
you,
elaine
thanks
george
for
hosting
I,
my
name
is
travis.
I
think
everybody
knows
me
pronouns.
He
him
his.
I
am
here
to
show
support,
certainly
interested
in
staying
in
touch
with
the
community
and
the
topics
that
matter
most
to
it.
So
I
am
going
to
pass
to
kapil.
F
Hi,
my
name
is
kapil.
I
am
generally
pronoun
neutral.
I
will
respond
to
all
and
yeah.
Thank
you,
george,
for
putting
this
together
super
looking
forward
to
it.
F
I
was
super
nervous
about
doing
one
of
these
for
the
last
few
years,
which
is
why
it
never
been
done
before
outside
of
in
person,
so
looking
forward
to
getting
it
going
and
seeing
what
kind
of
flow
we
can
get
on
some
of
our
pr
backlog,
because
it's
definitely
stretched
out
over
the
last
few
months
and
I
think
we're
starting
to
make
some
progress
on
whittling
it
down.
So
looking
forward
to
it,
I
will
pass
to.
K
K
K
And
I'll
pick
dean.
L
All
right,
thank
you
mayor,
so
I'm
dean
he
him
his.
I
join
also
by
way
of
stacklet
long
time,
history,
linux,
open
source
cloud
tech
coming
from
canonical
working
on
ubuntu
and
I
recently
joined
stacklit
to
work
in
engineering
and
I'm
here
to
just
get
up
to
speed
and
help
george
get
to
know.
What's
going
on
and
see
what
I
can
do
to
help
and
let's
see
I
will
pass
to.
M
Oh
hey,
this
is
a
ram
here,
that's
a
big
long!
It's
a
big
name.
You
can
call
me
ram,
I'm
from
india,
and
this
is
the
first
meeting
that
I'm
attending
at
a
community
level
and
I've
been
using
cloud
custodian
for
a
year
right
now,
not
in
production
but
at
my
personal
level,
and
I'm
just
here
to
learn
new
things.
I
don't
have
any
specific
agenda
from
my
side
and
nice
to
meet
you
guys.
A
N
Okay,
yeah,
I
just
joined
up.
I've
got
I've,
got
15
minutes
in
between
my
meetings,
so
I'm
with
tyson
foods
and
we've
been
using
cloud
custodian
for
about
three
years
now,
we've
been
in
in
the
cloud
for
a
little
little
over
a
little
longer
than
that,
and
we
use
it
extensively
for
production,
non-production
everything
and
we're
just
I'm
just
just
here
to
see
what
I,
what
what
we
can
do.
I
don't
know
awesome
great.
A
F
A
All
right,
so
I'm
glad
everyone
came
to
make
it
like.
I
said
this
is
our
first
one,
so
it
was
is
kind
of
key
for
me
to
see
like
who's
going
to
show
up
who's
going
to
be
here.
Obviously,
a
lot
of
my
co-workers
from
stacklet
are
here
as
well,
however,
if
over
the
next
few
months,
I'm
hoping
to
get
as
many
people
from
many
affiliations
as
possible.
A
So
if
it's
six
months,
the
stacklet
people
are
still
outnumbering
everybody
else-
I
don't
know,
maybe
I'm
in
trouble,
but
I'm
really
glad
everyone
took
time
out
of
their
day
to
to
come
and
do
this.
A
So
I
wanted
to
share
a
few
things
that
I've
been
working
on
here
is
I've
started
a
community
repo
in
github
here,
and
you
might
have
seen
this
from
other
cncf
projects
and
I'm
gonna
kind
of
start
keeping
track
of
meta
things
in
here
that
might
or
might
not
affect
the
community
and
I've
started
to
organize
it
actually
around
a
board.
So,
as
I've
been
learning
a
lot
about
cloud
custodians,
seeing
how
the
docs
are
laid
out,
things
like
that,
I
started
to
note
things
down
things
like
hey
baby.
A
We
should
have
a
regular
meeting.
You
know,
github
has
new
cool
templates
out.
Should
we
use
those
things
like
that,
so
I've
been
starting
to
actually
file
these
as
issues
in
this
repo,
and
you
all
can
kind
of
consider
this
as
the
hey
I
kind
of
found
something,
it
might
be
a
good
idea
for
us
to
look
at
this,
but
I
don't
have
time
to
do
that.
A
Anyone
in
this
you
know
in
the
community
feel
free
to
either
file
an
issue
here,
or
you
can
ping
me
on
chat
or
during
one
of
the
meetings
and
I'd
be
happy
to
kind
of
put
that
on
the
board.
Here,
I'm
sort
of
prioritizing
my
work
around
this
board
for
a
few
reasons,
a
to
keep
it
open
to
everybody.
A
So
you
can
kind
of
see
what
I'm
working
on
and
see
if
it's
interesting
to
you
and
b,
to
kind
of
show
you
what
community
level
st
style
things
I'm
working
on,
so
that
if
you
have
an
experience
in
that
field
or
something
or
you
have
a
strong
opinion,
you
can
ping
me
about
it.
So
there
are
some
things
that
I'll
be
reviewing
here.
A
You
might
have
seen
with
other
projects,
things
like
having
an
office
hours
program,
who's,
the
person
grabbing,
all
the
q,
a
the
facts
from
chat
and
collating
those
into
something
useful
things
like
that.
So
I'm
starting
to
kind
of
investigate
all
sorts
of
things
like
that
kind
of
the
typical
community
manager
thing,
and
I
will
plan
on
having
that
always
be
living
at
this
board
in
public.
So
anyone
can
go
ahead
and
and
do
that,
I
don't
really
anticipate
myself
having
any
private
agenda
items
there.
A
A
Okay,
the
next
is
agenda
items,
so
the
good
thing
is
I'm
planning
on
having
open
agenda
basically
at
the
at
the
start
of
every
meeting,
so
I'll
usually
put
together
the
notes
for
the
next
week,
the
day
after
this
meeting
and
I'll
keep
those
in
an
obvious
place
and
I'll,
probably
over
communicate
a
little
bit
too
much
on
the
mailing
list.
As
to
hey.
You
know
reminder
the
next
meeting's
coming
here:
the
open
agenda
items.
A
If
you
would
like
to
see
an
agenda
item
kind
of
addressed
during
this
meeting,
we
could
just
plot
that
directly
in
the
notes,
I'm
using
a
tool
called
hackmd.
I've
got
the
url
in
the
notes.
You
basically
just
sign
in
with
your
github
account,
and
then
you
can
add
your
thing
there
and
then
we'll
address
it
during
the
meeting.
Think
of
that,
as
kind
of
your
relief
valve,
maybe
you
have
a
pull
request
or
something
that
you
want
to
get
some
attention
to
that
kind
of
thing.
A
Or
maybe
you
have
a
proposal
that
you
like
to
bring
forth
for
the
community
and
I've
had
kapil
kind
of
seed,
one
or
two
of
them,
and
I've
done
a
few
myself.
So
we
can
just
kind
of
start
getting
through
the
motions
and
as
we
figure
out
how
we're
gonna
do
this
we'll
you
know
we
can
figure
out
hey.
A
Maybe
we
need
more
time
around
agenda
items
and
maybe
less
time
around
the
pull
request
party
and
then
for
the
last
quarter
of
the
meeting
we'd
like
to
do
what
we
call
a
pull
request
party.
I've
had
some
people
saying.
Well,
I'm
sure
a
lot
of
you
have
known
kapil
for
a
long
time
and
figuring
out
what
is
in
his
brain
is
kind
of
part
of
the
puzzle
in
itself.
A
So
one
of
the
things
that
we'd
like
to
do
is
get
started
is
basically
kind
of
having
prs
like
on
a
hit
list
as
they're
coming
into
the
repo,
so
that
the
authors
of
those
pr's
and
kapil
could
kind
of
review
them.
We
could
review
them
in
a
high
bandwidth
manner
and
basically
get
the
knowledge
that
we
want
out
of
his
brain
and
into
more
people's
kit
bags
so
that
we
can
scale
and
things
like
that.
A
Does
anybody
have
any
questions
or
opinions
about
that,
because
we've
got
a
few
lined
up.
So
there's
that
and
of
course,
as
always,
I
know
everybody's
busy.
So
if
you
need
to
bail
or
something
at
all
during
any
time
of
the
meetings,
you
know
feel
free
to
just
skate
in
and
out
as
necessary,
and
you
know
no,
no
judgment,
no
harm
no
foul
there.
I
know
everyone's
busy
and
we
appreciate
your
time.
A
J
A
Very
introverted
crowd,
yes
yeah!
You
know,
nobody
has
any
opinions
until
we
start
talking
about
designs,
I'm
sure,
and
with
that
we
have
any
agenda
items
here.
We
have
one
that
kapil
added
that
I'm
going
to
bring
up
right
away,
and
that
is
an
enhancements.
Oh,
we
got
a
new
person
here.
Thank
you,
marco.
Are
you
just
handling
new
people
who
show
up
to
the
meeting?
Is
that
yeah.
A
Thank
you
appreciate
that
awesome.
Rohit
welcome.
You
want
to
introduce
yourself
or
you
just
want
to
sit
in
the
back.
You
can
go
either
way,
you're
on
mute.
A
All
right
awesome
welcome
all
right,
so
agenda
items,
I'm
gonna,
leave
that
there,
if
you
have
a
topic
that
you
wanna
discuss
for
today,
feel
free
to
just
whack
it
in
there
in
the
notes
I'm
gonna
stick,
marco
is
going.
Can
I
do
this?
Marco
is
going
to
stick
the
url
to
the
hackmd
in
chat?
A
If,
if
you
want
to
get
into
the
raw
notes-
and
if
you
have
something
that's
kind
of
too
big
to
tackle
or
whatever
feel
free
to
stick
it
in
the
backlog
and
that's
what
I
did
for
an
agenda
item
that
I
I'd
like
I'd
like
to
talk
about
slack
next
time,
unless
people
really
want
to
start
talking
about
it
today,
but
I
don't
know
if
we
wanted
our
first
meeting
to
be
that
controversial,
so
kapil
added
an
enhancements
feature
process
kapil.
What
do
you
have
in
mind
for
here
yeah
I
mean.
L
F
Python
pep
or
like
python
enhancement
proposal,
process
or
kubernetes
cap
kubernetes
enhancement,
proposal
ssd,
and
the
notion
is
basically
so
generally
speaking,
stating
we
haven't
done
that
we
have
tried
to
do
it
as
in
the
form
of
issues
like
a
github
issue
that
then
gets
sort
of
discussion,
but
like
for
longer
form
documents.
It
doesn't
it's
not
clear
if
that's
really
the
right
way
to
get
the
best
review
on
the
document
as
it's
getting
updated,
and
so
is
it
get
at
issue?
F
If
you
have
it
in
the
main
ticket
description,
if
it
gets
revised
over
time,
then
you
lose
sort
of
the
contents
of
the
comments
below
it
get
lost
as
far
as
how
they
apply
to
the
document
and
like
a
poll
request,
the
the
biggest
issue
with
github
pull
requests
in
this
context.
Is
they
work
for
the
initial
pull
request,
but
after
they're
merged,
it's
really
hard
to
comment
on
them,
and
so
at
least
for
the
policy
testing
spec.
What
we
did
was
we
did
a
get
up
issue.
F
I
think
marco
authored
the
document,
and
then
it
was
like
a
google
doc
that
we
linked
into
the
issue
so
that
anyone
could
put
comments
on
like
how
do
we
get
to
better
policy
testing
and
so
like
at
least
some
of
the
things
I
feel
like
are
longer
impact
and
hard
to
see
the
full
direction
on
by
inferring
from
pull
requests,
especially
on
larger
pull
requests.
I
think
tj's
got
some,
but
I
know
there's
something
there
and
I
just
don't
know
where
it's
going
and
I'm
like.
I
really.
F
It
would
be
really
helpful
to
try
to
understand
it
and
comment
on
it
in
the
form
of
what's
the
sort
of
the
plan
and
the
vision
around
it,
and
this
tj's
got
one
around
that
he's
very,
very,
very
passionate
about
around
arab
handling,
inactions
and
so
just
trying
to
figure
out
how
we,
how
we
scale
larger
feature,
work
in
a
way
that
actually
gets,
gets
the
right
amount
of
discussion
about
something
and
can
also
serve
as
a
living
artifact
for
people
coming
into
the
project
in
the
future.
F
Like
does
it
go
into
the
repo?
Does
it
like?
Does
it
get
merged
into
our
sphinx
stock
builds
right,
and
so
I
I've
seen
I've
seen
every
community
do
everything
every
which
way
yeah
at
this
point,
like
the
I
think
like
we're,
currently
doing
a
bunch
of
our
cncf
stuff
and
that
they
they
say,
do
it
in
google
drive
for
discussion
and
then
convert
it
to
markdown
for
committing
to
the
repo
the
apr,
which
also
feels
a
little
weird.
I
mean
it's
fine.
F
It
feels
a
little
weird
only
that
you're
reformatting
it
to
replay
your
whole
document
at
the
end
of
the
review,
which
a
gender
of
more
review
but
yeah.
So
just
general
discussion
like
for
longer
form
features
policy
things.
F
One
error
handling
another
one
pulling
out
c7n
core
from
c7n,
especially
another
one
like
what
is
what
do
people
feel
like
is
the
right
way
to
do
that
and
I'll
throw
out
a
straw
person
of
I
think
we
potentially
grow
outgrowing
issues
for
longer
form
discussion,
and
we
should
try
a
google
doc
potentially
so
that
everyone
can
comment
in
on
directly
the
line
item
content
they
care
about
bye.
Michael.
B
I'll
comment
that
internally
we
do
google
docs
for
that
same
purpose,
design,
review
comments,
all
that
kind
of
stuff,
and
we
have
found
that
much
more
successful
in
having
actual
engaging
discussions
and
focusing
on
decisions
and
things
like
that,
and
then
you
know.
Similarly,
once
we're
done,
the
final
decisions
end
up
getting
put
into
a
confluence
talk
or
something
like
that
as
the
okay,
here's,
our
policy
or
whatever
we're
discussing
right,
but
google
docs
has
definitely
worked
fairly.
B
F
Yeah,
I
think
google
docs
just
has
a
better
experience
for
commenting
and
feedback.
I
think
the
way
it
would
probably
work,
then,
is
sort
of
what
we
trialled
with
the
policy
testing
stuff,
where
you
follow
an
issue.
So
a
maintainer
drops
a
it
with
the
google
doc
and
spec.
It
has
a
proposal
or
a
spec,
and
we
add
the
proposal
label
to
it
on
the
github
issue
and
then
those
are
quickly
browsable
potentially
add
it
to
the
roadmap
backlog,
big
impact
context.
F
We
would
also
then
also
trigger
a
discussion
in
a
follow-up
meeting
of
this
working
of
this
community
meeting
for
like,
if
there's
not
clear,
oh
yeah,
that
makes
sense
and
like
if
there's
actually
questions
that
we
need
high
bandwidth
communication.
This
is
probably
the
right
channel
for
it.
A
F
A
F
A
E
E
In
a
single
org
or
account
or
something
I
I
agree
with
like
todd's
assessment
like
google
docs-
are
really
nice
for
collaboration
both
from
like
an
editing
perspective,
but
as
well
from
like
a
commenting
and
feedback
loop.
But
there
are
some
sticky
things
that
come
where
in
an
org
like
in
a
company,
it's
a
lot
easier
to
manage
the
the
domain
of
that
where
we
could
potentially
lose
good
specs.
Just
because
someone's
google
account
gets
deleted
or
they
go
inactive
or
something.
F
F
Unfortunately,
as
a
toilet
plays
in
somewhat
of
an
enterprise-y
space,
we
run
across
those
organizations
rather
frequently,
which
is
one
of
the
reasons
why
we're
on
getter
is
because
it's
it's
just
a
web
app
and
no
one
thinks
to
block
it.
Those
are
fine
and
fair
points.
I
mean
we
could
talk,
but
we
could.
That
could
be
a
legitimate
reason
for
why
the
final
merge
would
actually
be
transferred
into
into
markdown
or
into
markdown
or
arrest
markdown
preferred
so
that
we
can
actually
publish
it
to
like.
F
B
B
F
F
So
it
would
just
it
would
keep
a
pristine
copy
of
the
content,
but
of
the
potentially
the
final
form
or
whatever
point
we
snapshotted
it,
but
I
think
ideally
directing
people
to
try
to
get
it
merged
into
the
actual
repo
would
lead
to
it
being
published
as
part
of
the
official
docs
might
be
a
better
channel,
because
if
we
just
copy
the
a
snapshot,
we're
going
to
lose
all
the
common
history
and
how's
that
different
than
the
final
archive
form,
which
would
be
published
through
the
website,
would
be
the
only
differential
there
that
I
don't
see.
F
Like
say,
I'm
a
brand
new
contributor
at
this
great
idea.
I
want
to
respect
I
use
my
personal
or
my
corporate
g
suite
and
to
create
a
doc
if
we
and
it
gets
feedback
and
commentary
we're
like
okay.
This
looks
good
to
go
we're
not
we
can't
you,
don't
transfer
the
doc
ownership
per
se
and
to
create
a
clean
copy,
you'd,
actually
copy
the
copy
make
a
copy
of
a
content
which
would
lose
all
the
comment.
History
per
se,
with
my
understanding
so
and
you
do
that,
probably
at
the
end
of
the
process.
F
So
I
don't
know
that
you
have
the
full
history
that
you're
referencing.
You
actually
have
revision
document
revision
history
in
the
copy,
but
you
wouldn't
necessarily
have
common
history.
A
A
H
I'm
I'm
just
wondering,
wouldn't
one
still,
you
know
maybe
submit
a
you
know,
issue
and
then
say
you
know,
sort
of
the
issue
type
is,
you
know,
request
for
comment,
type
of
document
and
then
one
of
the
you
know,
custodian
maintainers,
you
know,
creates
the
doc
links
to
the
issue.
So
we
still
have
you
know
tracking
like
from.
If
we
search
the
issues
most
of
folks
need
to
get
up
first
issues,
you
get
the
issue,
they
get
the
link
to
the
doc
and
then
they
can,
you
know,
add
the
comments
there.
H
So
that
way,
of
course
you
know
you
keep
ownership
and
then
yeah
hear
what.
F
F
I
mean
going
back
to
the
original
problem.
It
happens,
but
does
it
happen
that
often
that
we
should
be
working
around
a
whole
process
around
working
around
it,
like
of
someone's
account
getting
deleted,
etcetera.
F
F
Really
don't
like
do
we
want
to
be
asking
people
for
their
email
address
in
public
forums
and
channels?
That
also
feels
a
little
strange
too,
which
we
would
need
to
do
to
recreate
the
document
and
assign
them
red
edit
rights,
because,
generally
speaking,
github
usernames
or
do
not
track
back
to
people
easily
without
verbal
confirmations.
A
So
maybe
a
way
to
help
here
would
be.
I
can
I
have
items
to
investigate
the
workflow
there.
Why
don't
we
concentrate
on
what
you
would
like
to
see
the
process
to
be?
As
far
as
you
know,
inception
review
approval
implementation
and
then
I
could
come
back
with
kind
of
here.
Are
options
for
workflows?
A
You
know
that
way.
That
way,
you
may
we're
making
progress
on
what
we
think
the
actual
process
itself
would
be
like
and
not
talk
about.
F
A
A
A
Anybody
else
have
strong
opinions
on
design
design,
docs.
A
Proposals
awesome
all
right.
Well.
That
concludes
our
first
seated
agenda
item.
I've
got
a
few
for
next
week,
but
in
interest
of
time
we're
gonna
kick
over
to
the
pr
review
now.
So
I
guess
what
we'll
do
is
kind
of
close
the
meeting
here.
Unless
anybody
has
any
questions
or
things
like
that,
and
then
we
could
just
do
pr
reviews
for
a
little
bit,
and
I
guess
that
kind
of
concludes
the
formal
part
of
the
meeting.
Does
anybody
have
any
comments?
Questions
agendas
for
next
time.
A
Okay,
so
I
guess
kapila
and
I
will
continue
talking
to
each
other
this
time-
we're
going
to
bring
in
some
pr
folks
scrolling
down
here
for
the
pr
reviews
that
we're
gonna
review
today,
we're
gonna
start
with
app
autoscaling
and
who's.
This,
I'm
I'm
still
learning
everybody's
github
handles
so
cp
lee.
I
don't
think
they're
in
this
meeting
right
kapil
did
you
want
to
go
over
this
one
or
we
have
these
in
orderish?
I
think.
F
So
generally,
this
pr
looks
awesome.
It
adds
in
all
this
application,
auto
scaling.
I
think
there
were
some
questions
that
it
was
re-implementing
tagging
and
having
it
reuse.
I
think
the
existing
tag
actions
was
the
only
real
thing
I
think
as
far
as
making
it
work.
So
I
think
it
just
needs
some
like
maintaining
time
to
go
back
through
and
make
sure
that
we're
not
duplicating
existing
capabilities
out
of
band
like
or
as
one
offs
for
a
particular
thing
seems
well
tested.
Maybe
it's
been
updated.
F
F
F
Do
we
have
any
gcp
users?
Oh
yes,
michael
next,
one
is.
G
F
Filters
this
one
is
basically
every
lots
of
gcp
researchers
have
embedded
im
docs.
This
adds
a
ability
to
do
filtering
on
resources
based
on
their
embedded
imdocs,
but
it's
it's
effectively
just
doing
a
raw
jms
path.
Query
against
the
raw
doc,
which
tends
to
not
be
particularly
useful
for
expressing
any
semantic
intent,
is
the
concern
I
linked
in
the
pr
to
a
prior
pr
around
this
that
wasn't
as
flushed
out,
but
I
mean
the
upsides.
This
actually
covers
a
lot
of
resources.
F
I
think
there
were
two
things
one
using
like
the
method
action
base,
sub
class
to
get
the
the
resource
or
the
method
filter
a
sub
class
to
get
the
resource.
I
am
doc.
The
second
was
to
try
to
express
semantic
intent,
whereas
the
other
pr
allowed
you
to
specify
like
scope
and
binding,
which
allows
for
being
able
to
say
things
like
hey.
Am
I
giving
any
grants
to
users
outside
of
my
domain?
F
I
think
one
of
the
challenges
is
just
trying
to
express
that
type
of
logic
with
a
raw
jms
path,
expressions
generally,
not
non-trivial
or
generally,
not
not
viable.
So
in
terms
of
getting
that
merged.
I
think
it's
a
question
of:
can
we
can
we
layer
that
lot
that
behavior
on
in
a
compatible
way
and
then
can
we
use
a
method
filter
as
a
base
class
just
to
simplify
some
of
the
internal
logic.
F
And
I
don't,
we
only
have
a
handful
of
gcp
active
maintainers
one
is
in
eastern
europe,
so
this
time
zone
doesn't
work
out,
but
I
mean
doesn't
work
out
the
other
ones
in
dc,
but
I
don't
know
if
they
saw
the
invite.
A
And
then
in
the
notes
here,
I'll
put
any
we'll
just
put
gcp
familiar
folks
welcome
to
dive
in
or
or
pink
appeal.
What
are
we.
F
A
A
A
Wayne,
but
if
not,
we
can
move
over
to
this,
this
gcp
folder
one.
F
F
This
is
basically
allowing
you
to
take
in
project
hierarchy
into
account
as
you're
building
out
actions
and
then
a
specific
implementation
around
propagating
labels
and
folder
hierarchies,
but
additionally,
to
that
it
also
enables
a
capability
that
applies
to
the
other
providers
with
regards
to
source
propagation,
if
you're
doing
like
source,
config
or
source
cloud
asset
inventory
or
source
resource
graph
and
azure
notion,
as
you're
going
through
related
resource
filters
that
that
initial
source
propagates
to
the
related
resources,
if
they
support
that.
F
Right
now
it
just
needs.
I
need
some
more
unit
tests
to
get
the
coverage
up
to
pass
on
ci,
okay,
but
it's
got
some.
F
F
Yeah,
so
this
is
someone
who
went
through
they
did.
This
is
actually
a
small
team
of
folks
they
went
through
and
they
did
a
few
pr's
and
then
they
went
through
and
we're
trying
to
tidy
up
the
contribution
documentations
it's
already
interviewed.
I
think
it
looks
good
okay,
I
think
the
question
there
would
be.
They
need
a
little
bit
of
help
on
getting
through
why
sphinx
is
barfing
on
them,
and
so
basically,
it's
filling
ci
right
now,
basically
nci.
F
We
also
build
the
docks
and
that's
not
currently
working
with
this
pr,
and
that
just
needs
someone
to
dig
into
why
and
potentially
deal.
E
F
I
think
this
one's
actually
the
one
word
with
the
diff
error,
not
strings.
Oh
the
the
code.
F
This
is
the
issue:
let's
go
to
the
pier.
Well,
I
mean
this
is
the
issue
where
he
describes
it.
G
F
I
look
at
the
pr
I'm,
like
all
you're
really
doing
is
pulling
all
the
metric
client
side
to
re-implement
the
server
side,
filters,
client
side,
and
I
I
feel
like
I'm
missing
something
about.
Why
is
this
a
pr
here
doing
doing
like
max,
and
some
an
average
client
side
makes
solves
a
use
case
versus
passing
it
to
the
server.
C
Yeah
that
was
that
was
related.
It
was
a
bit
tangential
to
the
to
the
issue
in
that
6301.
I
am
happy
to
go
back
in
and
have
a
look
at
this
you
so
you
can.
You
can
put
me
down
for
this
one
only
because
we
we've
had
I've,
had
this
discussion
and
commented
on
either
the
issue
or
the
pr
okay,
and
I
think
I
understand
it,
and
then
I
don't
look
at
it
for
a
while,
and
then
I
have
to
go
back
and
figure
it
out
again
sure
sure
so
yeah
it
should
be.
A
F
This
is
basically
just
quality
of
life
thing.
We
should
just
do
it
it'll
change
effectively.
This
is
basically
custodian
when
you
go
to
provisional
lambda
policy
automatically
creating
its
own
layer
and
assessing
it
to
lambda
functions.
The
problem
is,
is
this
is
specific
to
aws
generally,
the
sdk
revs
faster
than
land
arrives
versions
once
a
year
twice
a
year,
the
sdk
is
rev
every
other
day,
and
so
we're
constantly
in
a
point
where
we
do
a
release,
everything
looks
great.
F
The
people
go
to
update
their
functions,
it
doesn't
work
and
then
they
have
to
manually
add
layering
to
their
policies,
which
is
supported,
but
it
would
be
nice
if
that
was
just
an
out-of-the-box
experience.
F
Notes
needs
more
work,
there's
potentially
compatibility
considerations.
I
mean,
I
think,
that
care
actually
works.
F
It
will
change
some
of
the
runtime
behavior.
It
has
to
deal
with
people
that
already
have
the
manual
specification,
and
I.
L
G
F
Dealt
with
that,
if
there
was
just
boto
and
just
the
bottom
stack
we
we
ran
with
we,
we
didn't,
we
still
kept
doing
the
auto
layer
stuff.
If
they
had
specified
any
other
dependencies,
then
sorry
they
had
a
manual
dependency
specification
on
a
layer.
We
used
it
sure
and
if
they
didn't,
then,
if
they
just
did
a
package
specification,
then
we
just
we
continued
to
do
the
old
thing
unless
the
packages
were
just
the
photo
packages,
in
which
case
we
used
our
auto
layer.
A
F
Said
yeah
that
pr
is
openable.
I
think
I
played
around
with
it
and
I
was
just
like
I
don't
know,
because
it's
gonna
be
good
or
bad.
So
yeah,
that's
my.
A
M
F
B
A
A
F
Hasn't
changed,
I
think
it's
just
a
question
of
doing
the
legwork
and
making
sure
that
there's
a,
I
think,
a
couple
edge
cases
that
we
just
have
to
deal
with
as
far
as
making
sure
that
we're
keeping
good
compatibility
with
any
extent
setups
that
people
have
done
previously
to
work
around
this
issue.
A
F
There's
a
number
of
issues
I
think
I'm
related.
Okay,.
A
All
right
so
there's
a
number
of
issues
around
this
okay,
so
this
is
just
maybe
something
that
sit
on
a
backlog
and
then
we'll
get
we'll
get
back
to
this
is
that
bull.
A
And
then
the
last
one
I
want
to
do
today
is
convert
tags.
B
B
You
some
background
here,
so
I
ran
across
this
while,
while
messing
with
all
the
event
handling
stuff
and
changing
things
around
and
restructuring
it,
it
comes
in
mostly
when
you
have
resources,
calling
the
resource,
tagging,
api
bits
and
or
resources,
calling
another
class
of
a
resource
and
doing
sharing,
and
things
like
that,
where
they're
passing
in
tags
to
go
there,
there
were
a
handful
of
places
where
I
have.
B
Basically
you
you
have
to
know
this
function
over
here.
Expects
tags
in
the
traditional
list
form
versus
a
dictionary
form,
and
this
function
over
here
you
know,
assumes
that
it's
a
dictionary
form,
and
so
it
felt
cumbersome
and
difficult,
and
so
I
ended
up
writing
this
conversion
thing
where
you
can
just
specify.
Okay,
I
want
to.
F
B
B
In
so
long,
I
can't
remember
the
exact
details:
now:
I'd
have
to
go
through
the
pr
and
there
there's
there's
definitely
places
where
having
a
function
cleans
up
a
lot
of
the
code
so
that
there
isn't
so
much
duplication
on
okay.
I'm
I'm
expecting
that
the
input
here
is
list
form
and
I'm
explicitly
converting
it
over
to
dictionary
form
so
that
I
can
manipulate
it
right
and
adjust
the
values.
And
then
I
convert
it
back
to
list
form
again
to
then
pass
it
to
the
resource
tagging
api.
B
I
think,
or
I
I
can't
remember
the
details,
but
that's
the
general
concept,
and
so
there
was
definitely
a
need
to
simplify
converting
from
one
form
to
another,
and
so
I
wrote
the
function
and
I'm
like
well.
Why
don't?
We
just
like
convert
all
the
use
cases
to
use
this
function
and
it
actually,
in
my
opinion,
cleans
up
the
code
in
that
it's
clear
on
the
intent
of
what
you're
doing
in
that
code.
So
for
readability
it
felt
cleaner.
B
F
Yeah,
you
mentioned,
like
the
usage
of
the
other
resource
tag,
actions
and
stuff.
So
is
this
more
related
to
like
copy
related
tag
and
like
errors
that
come
up
out
of
there.
B
Yeah,
some
of
some
of
it's
related
to
that
yeah,
where
you're
you've
got
one
resource
and
you're
trying
to
copy
tags
from
another
type
of
resource,
and
this
resource
assumed
you
know
it.
There
were
a
couple
of
resources
where
the
way
that
aws
presents
it,
I
don't
think,
is
entirely
consistent
in
the
traditional
list
form.
B
There
were
a
couple
of
edge
cases
where
it
comes
in
in
dictionary
forms,
and
so
you
just
you
have
to
know.
Okay.
I
need
to
pass
this
to
this
other
function
over
here,
but
that
assumes
that
it's
in
dictionary
form,
whereas
using
everything
in
list
form
and-
and
so
it
just
felt
complicated,
and
if
you
could
just
pass
a
set
of
tags
from
one
function
to
another
and
then
that
function
would
just
convert
it
to
whatever
format
needed
internally,
then
that
would
simplify
the
cooperation.
F
So
yeah
on
the
implementation,
I
think
the
only
comment
I
had
was
that
it's
got
a
large
inner
function
as
a
static
closure
that
didn't
need
to
be
that
might
be
nicer
to
define
as
a
private
function
at
the
top
scope
as
opposed
to
doing
a
closure,
because
the
closure
wasn't
it
didn't,
need
to
be
a
closure.
The
inline
function
aspect
of
it
sort
of
like
a
convert
tags
with
a
big
body.
That's
the
actual,
separate
function
inside.
F
I
think
just
pulling
that
up
to
the
top
level.
I'll
drop
a
comment
in
the
pr
readability
aspect.
It's
one
liner
for
one
minor
to
me
so
perfectly
comprehensions,
the
reuse
aspect,
especially
around
copyrighted
tags,
is
potentially
viable
and
meaningful.
It.
A
Yeah,
well
it
we're
a
little
bit
past
time,
but
liz
and
aj
you
all
going
to
team
up
on
that.
One
together
liz
was
looking
for
someone
to
pair
with.
D
A
C
C
A
Awesome,
and
with
that
I
know,
people
have
meetings
and
they're
busy
all
day,
so
this
is
basically
how
we're
going
to
roll.
So
if
you
have
any
feedback,
good
positive
you're
not
going
to
hurt
my
feelings,
we
just
want
to
make
stuff
efficient
like
this
and
then
we'll
just
keep
rolling
with
that.
A
Keep
your
eyes
out
on
the
list
and
I'll
be
sending
up
the
minutes,
a
link
to
the
videos
and
all
the
good
stuff,
and
with
that,
thank
you
so
much
those
of
you
that,
thanks
for
supporting
our
first
meeting
thanks
guys.