Removed additional forward slash causing 404 error

[james-gould]

The additional / in both restore API calls results in the URL being:

• https://{vaultName}.vault.azure.net/certificates//restore
• https://{vaultName}.vault.azure.net/keys//restore

Removing the additional / constructs a correct path for the request.

For context: I'm building the Azure Key Vault Emulator and have hit this in both keys and certificates, the SecretsClient has the correct path and works without a problem. I raised this a few days in my repo when I found the bug in the KeysClient, having just repeated it in the CertificatesClient I've dug further and got it reproducing. Emulator issue here: james-gould/azure-keyvault-emulator#89

[github-actions]

Thank you for your contribution @james-gould! We will review the pull request and get back to you soon.

[james-gould]

@microsoft-github-policy-service agree

[azure-sdk]

API change check

API changes are not detected in this pull request.

[james-gould]

Build failures are due to the request and recorded URL being different (which is the change), please advise on next steps?

[jsquire]

Hi @james-gould. Thank you for your contribution and interest in improving the Azure developer experience. The test failures do look to be related to test recordings and would require re-recording. Steps for doing so can be found in the recording section of the test framework README.

[jsquire]

@jorgerangel-msft: I'm going to kick the live tests. Can you please take a look at the results and advise whether there's a gap in live testing coverage or in the scenario that is causing a 404 for @james-gould?

[jsquire]

/azp run net - keyvault - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[james-gould]

Sure, will wait for the tests to run. Thanks for getting back so quickly!

[james-gould]

Will take a little time to record the tests again, need to set everything up locally. Will update the PR when it's ready!