Comments (4)
Thank you for the added thoughts on this, @paraenggu .
We're planning to retire the file, and we'll then also remove the references from the content - we'll get this done asap to avoid further confusion, and we'll rely on the docs as the source of truth.
Thanks!
Tobias.
from cloudadoptionframework.
thanks for your feedback on this issue @Zimmergren
Are you relying on the Excel file, specifically, or would you rather be able to keep up to date with the official docs, which are updated and maintained regularly? If I can understand how the Excel file is being used, we might be able to justify looking at an update. The way we see it right now, we're more likely to discontinue the Excel file and only keep the docs.
I originally opened this issue after following Step 5: Establish naming and tagging standards across the portfolio of the foundational alignment, which links to this file:
- Populate the naming and tagging conventions tracking template to track decisions.
The same page also links to the initial-decisions-checklist which also contains a link to this template.
I don't directly relay on it, but found it practical to have a consolidated document which helps one to define the naming and tagging conventions and gather inputs from the involved people.
It's certainly OK, to discontinue the file and refer to the online docs, but I guess others will also end there as long as it's linked on that page and within that document.
from cloudadoptionframework.
In the "intro and components" sheet most resource name prefixes include a dash (-) as the last character, while some are lacking one (e.g. stor, ssimp, dls, dla and pbiemb). Do they use a different schema intentionally and if yes, is there a technical limitation or similar to it, which could be noted as a comment in the sheet?
I assume this is because of the character limit (24 IIRC) for storage based services, which have a global scope, thus saving some chars by not using the dashes in the naming scheme.
In general it would be nice to get answer on this topic, as I saw these stuff as well and had to fix it manually.
from cloudadoptionframework.
Thank you for reporting this, @paraenggu.
The linked file is over 4 years old, and drifted out of sync with the source of truth (CAF docs) - I would recommend checking out the official docs:
Are you relying on the Excel file, specifically, or would you rather be able to keep up to date with the official docs, which are updated and maintained regularly? If I can understand how the Excel file is being used, we might be able to justify looking at an update. The way we see it right now, we're more likely to discontinue the Excel file and only keep the docs.
cc @shurik-io
from cloudadoptionframework.
Related Issues (20)
- Import Custom Components from JSON file HOT 2
- Specified delimeter is not allowed for "Compute/virtualMachines - Windows (vm)" HOT 4
- AzNamingTool - New feature request: Add componet of type free text similar with instances HOT 2
- AzureNamingTool: Globally optional in version 2.5.0 does not apply when generating multiple resource type names HOT 2
- AzNaming Tool - Option to return also expanded resourceName using API HOT 3
- AzNamingTool - Unable to generate name using rest api for optional custom component HOT 2
- When Running the Command docker build -t azurenamingtool . from Linux Server an Error Showed up like nu1301 unable to load the service index for source HOT 6
- How to Make AzureNamingTool to Listen HTTPS Port HOT 8
- Assistance with hosting AzNamingTool as standalone in IIS HOT 10
- Backing up all configuration and data from AzureNamingTool HOT 2
- AzNamingTool - New feature - ReadOnlyApiKey HOT 1
- This repo is missing important files
- HTTP ERROR 500 HOT 1
- Inconsistent Bootstrap reference HOT 2
- Generate screen autocomplete HOT 1
- Validate resource names HOT 1
- Is there a way of auto using the next instance number available HOT 4
- Error while updating filepath parameter [azure-virtual-machine-cost-estimator.pbix] HOT 3
- Cannot access blob storage in azure-virtual-machine-cost-estimator.pbix HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cloudadoptionframework.