Specify a platform in the Molecule test configuration

[mcdonnnj]

💡 Summary

We should consider specifying a platform in our Molecule configurations.

Motivation and context

This would both allow us to test multiple platforms in a given configuration (amd64 and aarch64/arm64 for example) as well as ensure that the desired platform is tested regardless of the underlying hardware. The former would allow us to ensure our roles are compatible with AWS Graviton2-based instances for our own purposes. The latter would help ensure that with the rollout of Apple silicon (ARM) that the amd64 platform is still tested explicitly.

Implementation notes

Support for this was added in ansible-community/molecule-docker#122 which was included in molecule[docker] v2.0.0.

Acceptance criteria

• Molecule testing is enabled for non-amd64 platforms.
• Molecule testing works even when run on non-amd64 hardware.

[jsf9k]

@mcdonnnj - do you think that the arm64v8 platform should be handled as a separate scenario, or should we double the number of platforms served by the default scenario?

[mcdonnnj]

@jsf9k I think increasing the number of platforms served by the default scenario makes the most sense for this specific change. However, I'm not opposed to treating different underlying architectures as different scenarios if you think that would be a better implementation.

[jsf9k]

@jsf9k I think increasing the number of platforms served by the default scenario makes the most sense for this specific change. However, I'm not opposed to treating different underlying architectures as different scenarios if you think that would be a better implementation.

I will try to include them in the default scenario, but there may not be sufficient disk space on the GH Actions runners for that.