You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the API reference docs link for the azure-keyvault package: https://docs.microsoft.com/en-us/python/api/overview/azure/keyvault. Unfortunately this link gets re-directed in a way such that it gets the query parameter view=azure-python-preview which makes the page use the "preview" moniker. It should be using view=azure-python-previous instead so that the "legacy" moniker is used and the right content gets rendered for azure-keyvault.
ghost
removed
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Dec 15, 2020
ramya-rao-a
added
Central-EngSys
This issue is owned by the Engineering System team.
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
and removed
Client
This issue points to a problem in the data-plane of the library.
labels
Dec 15, 2020
ghost
removed
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Dec 15, 2020
This seems to have been resolved -- following the link in the description or the version 1.x.x "Reference" link in the KV overview page leads to the correct, legacy page. Closing as a result, thank you!
Revert "[Hub Generated] Review request for Microsoft.Devices to add version preview/2021-09-01-preview (Azure#15428)" (Azure#15797)
This reverts commit 2105605.
This is the API reference docs link for the
azure-keyvault
package: https://docs.microsoft.com/en-us/python/api/overview/azure/keyvault. Unfortunately this link gets re-directed in a way such that it gets the query parameterview=azure-python-preview
which makes the page use the "preview" moniker. It should be usingview=azure-python-previous
instead so that the "legacy" moniker is used and the right content gets rendered forazure-keyvault
.Found during #15110
Nice catch @mccoyp!
The text was updated successfully, but these errors were encountered: