New api version for redis 2018-03-01

[TimLovellSmith]

Fixes #1347. Redis RP now supports long-running delete operation with this api version.

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

• The title of the PR is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
• Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
• If applicable, the PR references the bug/issue that it fixes.
• Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

• I have read the contribution guidelines.
• My spec meets the review criteria:
  • The spec conforms to the Swagger 2.0 specification.
  • The spec follows the guidelines described in the Swagger checklist document.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.

[AutorestCI]

Automation for azure-sdk-for-go

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-go#1312

[AutorestCI]

Automation for azure-sdk-for-python

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-python#2091

[mcardosos]

Hello @TimLovellSmith !
Changes in the swagger itself look good. However there are some example validation errors

[AutorestCI]

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

[tombuildsstuff]

hey @TimLovellSmith

Out of interest does this API version include fixes for #1347 and #1499?

Thanks!

[TimLovellSmith]

@tombuildsstuff RE #1347 yes, it is intended it will (api spec is done here, but server fixes are not yet rolled out). RE #1499 no, although I believe that is purely a server bug and won't require a new api version.

If #1499 is still happening for you could you get me some more details in that bug's thread? I've had trouble tracking down what is going on there.

[mcardosos]

@TimLovellSmith There are still issues. Probably an invalid JSON.
On the other hand, we had some recent issues with CI, I would recommend to rebase the branch.

[jhendrixMSFT]

@AutorestCI rebuild azure-sdk-for-go

[jhendrixMSFT]

@AutorestCI rebuild azure-sdk-for-go

[TimLovellSmith]

@mcardosos This PR is now ready to be accepted!
/cc @jhendrixMSFT @tombuildsstuff

[mcardosos]

Great!
@TimLovellSmith question, is this already deployed?

[TimLovellSmith]

@mcardosos
Yes, you can now call the new api-version in public Azure
/cc @tombuildsstuff

[AutorestCI]

Automation for azure-libraries-for-java

The initial PR has been merged into your service PR:
Azure/azure-libraries-for-java#338

[jhendrixMSFT]

@AutorestCI rebuild azure-sdk-for-go

[lmazuel]

@AutorestCI rebuild azure-sdk-for-go

[lmazuel]

@AutorestCI rebuild azure-libraries-for-java