17:30:11 <jillr> #startmeeting Ansible AWS Community Meeting
17:30:11 <zodbot> Meeting started Thu Sep 28 17:30:11 2023 UTC.
17:30:11 <zodbot> This meeting is logged and archived in a public location.
17:30:11 <zodbot> The chair is jillr. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
17:30:11 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:30:11 <zodbot> The meeting name has been set to 'ansible_aws_community_meeting'
17:31:03 * ansible_relay 15mchappell:matrix.org> waves
17:31:28 <jillr> ah I don't know how to chair people across the relay!  :)
17:32:04 <jillr> well I guess we'll continue on as best we can?
17:32:28 <jillr> #topic Promote some modules to supported in 7.0.0
17:33:15 <jillr> I think we've agreed to migrate the sts and iam_* modules from c.aws, does anyone disagree about that?
17:33:22 <jillr> are there any other modules that I missed?
17:33:50 <ansible_relay> 15mchappell:matrix.org> Are we going to try and keep some of the history?  Several modules have been merged with history now only available in community.aws
17:34:17 <jillr> I thought we were keeping the history, do you know which PRs those were?
17:35:37 <ansible_relay> 15mchappell:matrix.org> #1762 #1760 #1755
17:35:46 <jillr> ta.  I'll follow up on those.
17:36:25 <ansible_relay> 15mchappell:matrix.org> 1755 was my fault (I added mergeit and forgot) we'd need a manual merge/config change
17:36:40 <ansible_relay> 15mchappell:matrix.org> We still have a couple pending though.
17:36:51 <jillr> we can always revert and redo
17:37:38 <ansible_relay> 15mchappell:matrix.org> Might be worth it.
17:38:14 <jillr> mgraves thinks we may have squash merged instead of rebase merge on those, which might be the issue
17:38:27 <ansible_relay> 15mchappell:matrix.org> yup
17:38:41 <ansible_relay> 15mchappell:matrix.org> I think we let mergeit do its default thing
17:39:07 <ansible_relay> 02Helen Bailey> maybe we could make a note about that in the el_grandiose_module_promoter repo as a reminder in future?
17:39:17 <jillr> we need to document that the process for this is "DM jill for a manual merge" I guess
17:39:28 <jillr> super scalable, but it works?  :D
17:40:11 <ansible_relay> 15mchappell:matrix.org> Works for now.  Maybe one day it'll be one big repo...
17:41:07 <jillr> On the topic, are there any other modules to promote for 7.0.0?
17:42:39 <ansible_relay> 12mgraves> alina had suggested s3_bucket_info
17:43:15 <ansible_relay> 12mgraves> there's also iam_saml_federation, but I am not sure how we would test that
17:43:37 <jillr> do we have a ticket or PR for s3_bucket_info?
17:43:56 <ansible_relay> 12tremble> IMO that's a question for your team.  I wouldn't want to demand you take on a different support role.
17:43:56 <ansible_relay> 12tremble> That said s3_object_info possibly.  (just for consistency) and possibly aws_region_info
17:43:57 <ansible_relay> 12mgraves> not yet, I don't think
17:44:13 <jillr> We'd need a ton of unit test coverage for iam_saml_federation, which I think we don't have
17:44:41 <jillr> and we'd still have trouble supporting the functionality
17:45:11 <ansible_relay> 12tremble> Really hard to test, I wrote the module and wouldn't really want to go there with iam_saml_federation.
17:45:15 <jillr> the s3 modules and aws_region_info make more sense to me
17:45:25 <jillr> tremble: ack
17:45:28 <ansible_relay> 12mgraves> aws_region_info seems reasonable. s3_object_info is already in supported collection
17:46:23 <jillr> given the short timeline we're looking at (which is next topic) is that too many modules all for one release? or do we think it's reasonable to add the s3 modules and aws_region_info?
17:46:49 <ansible_relay> 12mgraves> are you talking about all the remaining s3 modules in community?
17:46:52 <jillr> We'd probably have to start executing the migration work in the next week
17:46:55 <ansible_relay> 12mgraves> I think that would be too many
17:46:59 <jillr> Sorry no, just the ones mentioned above
17:47:03 <ansible_relay> 12tremble> aws_region_info is quick and easy,
17:47:17 <ansible_relay> 12mgraves> aws_region_info and s3_bucket_info we can do
17:47:26 <ansible_relay> 12tremble> Oh, I got s3_bucket_info and s3_object_info mixed up
17:49:13 <ansible_relay> 12tremble> Actually iam_saml_federation we've already got integration tests for.
17:49:20 <jillr> So we add aws_region_info and s3_bucket_info to the list of modules we are already working on migrating, but not any other s3 modules and not iam_saml_federation.  Agreed?
17:50:12 <jillr> I think we'd still want to look at iam_saml_federation in more depth before extending downstream support for it
17:50:36 <ansible_relay> 12tremble> Fair enonugh
17:50:58 <ansible_relay> 12tremble> I'm not in a hurry to see any others moved :)
17:52:09 <jillr> moving forward then
17:52:15 <jillr> #topic 7.0.0 release planning - target November?
17:52:44 <jillr> I think the question here is if we want to bump the 7.0.0 release date to target the ansible9 release date, is that right?
17:53:11 <jillr> or rather, to target the cutoff date for collections to be included in ansible 9
17:55:32 <jillr> I recall that there was some discussion in channel about this maybe last week, was there already a decision made?
17:55:33 <ansible_relay> 12tremble> Yeah, it'd be nice to have a nice new version available for 7.0.0
17:55:50 <ansible_relay> 12tremble> Err Ansible 9.0
17:56:55 <ansible_relay> 12mgraves> there was a potential argument for holding off until december so we could drop a bunch of deprecations, but I think ansible 9 is the more compelling argument
17:57:14 <ansible_relay> 12mgraves> the current proposal is nov 2
17:57:37 <jillr> okay thanks, I was still looking in scrollback
17:58:04 <ansible_relay> 12tremble> I think there was more discussion inside the team rather than on IRC
17:58:08 <jillr> Does anyone disagree with targetting Nov 2 for the 7.0.0 amazon.aws and c.aws releases?
17:58:44 <jillr> Or was that date only for amazon.aws?
17:59:18 <ansible_relay> 12tremble> We'll want the two ready really close to each other, would be silly if we have amazon.aws 7 and community.aws 6
17:59:34 <jillr> totally, just making sure I understand the plan
18:00:43 <ansible_relay> 12tremble> Migrations and isort would be the only things pending.  I think we'll menage it...
18:02:23 <ansible_relay> 12tremble> Speaking of isort - who would I need to poke about https://github.com/ansible-network/github_actions/pull/124/ ?
18:03:45 <jillr> I think that just needs someone to click merge,  I can look after this meeting
18:03:57 <ansible_relay> 12mgraves> that's a backwards compatible change, right?
18:04:04 <ansible_relay> 12tremble> I believe so...
18:05:25 <ansible_relay> 02Helen Bailey> yeah, it should be
18:06:28 <jillr> we'll get the isort PR merged (or else feedback provided) asap
18:06:41 <ansible_relay> 12tremble> WFM
18:06:53 <jillr> For release, I'll take a lack of dissent for agreement and we'll target Nov 2 for both collections to be prepared
18:08:30 <jillr> #topic Community forum https://forum.ansible.com/
18:08:50 <jillr> hopefully folks have seen the announcements about the new discourse forum.
18:09:11 <ansible_relay> 12tremble> \o/  New shiny thanks to the wonderful community team.
18:09:29 <jillr> there is already an AWS tag available if people want to follow topics that get tagged with that, is there anything else we could do as the AWS community?
18:09:51 <jillr> For example, DaWGs has moved their meeting agendas from github issues to the forum:  https://forum.ansible.com/t/documentation-working-group-agenda/153/2
18:10:47 <jillr> It would probably help get people more involved if they didn't have to dig around in the right repos to find the meeting info
18:11:14 <ansible_relay> 02Helen Bailey> ooh I like that
18:11:15 <ansible_relay> 12tremble> I'd like to try moving the agenda.  didn't want to take it into my own hands though.
18:11:29 <jillr> tremble: heh - same!
18:11:41 <ansible_relay> 12tremble> Would be really nice if more of us can update/complete agenda items
18:12:09 <jillr> +1
18:12:22 <ansible_relay> 02Helen Bailey> I don't mind figuring out how to do that. would help me learn how to use the forum
18:13:14 <jillr> I think we can probably just duplicate the setup that the Docs folks are using, since they seem to have it working pretty well
18:13:23 <jillr> thanks Helen!
18:14:50 <ansible_relay> 02Helen Bailey> np
18:16:42 <jillr> #topic open floor
18:16:53 <jillr> Any other things to discuss?
18:18:06 <ansible_relay> 12tremble> next stable-6 releases?
18:18:23 <jillr> #topic stable-6.next
18:19:12 <ansible_relay> 12tremble> https://github.com/ansible-collections/amazon.aws/tree/stable-6/changelogs/fragments Looks like we have enough to be worth it.
18:19:57 <ansible_relay> 12tremble> Any more "urgent" PRs to pull in ?
18:20:29 <jillr> I'm not aware of any, mgraves do we have anything?
18:20:53 <ansible_relay> 12mgraves> I don't think so
18:25:20 <jillr> Are we in a position to release next week then?
18:25:39 <jillr> I assume that's what we're targetting for the regular release cadence
18:26:01 <ansible_relay> 15mchappell:matrix.org> Yeah, should be
18:27:26 <jillr> I think we're still planning to do a key rotation on the galaxy keys with the amazon.aws release, I'll double check with abuzachis (since I have the keys)
18:28:08 <jillr> We need to rotate them on zuul so it will affect all collections using zuul, but we figured this was a good collection to plan against
18:30:33 <ansible_relay> 15mchappell:matrix.org> I thought that was done with the last release
18:31:08 <jillr> I think we had planned to and then time and planning got away from us
18:34:59 <jillr> are we set for next week then, and if possible the team will coordinate amongst ourselves to do the key roation but not block on it?
18:36:44 <jillr> (the key rotation is basically staging a PR for zuul, and reverting it if things blow up.  this is a proactive rotation, we're not expiring, so we can just back out the change if needed)
18:37:48 <ansible_relay> 15mchappell:matrix.org> WFM
18:39:18 <jillr> sounds like a plan then
18:39:25 <jillr> any last topics before we close out?
18:42:20 <jillr> #endmeeting