Naming templates (#129)

* refactor to support custom naming templates (ref #126)

* cleaning Naming interface

* refactored for custom naming template

and initial set of unit tests

* more unit tests

* convert ARM template to use additional parameters

* rename to better convey

* fix ARM template sanity check

* editorconfig, attributes and using clean-up

* fixed implementation of FileNamingTemplates

added more argument validation
added unit tests

* Integration test for naming template feature

and some fixes
and some doc notes

* fix integration test cleanup

should be moved to a special test command

* factored out integration test cleanup

that is delete all azure resources except for the resource group

Author: giuliov

.editorconfig

@@ -0,0 +1,10 @@
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+insert_final_newline = true
+
+[**.md]
+indent_size = 2
+trim_trailing_whitespace = false

doc/command-examples.md

@@ -1,8 +1,31 @@
 # Sample Aggregator CLI usage
 
 run `aggregator-cli.exe` (Windows), `aggregator-cli` (Linux) or `dotnet aggregator-cli.dll` followed by the command and any option.
+
+
+### Options valid for all command
 All commands accept the `--verbose` option to print additional messages for troubleshooting.
 
+With `--namingTemplate`, you can specify affixes for all Azure resource that will be created or used.
+ follows
+
+```json
+{
+  "ResourceGroupPrefix": "aggregator-",
+  "ResourceGroupSuffix": "-sfx",
+  "FunctionAppPrefix": "fp",
+  "FunctionAppSuffix": "fs",
+  "HostingPlanPrefix": "hp",
+  "HostingPlanSuffix": "hs",
+  "AppInsightPrefix": "aip",
+  "AppInsightSuffix": "ais",
+  "StorageAccountPrefix": "strg",
+  "StorageAccountSuffix": "31415"
+}
+```
+
+If you use this, the `--resourceGroup` option is mandatory.
+
 
 ### Logon
 You are required to log into both Azure and ADO. The credentials are cached locally and expire after 2 hours. _(Replace the below asterisks `*` with valid values.)_
@@ -181,4 +204,4 @@ Runs existing rule in Azure, no change is sent to Azure DevOps thanks to the `dr
 invoke.rule --instance my7 --resourceGroup test-aggregator7  --name r1 --event workitem.created --account giuliovaad --project WorkItemTracking --workItemId 14 --verbose --dryrun
 ```
 If you want to see the log messages, run a `stream.logs` command in another window.
-This can be used (without the `dryrun` flag) to apply rules to existing work items.
+This can be used (without the `dryrun` flag) to apply rules to existing work items.