This repository has been archived by the owner on Oct 31, 2019. It is now read-only.
Support blob functions without authentication #44
Comments
|
Great plan Andire. Also we need to check the blob read/write for some data types. |
andrie
added a commit
that referenced
this issue
Feb 6, 2017
…to azureListStorageBlobs() and azureGetBlob() #44
andrie
added a commit
that referenced
this issue
Feb 6, 2017
andrie
added a commit
that referenced
this issue
Feb 13, 2017
* 44-blob-no-authenticate: Update tests to reflect that function output is TRUE when successful #31 Remove redundant arguments, e.g. azToken #50 Add validateStorageArguments() function #46 Support downloading more than 5000 blob results, by passing maxresults as an argument #48 Replace cat() with message() #49 Modify tests to reflect that azureCheckToken() return logical value Modify azurePutBlob() to use callAzureStorageApi() and updateAzureActiveContext() #46 Add updateAzureActiveContext() function to simplify code #46 Only attempts to authenticate if is.activeAzureContect() is TRUE #46 Define callAzureStorageApi() function and use in azureListStorageBlobs() #46 Don't authenticate - workaround for testing - have to fix this!!! #44 Allow setting azureContext = NULL to access blob storage. Edits only to azureListStorageBlobs() and azureGetBlob() #44 Add Visual Studio RTVS files to .gitignore
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As mentioned in #41, some functions don't require authentication against the Azure Service Manager. Specifically, blob storage functions will work given only the storage key.
By supporting a version of the function that does not enforce supplying the
activeAzureContextargument, we can improve ease-of-use for certain use cases.I will create a feature branch to test this functionality, prioritizing the following functions:
azureListStorageBlobs()The text was updated successfully, but these errors were encountered: