generate-sas creates SAS without t after ss= even though I specified table service in --services
See original GitHub issueI tried to use generate-sas to create a SAS link with access to table service. But the created SAS token doesn’t have t after ss==. It seems to intentionally ignore the request. The same command line works fine on my windows box with azure-cli(2.0.0). Is it a regression?
az storage account generate-sas --account-name ubuntudiagnostic --expiry 2018-12-31T23:59Z --permissions wlacurdp --resource-types sco --services bfqt -o tsv --verbose
se=2018-12-31T23%3A59Z&sp=rwdlacup&sv=2017-04-17&**ss=bqf**&srt=sco&sig=<remove signature intentionally>
Environment summary
azure-cli (2.0.20)
acr (2.0.14) acs (2.0.18) appservice (0.1.19) backup (1.0.2) batch (3.1.6) batchai (0.1.2) billing (0.1.6) cdn (0.0.10) cloud (2.0.9) cognitiveservices (0.1.9) command-modules-nspkg (2.0.1) component (2.0.8) configure (2.0.12) consumption (0.1.6) container (0.1.12) core (2.0.20) cosmosdb (0.1.14) dla (0.0.13) dls (0.0.16) eventgrid (0.1.5) extension (0.0.5) feedback (2.0.6) find (0.2.7) interactive (0.3.11) iot (0.1.13) keyvault (2.0.13) lab (0.0.12) monitor (0.0.11) network (2.0.17) nspkg (3.0.1) profile (2.0.15) rdbms (0.0.8) redis (0.2.10) resource (2.0.17) role (2.0.14) servicefabric (0.0.5) sql (2.0.14) storage (2.0.18) vm (2.0.17)
Python location ‘/opt/az/bin/python3’ Extensions directory ‘/home/fliang/.azure/cliextensions’
Python (Linux) 3.6.1 (default, Oct 18 2017, 20:41:18) [GCC 4.8.4]
Legal docs and information: aka.ms/AzureCliLegal
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (6 by maintainers)
Top GitHub Comments
Table service is being moved out of azure storage and integrating with CosmosDB service. Therefore the table will not fall under the storage service’s SAS token anymore. We kept the command structure to avoid breaking change in short-term.
To generate a SAS for table service please use
az storage table generate-sas
command.Thanks for the confirmation. It has been fixed.