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

Contradictory naming convention #371

Open
vanillajonathan opened this issue Mar 23, 2020 · 1 comment
Open

Contradictory naming convention #371

vanillajonathan opened this issue Mar 23, 2020 · 1 comment
Labels
documentation Applies to documentation and diagrams

Comments

@vanillajonathan
Copy link

The Cobalt wiki recommends the abbreviation "asp" for App Service Plan.
https://github.com/microsoft/cobalt/wiki/Azure-Services-Naming-Convention#resource-type-abbreviations

However the Cloud Adaption Framework recommends the name prefix "plan-" for App Service Plan.
https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/naming-and-tagging#compute-and-web

@TechnicallyWilliams TechnicallyWilliams added the documentation Applies to documentation and diagrams label May 9, 2020
@thiagopesquisa42
Copy link

thiagopesquisa42 commented Nov 17, 2022

I have found the same issue in another Azure Resource: Application Insights

This Cobalt wiki suggests "ai",
but Microsoft´s Cloud Adaption Framework suggests "appi".

Naturally and probably there are more incongruencies...

Any update on this? This seems so simple to solve and important.
Both sources (Cobalt and Cloud Adaption Framework) are under Microsoft's name, so they are causing confusion.

I suggest the following solution:
I think the Cloud Adaption Framework seems more like an official documentation for these abbreviations suggestions,
so maybe this Cobalt wiki should at least inform that:
".... Although this project uses its own abbreviations convention, there is another option too, listed in Microsoft´s Cloud Adaption Framework"

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

No branches or pull requests

3 participants