Adding missing tag required by network release

[zikalino]

I got request to release network tag 2019-07-01, but appropriate definitions were missing from readme.python.md

[openapi-sdkautomation]

In Testing, Please Ignore

[Logs] (Generated from 1da3599, Iteration 2)

.NET: test-repo-billy/azure-sdk-for-net [Logs]

• Package generation in progress.

Python: test-repo-billy/azure-sdk-for-python [Logs]

• Package generation in progress.

Java: test-repo-billy/azure-sdk-for-java [Logs]

• Package generation in progress.

Go: test-repo-billy/azure-sdk-for-go [Logs]

• Package generation in progress.

JavaScript: test-repo-billy/azure-sdk-for-js [Logs]

• Package generation in progress.

Ruby: test-repo-billy/azure-sdk-for-ruby [Logs] [Diff]

• azure_sdk [Logs] [Instructions]
  • azure_sdk-0.19.7.gem

[AutorestCI]

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

[AutorestCI]

Automation for azure-sdk-for-python

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

Command: ['/usr/local/bin/autorest', '/tmp/tmp_4iyqbbi/rest/specification/network/resource-manager/readme.md', '--keep-version-file', '--multiapi', '--no-async', '--python', '--python-mode=update', '--python-sdks-folder=/tmp/tmp_4iyqbbi/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
   Loading AutoRest core      '/root/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4399)
   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-08"} .

<--- Last few GCs --->

[13512:0x40b5cc0]    78961 ms: Mark-sweep 1378.7 (1425.1) -> 1378.4 (1425.6) MB, 1264.2 / 0.0 ms  (average mu = 0.097, current mu = 0.010) allocation failure scavenge might not succeed
[13512:0x40b5cc0]    80240 ms: Mark-sweep 1379.2 (1425.6) -> 1378.9 (1426.1) MB, 1276.1 / 0.0 ms  (average mu = 0.051, current mu = 0.002) allocation failure scavenge might not succeed


<--- JS stacktrace --->

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

    0: ExitFrame [pc: 0xfb4cda5be1d]
Security context: 0x13851539e6e9 <JSObject>
    1: ParseNodeInternal(aka ParseNodeInternal) [0x105ee4d9e091] [/root/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core/dist/lib/ref/yaml.js:~86] [pc=0xfb4ce1301ff](this=0x3dac8b9826f1 <undefined>,yamlRootNode=0x3e76c1582a81 <Object map = 0x21040114d7e1>,yamlNode=0x29cb8a13b599 <Object map = 0x210401122f99>,onErro...

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: 0xea07f4 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [node]
11: 0x114018e v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [node]
12: 0xfb4cda5be1d

[azuresdkci]

Can one of the admins verify this patch?

[anton-evseev]

To avoid opening multiple PRs and having conflicts later, I pushed commit to add tags for 2019-08 to this PR. Hope you don't mind, Zim.