Add import to the JSON Web Key Operations

[vakkinep]

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.

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[openapi-sdkautomation]

azure-sdk-for-java

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

[openapi-sdkautomation]

azure-sdk-for-net

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

[openapi-sdkautomation]

azure-sdk-for-python

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

[openapi-sdkautomation]

azure-sdk-for-js

No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[openapi-sdkautomation]

azure-sdk-for-go

️✔️ succeeded [Logs] [Expand Details]

• ️✔️ Generate from 731eb43 with merge commit 2e34e5f7380d8d6c5b24a0d83fd0e6161554851e. SDK Automation 13.0.17.20191226.1
• ️✔️keyvault/2015-06-01 [Logs]  [Preview SDK Changes]
  • keyvault.2015-06-01.zip
• ️✔️keyvault/2016-10-01 [Logs]  [Preview SDK Changes]
  • keyvault.2016-10-01.zip
• ️✔️keyvault/v7.0 [Logs]  [Preview SDK Changes]
  • keyvault.v7.0.zip

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[amitbapat]

Looks good.

[schaabs]

@heaths could you take a look at this and see how it fits into your swagger refactoring?

[heaths]

I have a PR started in the private fork for preview-7.1 we should probably rebase this on. I can clean it up for public release, but is otherwise a split of services we wanted for maintainability.

[heaths]

I've also already included this in the aforementioned PR.

[jkapil]

I've also already included this in the aforementioned PR.

@heaths Does this PR needs to be abandoned if you are bringing this change with your PR ?

[heaths]

The timeline for my changes is not quite solidified. For now, I recommend changing your branch to target the new preview-7.1 branch and files (i.e. rebase, but also move the changes to preview/7.1/keyvault.json) and we can get it approved and merged. I'll just have to do a "manual rebase" later when I pull my split-files change in.

[heaths]

Even if the swagger review board allows modifying a shipped version, 7.0 already shipped. This is the wrong file. You need to modify stable/7.0/keyvault.json. /cc @adrianhall @johanste