request: rename all providers to match real world

[systemcrash]

Working on PR #2197 raised the question.

I prefer snake_case for the naming.

[tlimoncelli]

rename them where? Rename the identifier ("GCLOUD", "ROUTE53"), the directory (providers/gcloud), or the documentation TOC entries?

[systemcrash]

All of the above. At least so everything is synchronized. I'd considered putting each provider markdown in the provider folder so there's only 1 source tree for adding a provider, but perhaps this creates problems when building/copying the docs and new record types would probably seem like a weird exception if it wasn't handled similarly.

…

On Sun, 26 Mar 2023 at 14:57, Tom Limoncelli ***@***.***> wrote: rename them where? Rename the identifier ("GCLOUD", "ROUTE53"), the directory (providers/gcloud), or the documentation TOC entries? — Reply to this email directly, view it on GitHub <#2233 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE6DUPNMI3EABQMK77BITDW6A4KDANCNFSM6AAAAAAWHVCRSE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[tlimoncelli]

Rejected.

This would break all existing configurations for no other reason than "I prefer snake_case for the naming".

Please use the issues feature to file bugs and feature requests. This is neither.

[systemcrash]

Actually, as expressed in the auto TOC PR, the hope was to have all providers in snake_case so that TOC name printing would be reasonably predictable and elegant.

[tlimoncelli]

I apologize for the abrupt issue closure. That was rude of me.