ansible-community / ansible-community/molecule-plugins
iam_instance_profile is set in wrong place
- Dominant language
- Python
- Stars
- 164
- Forks
- 113
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 1
Description
This PR
https://github.com/ansible-community/molecule-plugins/pull/164/files
[amazon.aws.ec2_security_group module](https://docs.ansible.com/ansible/latest/collections/amazon/aws/ec2_security_group_module.html#ansible-collections-amazon-aws-ec2-security-group-module) does not have `iam_instance_profile` parameter.
This parameter should be set in
https://github.com/ansible-community/molecule-plugins/blob/b48ead5d12d80eb90ead14f1958d0e9ef79b8752/src/molecule_plugins/ec2/cookiecutter/%7B%7Bcookiecutter.molecule_directory%7D%7D/%7B%7Bcookiecutter.scenario_name%7D%7D/create.yml#L203
as a part of [amazon.aws.ec2_instance](https://docs.ansible.com/ansible/latest/collections/amazon/aws/ec2_instance_module.html)
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect the EC2 scenario template at src/molecule_plugins/ec2/cookiecutter/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/create.yml, especially around line 203. Compare the parameters used by amazon.aws.ec2_security_group and amazon.aws.ec2_instance, then verify that iam_instance_profile is under the instance task and the generated create.yml remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100