17:31:53 <abuzachis[m]> #startmeeting Ansible AWS Community Meeting
17:31:53 <zodbot> Meeting started Thu Feb 23 17:31:53 2023 UTC.
17:31:54 <zodbot> This meeting is logged and archived in a public location.
17:31:54 <zodbot> The chair is abuzachis[m]. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
17:31:54 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:31:54 <zodbot> The meeting name has been set to 'ansible_aws_community_meeting'
17:32:44 <abuzachis[m]> #chair tremble jillr markuman
17:32:44 <zodbot> Current chairs: abuzachis[m] jillr markuman tremble
17:34:16 <abuzachis[m]> I had a look at the milestones in community.aws for 5.3.0 https://github.com/ansible-collections/community.aws/milestone/2 and we have only one.
17:35:44 <abuzachis[m]> #topic: community.aws 5.3.0 release
17:35:52 <tremble> Do we have anything else we want to pull in?
17:35:52 <abuzachis[m]> #info:  https://github.com/ansible-collections/community.aws/milestone/2 and we have only one.
17:35:52 <abuzachis[m]> 5.3.0 Milestone · an
17:36:03 <abuzachis[m]> * #info:  https://github.com/ansible-collections/community.aws/milestone/2
17:36:19 <jillr> mgraves and I have been working on the CI policies for #1716 for a few days.  It's behaving very oddly.
17:36:49 <abuzachis[m]> I know Mike was testing the policies on that PR and I also tried it, and it should be probably fine.
17:37:33 <abuzachis[m]> jillr: tested earlier today. it seems Mike is the only one having issues with one policy.
17:37:45 <jillr> We had talked about just deploying the policy (since we don't disagree with anything in it) and seeing how it goes
17:38:02 <jillr> I was testng with 3 different users last night and couldn't get consistent results with any account
17:38:33 <markuman[m]> abuzachis[m]: He did one commit today that might fixed it
17:38:40 <jillr> IAM  ¯\_(ツ)_/¯
17:39:24 <abuzachis[m]> Other than this, do we want to pull something in 5.3.0 as tremble suggested?
17:41:28 <tremble> If not, we're possibly good to get 5.3.0 prepared next week.
17:42:49 <abuzachis[m]> Not sure what you think about this one https://github.com/ansible-collections/community.aws/pull/432?
17:43:25 <abuzachis[m]> It seems there's lot of work already there and probably with minimal changes we can have it ready.
17:44:53 <tremble> Sure, I might have chance to poke it tomorrow.
17:45:04 <abuzachis[m]> Awesome, thanks!
17:45:21 <abuzachis[m]> This one https://github.com/ansible-collections/community.aws/pull/869 instead?
17:46:47 <tremble> That one's harder iirc, I don't think I can push fixes to their repo
17:47:17 <abuzachis[m]> ok, we can probably poke the author and see if we can have it for 6.0.0 in case
17:49:09 <tremble> The PR queues are in a much better state now, we stand a chance of keeping on top of PRs as they come in.  Feel sorry for the folks who got radio silence for a year or more
17:49:58 <tremble> Like that ACM one
17:50:05 <abuzachis[m]> Yeah, we're still improving. Thank you for all that work!
17:50:47 <abuzachis[m]> There's also another one, already passed through a first round of reviews https://github.com/ansible-collections/community.aws/pull/1353
17:51:35 <abuzachis[m]> However, we can also try to pull some of the remaining PRs for 6.0.0
17:52:15 <tremble> Yeah, testing that was weird
17:52:35 <tremble> Something about dedicated AZs
17:53:11 <abuzachis[m]> Ah, ok
17:54:58 <tremble> But maybe we add it to the milestone and see what we can do
17:55:37 <abuzachis[m]> Yes, that makes sense!
17:55:47 <tremble> Think the acm one's a good story behind it too
17:57:34 <tremble> Looking forward to getting 6.0.0 out the door
17:58:21 <abuzachis[m]> Do we want to set any timeline for 5.3.0?
17:58:45 <tremble> Next week?
17:59:32 <tremble> Or whenever those blasted ecs tests finally get in :)
18:00:20 <abuzachis[m]> makes sense to me 👍️
18:02:04 <jillr> I have to run for another call, see y'all  o/
18:02:23 <abuzachis[m]> Thank you jillr
18:03:14 <tremble> 6.0.0 - I'd suggest ~ April 25
18:04:15 <tremble> That gets it into the next major Ansible release and pulls in a new version of botocore
18:05:35 <abuzachis[m]> If the cutoff is planned by mid of May, that would make sense
18:06:41 <abuzachis[m]> We could try to release amazon.aws a week earlier.
18:07:42 <abuzachis[m]> Switching topic to community.aws 6.0.0 milestone
18:07:56 <abuzachis[m]> #topic:  community.aws 6.0.0 milestone
18:08:25 <abuzachis[m]> #info: https://github.com/ansible-collections/community.aws/milestone/1
18:08:52 <abuzachis[m]> We do not have any left at the moment, but unless we have 5.3.0 out, we can fill in.
18:09:28 <tremble> Yeah, 6.0.0 already has some major changes, they're just in already:)
18:10:57 <tremble> It will probably be the last python 3.6 compatible release (based on botocore support for python 3.6)
18:12:15 <abuzachis[m]> Something else to add in here? or we can switch to amazon.aws?
18:12:46 <tremble> Not from me
18:14:39 <markuman[m]> Neither from me
18:14:48 <abuzachis[m]> Ok 👍
18:15:09 <abuzachis[m]> #topic: amazon.aws release 5.3.0 milestone
18:15:40 <abuzachis[m]> #info: https://github.com/ansible-collections/amazon.aws/milestone/2
18:16:59 <abuzachis[m]> Do we have anything else to include in 5.3.0?
18:17:44 <abuzachis[m]> I guess this is something we could probably include https://github.com/ansible-collections/amazon.aws/pull/1383
18:17:46 <tremble> Nope.
18:18:03 <tremble> Ah, yeah the key one would be good
18:18:27 <abuzachis[m]> This small one https://github.com/ansible-collections/amazon.aws/pull/1378
18:19:11 <tremble> Sure, I'll review tomorrow
18:19:46 <abuzachis[m]> I do not know about this one https://github.com/ansible-collections/amazon.aws/pull/1282
18:20:26 <tremble> Yeah, think it was needed for a c.aws PR
18:20:36 <markuman[m]> I have to leave now. Bed time for my son
18:21:02 <abuzachis[m]> no worries! Thank you markuman, bye!
18:21:11 <abuzachis[m]> Yeah, for this one https://github.com/ansible-collections/community.aws/pull/1600
18:22:51 <abuzachis[m]> Do we want to set any timeline for amazon.aws 5.3.0?
18:23:19 <tremble> "Soon" ?
18:23:41 <tremble> Once they key fix is in?
18:24:03 <abuzachis[m]> Makes sense!
18:24:19 <abuzachis[m]> I guess the content we have is enough in any case!
18:24:57 <abuzachis[m]> Let's switch to amazon.aws 6.0.0 then
18:25:12 <abuzachis[m]> #topic: amazon.aws release 6.0.0 milestone
18:25:26 <abuzachis[m]> #info: https://github.com/ansible-collections/amazon.aws/pulls?q=is%3Aopen+is%3Apr+milestone%3A6.0.0
18:26:29 <abuzachis[m]> Anything specific we want to include in 6.0.0?
18:27:10 <tremble> There's a new ec2_instance pr
18:27:52 <tremble> Needs a little cleanup but it's ec2 "classic" networking related
18:29:18 <abuzachis[m]> There are also two PRs for the inventory plugin
18:29:42 <abuzachis[m]> https://github.com/ansible-collections/amazon.aws/pull/1365 and https://github.com/ansible-collections/amazon.aws/pull/1369
18:30:01 <tremble> Yeah, 65 at least
18:30:22 <abuzachis[m]> We should also have a look at this one https://github.com/ansible-collections/amazon.aws/pull/964
18:31:05 <tremble> Yeah that should be mostly ready, was just waiting on tests
18:31:40 <abuzachis[m]> ok, perfect!
18:31:49 <abuzachis[m]> Anything else?
18:33:42 <tremble> Think the other breaking changes already landed...
18:34:55 <abuzachis[m]> Yes, that seems.
18:36:19 <abuzachis[m]> If there's nothing else I will end the meeting and if something pops up we can discuss here.
18:36:29 <tremble> Sounds good to me
18:36:42 <abuzachis[m]> #endmeeting