Alexander Sehr

Hey @itpropro, great suggesstion and it couldn't be more current - in a way. A few thoughts: - We actually do have a Pull Request open by @BernieWhite (#161) -...

I know this does not answer all your questions just yet - but I hope things get clearer once we get closer to the first ported modules. And then ideally...

A couple comments from my side: - We're currently using Pester 'only' for our Unit Tests (i.e., static validation) to make sure that e.g. the ReadMe is correctly formatted, the...

Hey @itpropro, we're currently working on the [implementation](https://github.com/Azure/ResourceModules/pull/1787) that we'll start merging once the upcoming September release 0.7 is out.

> Indexing policy does not work with some specific capabilities (e.g. serverless) and with all database types (e.g. gremlin). We should wait until the PR #1566 is done and then...

Hey @MichaelJRogersGM, I just tested it with the default `parameters.json` with the following output: ``` PS CARML> . "c:\testLocal.ps1" VERBOSE: Using local tokens [namePrefix] VERBOSE: Deploy module [configurationStores] with parameter...

Suggestion: We could implement 2 consecutive deployments to catch these kind of errors. However, if we implement multiple pipeline runs to catch these kind of issues we have to be...

Regarding the issue itself we might need to use `union()` to not specify the HNS parameter at all (if it is not allowed to even use `null`).

We should probably also re-evalute the implementation to make sure everything is there (before we roll changes out on-scale)

Agreed. A benefit I see with the initial suggestion is that it's not actually necessary to 'publish' a readme. The issue would instead be solved by simply maintaining the table...