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
Currently, data recipients cannot specify the location of a sharing profile using Azure Synapse FS (synfs: schema). Rather than expanding support for synfs and future, alternate schemas, it may be more flexible to allow data recipients to specify the sharing profile as a JSON object, passing it as an argument to the Python sharing client constructor. For example:
While it could be argued that the sharing access token is now clear text, a secrets manager client, like Azure key vault client for Python, could be used to securely access the sharing token.
The text was updated successfully, but these errors were encountered:
Currently, data recipients cannot specify the location of a sharing profile using Azure Synapse FS (
synfs:
schema). Rather than expanding support forsynfs
and future, alternate schemas, it may be more flexible to allow data recipients to specify the sharing profile as a JSON object, passing it as an argument to the Python sharing client constructor. For example:While it could be argued that the sharing access token is now clear text, a secrets manager client, like Azure key vault client for Python, could be used to securely access the sharing token.
The text was updated successfully, but these errors were encountered: