search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.29k stars 21.47k forks source link

Synapse Analytics Notebook : tokenlibrary.getsecret() gets old version of the secret #94484

Closed skillbuilderzone closed 5 months ago

skillbuilderzone commented 2 years ago

The issue :

params =  TokenLibrary.getSecret("xxxx","xxxxx","xxx_linkedserver")
print(params)

When the keyvault is updated with a new version of the secret, the above function fetches old version of the secret.

can we specify it to fetch only the current version

Azure doc : https://docs.microsoft.com/en-us/azure/synapse-analytics/spark/apache-spark-secure-credentials-with-tokenlibrary?pivots=programming-language-scala#tokenlibrary-for-azure-data-lake-storage-gen2

Edited: Added doc metadata info

Update : If I update the password in key vault after fetching it in a cell, the re-run of the cell keeps fetching the same secret. Not sure if it's cached somewhere but this keeps happening.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

AjayKumar-MSFT commented 2 years ago

@RamakantDataGuy, Thanks for leveraging Azure docs feedback channel to raise this question. Could you please share the Azure documentation for which this feedback is applicable to? --This channel is reserved for ‘Azure docs’ feedback- for sharing doc feedback and suggesting content improvements.

skillbuilderzone commented 2 years ago

Updated the docs link. Apologies for missing that..

AjayKumar-MSFT commented 2 years ago

@RamakantDataGuy, No worries, thanks for sharing the Azure doc URL. I have added an SME from the area to investigate this further. Thanks!

CHEEKATLAPRADEEP-MSFT commented 2 years ago

@RamakantDataGuy Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

bandersmsft commented 5 months ago

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close