-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
Convert AP-ALB tests to testinfra #44
Comments
fititnt
added a commit
that referenced
this issue
Dec 26, 2019
…/opt/alb/bin/tests on each node that is not running only on alb-minimal
fititnt
added a commit
that referenced
this issue
Dec 27, 2019
fititnt
added a commit
that referenced
this issue
Dec 27, 2019
…lb/info/ to allow tests know what to check
fititnt
added a commit
that referenced
this issue
Dec 27, 2019
This was referenced Jan 1, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is a fact that well written idempotent Ansible Roles/Playbooks are aready good for testing the infrastructure actual state. For just test without apply, there is even the Check Mode (“Dry Run”).
But here with AP-ALB is more complex than average individual Ansible Role, even when running in a single node. One of the implications of this is that, even if is just to check what ports are used by what service become important. We already have some drafts on
files/alb-cli-tools
but writing more complex shell scripts to do some quick testing may be less portable.Because of the Implementation of Ansible Molecule on AP-ALB & travis-ci integration #2, we're already ideally would need to create some tests to check if all is ok, so I will take the oportunity to already use Testinfra on more than just the continuos integration testing.
The text was updated successfully, but these errors were encountered: