Add missing spec reference in readme.md

[anton-evseev]

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

• I have reviewed the documentation for the workflow.
• Validation tools were run on swagger spec(s) and have all been fixed in this PR.
• The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

• Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
• adding/removing APIs.
• adding/removing properties.
• adding/removing API-version.
• adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

• If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
  Please follow the link to find more details on API review process.

[AutorestCI]

Automation for azure-sdk-for-python

Encountered a Subprocess error: (azure-sdk-for-python)

Command: ['/usr/local/bin/autorest', '/tmp/tmp4_2xp9om/rest/specification/network/resource-manager/readme.md', '--keep-version-file', '--multiapi', '--no-async', '--python', '--python-mode=update', '--python-sdks-folder=/tmp/tmp4_2xp9om/sdk/sdk', '[email protected]/[email protected]', '--version=preview']
Finished with return code -6
and output:

AutoRest code generation utility [version: 2.0.4283; node: v10.15.3]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest

There is a new version of AutoRest available (2.0.4407).
 > You can install the newer version with with npm install -g autorest@latest

   Loading AutoRest core      '/root/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4407)
   Loading AutoRest extension '@microsoft.azure/autorest.python' (4.0.70->4.0.70)
   Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.44->2.3.44)
Processing batch task - {"tag":"package-2019-09"} .

<--- Last few GCs --->

[57030:0x2b64cc0]    78286 ms: Mark-sweep 1375.4 (1447.2) -> 1362.0 (1449.2) MB, 2204.1 / 0.0 ms  (average mu = 0.165, current mu = 0.101) allocation failure scavenge might not succeed
[57030:0x2b64cc0]    80816 ms: Mark-sweep 1377.1 (1449.2) -> 1363.7 (1451.2) MB, 2169.8 / 0.0 ms  (average mu = 0.154, current mu = 0.142) allocation failure scavenge might not succeed


<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0x2e40c2c5be1d]
    1: StubFrame [pc: 0x2e40c2c2e742]
Security context: 0x1353a011e6e9 <JSObject>
    2: items [0x3c9972727de1] [/node_modules/@microsoft.azure/linq/dist/main.js:~59] [pc=0x2e40c3146bd5](this=0x3f00d92404e1 <Object map = 0x296e3fe8851>,source=0x2763f4d15091 <JSProxy>)
    3: visit(aka visit) [0x3f00d927b641] [/node_modules/@microsoft.azure/datastore/dist/json-pointer.js:~154] [pc=0x2e40c31231e6](this=...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
 1: 0x8dc510 node::Abort() [node]
 2: 0x8dc55c  [node]
 3: 0xad9b5e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
 4: 0xad9d94 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
 5: 0xec7bf2  [node]
 6: 0xec7cf8 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [node]
 7: 0xed3dd2 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [node]
 8: 0xed4704 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
 9: 0xed7371 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [node]
10: 0xea0466 v8::internal::Factory::AllocateRawArray(int, v8::internal::PretenureFlag) [node]
11: 0xea0cea v8::internal::Factory::NewFixedArrayWithFiller(v8::internal::Heap::RootListIndex, int, v8::internal::Object*, v8::internal::PretenureFlag) [node]
12: 0xea0dc7 v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [node]
13: 0x1136c88 v8::internal::Runtime_CreateJSGeneratorObject(int, v8::internal::Object**, v8::internal::Isolate*) [node]
14: 0x2e40c2c5be1d

[azuresdkci]

Can one of the admins verify this patch?

[AutorestCI]

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

[mmyyrroonn]

@number213 Hello. I have a question about this PR. Why does networkWatcherConnectionMonitorV1 not have a 2019-11-01 version?

[anton-evseev]

@myronfanqiu this API isn't supported beyond 2019-06-01. Eventually it will be replaced by V2 version
ccre-work it: @v-shhatt @solhaile