We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Together with the upgrade to Molecule v3 the EC2 provider now was separated from the core Molecule project/providers into https://github.com/ansible-community/molecule-ec2, which isn't in a working state right now (see ansible-community/molecule-ec2#1). When there's a fix, we can activate our AWS EC2 tests again.
The text was updated successfully, but these errors were encountered:
#45: Prepare for usage of the new molecule-ec2 module & updated depen…
5a34a1c
…dencies accordingly. But we have errors, see ansible/molecule#2946, https://github.com/ansible-community/molecule/pull/2869/files, ansible-community/molecule-ec2#34 (only merged 3 days ago). Also removed CircleCI for now, since the goal is to simply run every scenario on GHA.
No branches or pull requests
Together with the upgrade to Molecule v3 the EC2 provider now was separated from the core Molecule project/providers into https://github.com/ansible-community/molecule-ec2, which isn't in a working state right now (see ansible-community/molecule-ec2#1). When there's a fix, we can activate our AWS EC2 tests again.
The text was updated successfully, but these errors were encountered: