-
Notifications
You must be signed in to change notification settings - Fork 144
Amazon Web Services Working Group Agenda - 2022 #654
Comments
Possible discussion points:
PRs for next community release ?
Possible also: |
This comment was marked as off-topic.
This comment was marked as off-topic.
backporting lifetime
|
I probably won't make the next meeting. for community.aws we can set any support cycle we like, for amazon.aws though we need to have the branches for anything that we still provide downstream Red Hat support for. stable-1 is still eligible for security fixes (but not feature backports). |
ansible-collections/community.aws#1064
|
@jillr Is 1.x eligible? I thought Ansible 2.9 had the modules still in ansible/ansible, so while we might need to backport over to the old repo but not necessarily into a 1.x release. Which supported release has 1.x rather than 2.x+ ? |
|
|
AAP 2.1 included supported Execution Environment version 1.1, with amazon.aws 1.5 |
|
does it break backwards compatibility, when the return values are not documentated yet? :) imo it must be a general compliance that _info modules returns snake_case.
|
IMO, yes. Our docs have historically been rather lacking in completeness and accuracy when it comes to the return values, so consumers of modules have had no choice but to rely on what's been historically returned. One work around can be to add a new return value and return the new data structure in there. |
|
|
Minutes from the May meeting: Minutes (text): https://meetbot.fedoraproject.org/ansible-aws/2022-05-26/ansible_aws_community_meeting.2022-05-26-17.33.txt All topics up to this point were covered. |
As we make decisions that effect the amazon.aws and community.aws repos, we could adopt ADRs (or something similar) in these repos too. Things like the recent conversations about returns values, in addition to being recorded in the documentation, could also be codified as ADRs in the repo.
|
I'm a generally +1
In general I'd suggest either amazon.aws or something separate, and we move the WG agenda there too.
I think it would be valuable to try and capture the decisions we've made in the past, so at least some of the background is recorded "somewhere". |
|
|
|
This is continued in #687. From now on we will have one issue per year. |
Please leave a comment regarding any agenda item you wish to discuss. If you don't show up for the meeting, your item will be skipped. If your IRC nick is different from your Github username, leave that as well.
See https://github.com/ansible/community/blob/master/meetings/README.md for the schedule
Once an item has been discussed it should get checked off.
If you just want reviewers for your contribution join us on:
#ansible-aws
The text was updated successfully, but these errors were encountered: