ansible-community / ansible-community/molecule-plugins
Instances are created without custom volumes
- Dominant language
- Python
- Stars
- 164
- Forks
- 113
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 1
Description
https://github.com/ansible-community/molecule-ec2/blob/08e1e57bff0d77e8100570e6d9b782171e831dc2/molecule_ec2/cookiecutter/%7B%7Bcookiecutter.molecule_directory%7D%7D/%7B%7Bcookiecutter.scenario_name%7D%7D/create.yml#L74 uses lowercase *volumes* field name, however molecule [schema](https://github.com/ansible-community/molecule/blob/52faa6647f2297f9a8f75dcc751299528ebadf64/src/molecule/data/molecule.json#L294) uses *volumes* for Docker volumes, ec2 volumes use an uppercase *Volumes* field. As a result that field never gets merged into instance config.
Attempt to name the field *volumes* instead of *Volumes* causes a schema validation error
Contributor guide
No contributing guide indexed for this repository
Research direction
Inspect the referenced create.yml line 74 and compare its volumes field with the EC2 schema in src/molecule/data/molecule.json around line 294. Trace how the instance configuration is merged and validated; done means custom EC2 volumes are retained without triggering schema validation errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, python
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100