Open alinabuzachis opened 1 week ago
cc @ansible-collections/cloud @tremble @markuman
My suggestions:
~AuthN related:~
Either general "Autoscaling" pieces:
Or Getting us closer to being able to set up a "base" AWS environment through amazon.aws:
@alinabuzachis @GomathiselviS opened PRs for migrating elb_classic_lb_info as discussed on slack, it already has a jira as well https://github.com/ansible-collections/amazon.aws/pull/2272 https://github.com/ansible-collections/community.aws/pull/2135 cc @tremble
@mandar242 @GomathiselviS I suggest developing a plan first and understanding whether any of the proposed modules can also be promoted. In the past, we agreed to move modules from c.aws to a.aws as blocks (as many as possible for each major release) and not as a single promotion per major release.
Getting us closer to being able to set up a "base" AWS environment through amazon.aws:
"base" is difficult to define. Is it just network, servers and dns?
Here is a proposal with some potential modules to be promoted from community.aws.
elb_classic_lb_info autoscaling_group_instance_refresh(_info) sts_session_token (pairs nicely with sts_assume_role) secretsmanager_secret (pairs nicely with the lookup module) ssm_parameter (pairs nicely with the lookup module)
I'm fine with those.
should we include the following?
community.aws.ec2_transit_gateway
community.aws.ec2_transit_gateway_info
community.aws.ec2_transit_gateway_vpc_attachment
community.aws.ec2_transit_gateway_vpc_attachment_info
Summary
Here is a proposal with some potential modules to be promoted from community.aws.
Let's review this list and possibly add more if you think so.
Issue Type
Feature Idea
Component Name
several
Additional Information
Code of Conduct