ec2_platform: Allow internal communication within test security group
#11
Labels
enhancement
New feature or request
Comments
syndr
added a commit
that referenced
this issue
Jan 23, 2025
* Rename components for influxdata namespace * Fix collections template, add latest tag (#1) * Fix collections template * Add workflow for generating 'latest' tag * Update docs (#2) * Add testing for init role * Fix license * Disable release workflow * Fix running multiple platforms, support ubuntu for testing Fix the `docker_platform` role so that it works correctly when more than one platform is specified in molecule.yml. Add more useful output to container creation steps (`docker_platform`) Fix docker_platform to work with debian-based systemd images Support ubuntu for testing workflow * Replace chicken with egg Fixes in this devel branch are needed for it to run its own internal tests. Will need to create another PR after current changing collection version back to main after these fixes are merged. * Fix typo * Use 'latest' for version -- makes way more sense * Only push to Galaxy on mainline release * Fix namespace * Merge internal branch updates Amazon EC2 test scenario Refactoring of Molecule tests Lots of other things... * Fix build CI, docker_platform, bump version * Dynamically generate branch tag * Fix CI execution * Only deploy on successful build, allow 'degraded' systemd status * Refactor branch tag CI step * Bump version to 1.5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The security group created for test instances should explicitly allow internal communication between instances -- this will handle the need for clustered communication for multi-node tests.
See also:
ec2_platform: Named security groups are not unique to job runs #8The text was updated successfully, but these errors were encountered: