Mandar Kulkarni
Mandar Kulkarni
Hi @stefanhorning, thank you for working on this! Could you rebase your branch with `main` https://github.com/ansible-collections/community.aws? With recent merge of https://github.com/ansible-collections/community.aws/pull/1036, integration tests TIMED_OUT issue should be resolved now :)...
Thank you @stefanhorning, minor changes that are causing CI failure https://github.com/ansible-collections/community.aws/pull/831/files#diff-1a33a4359f835bab9c605061886c5d1bfb6d0d2eb377f1fbf8f19720360e476dR488-R490 ([create_update_delete.yml](https://github.com/ansible-collections/community.aws/pull/831/files#diff-1a33a4359f835bab9c605061886c5d1bfb6d0d2eb377f1fbf8f19720360e476d) Lines 488-490) should be something like ``` "output.mixed_instances_policy.launch_template.overrides | length == 2" "output.mixed_instances_policy.launch_template.overrides[0].instance_type == 't3.micro'" "output.mixed_instances_policy.launch_template.overrides[1].instance_type == 't2.nano'"...
@lkatalin #1037 should likely solve the issue.
> Could you also add a changelog fragment: https://docs.ansible.com/ansible/latest/community/development_process.html#community-changelogs? Added.
Hi @kdelee, I was trying to reproduce the issue, however ending up with unique UUIDs for instances. Has this issue been solved already? if not, would you please recommend steps...