Molecule EC2 is designed to allow use of AWS EC2 for provisioning of test resources.
Quickstart
Installation
pip install molecule-ec2
Create a scenario
With a new role
molecule init role -d ec2 my-role
This will create a new folder my-role containing a bare-bone generated role like you would do with ansible-galaxy init command. It will also contain a molecule folder with a default scenario using the ec2 driver (using ansible community.aws.ec2_instance collection). Install the collection using ansible-galaxy install -r test_requirements.yml.
In a pre-existing role
molecule init scenario -d ec2
This will create a default scenario with the ec2 driver in a molecule folder, located in the current working directory.
Example
This is a molecule.yml example file
dependency:
name: galaxy
driver:
name: ec2
platforms:
- name: instance
image_owner: 099720109477
image_name: ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-*
instance_type: t2.micro
vpc_subnet_id: <your-aws-vpc-subnet-id>
tags:
- Name: molecule_instance
provisioner:
name: ansible
verifier:
name: ansible
All you need to do is fill in the subnet-id you want to create your test instance into. Then run
molecule test
Documentation
Read the documentation and more at https://molecule.readthedocs.io/.
Get Involved
Join us in the #ansible-molecule channel on Freenode.
Join the discussion in molecule-users Forum.
Join the community working group by checking the wiki.
Want to know about releases, subscribe to ansible-announce list.
For the full list of Ansible email Lists, IRC channels see the communication page.
License
The MIT License.
The logo is licensed under the Creative Commons NoDerivatives 4.0 License.
If you have some other use in mind, contact us.
Metadata
Release files for molecule-ec2 0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| molecule-ec2-0.4.tar.gz | 20.8 kB | Without provenance | Details for molecule-ec2-0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| molecule_ec2-0.4-py3-none-any.whl | Python 3 | none | any | Details for molecule_ec2-0.4-py3-none-any.whl |
Total release size: 42.5 kB
Release files / molecule-ec2-0.4.tar.gz
| Download URL | molecule-ec2-0.4.tar.gz |
|---|---|
| Size | 20.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7524a6c4a4e3d384fa63be4275dbcda41eb24b130a08714428deb30f1a014b5
|
|
BLAKE2b-256 checksum How to use checksums |
7ea4d2ad667fba09136e44ea3d5acd5d8a1c5a58edaa6d0e82e69386eb6e197e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.9
|
Release files / molecule_ec2-0.4-py3-none-any.whl
| Download URL | molecule_ec2-0.4-py3-none-any.whl |
|---|---|
| Size | 21.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
768ac602009f8d454a2cc2ba4afc7079d7ac1a945b01d9011a6150d74a6ba83e
|
|
BLAKE2b-256 checksum How to use checksums |
2e1fd7e20178ab304e534ac9c2ce4d7b0a6f302975e5ea760a03426e1eaf697e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.0 importlib_metadata/4.8.2 pkginfo/1.8.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.9
|
Security for molecule-ec2 0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.