Hello list,
I notice the Rackspace modules are prefixed with “rax”. However, other providers are more complicated:
- AWS modules mostly have an “ec2” prefix. Why “ec2”, and not “aws”? Why do some AWS modules start with “ec2”, but others have no prefix, e.g. “s3”?
- Openstack modules have no consistent prefix at all.
Is this intentional, or the result of organic growth?
Mostly because this is how they are done originally, though I don’t really think they are wrong. ec2 is part of AWS, s3 is a different part, route53 is a third part.
aws_ec2_foo could have been a thing, but that’s a little verbose.
The easiest thing to do here in the future is probably to add a subcategory for the module docs generator, as we will not be supporting alias names or breaking existing modules.