Skip to content
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

Naming convention #64

Open
cktricky opened this issue Sep 26, 2018 · 0 comments
Open

Naming convention #64

cktricky opened this issue Sep 26, 2018 · 0 comments

Comments

@cktricky
Copy link
Collaborator

Making sure to leave a note re: @carnal0wnage and I's discussion last night re: conventions.

Background: Now that we have both GCP and AWS functionality we might have a situation where a method is named the same between the two. So imagine a GCP method named module_do_something and an AWS module named module_do_something. This would be less than ideal.

So going forward, our thoughts were to do one of the following:

  • module_aws_do_something and module_gcp_do_something (prepending module_<cloudservice

  • aws/module_do_something and gcp/module_do_something

Anyways, recording this conversation in case we need to figure out later why we chose whatever convention we go with (which - I believe we're leaning towards module_aws_ or module_gcp_ 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant