Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No value of 'Shared Access Signature' display in 'Properties' window for attached table #184

Closed
v-dantch opened this issue May 15, 2018 · 1 comment
Assignees
Labels
⚙️ attach Related to attaching via keys, SAS, etc. 🧪 testing Found through regular testing ✅ merged A fix for this issue has been merged
Milestone

Comments

@v-dantch
Copy link

Storage Explorer Version: 1.1.0

Platform: Windows

Architecture: ia32

Build Number: 20180510.2

Commit: d271505a

Regression From: Not a regression

Steps to Reproduce:

  1. Attach one table with SAS.
  2. Navigate to '(SAS-Attached Services) > Tables' and check the 'Properties' window of this table.

Expected Experience:

The value of 'Shared Access Signature' displays well.

Actual Experience:

No value of 'Shared Access Signature' displays.

sas
More Info:
This issue doesn't reproduce for tables under attached storage account with SAS.
sas-account

@v-dantch v-dantch added the 🧪 testing Found through regular testing label May 15, 2018
@craxal craxal added this to the 1.3.0 milestone Jun 1, 2018
@craxal craxal added the ⚙️ attach Related to attaching via keys, SAS, etc. label Jun 1, 2018
@craxal craxal self-assigned this Jun 1, 2018
@MRayermannMSFT
Copy link
Member

Will be fixed with custom connections.

@craxal craxal modified the milestones: 1.3.0, 1.4.0 Jun 13, 2018
@craxal craxal added the ✅ merged A fix for this issue has been merged label Jul 16, 2018
@craxal craxal closed this as completed Jul 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⚙️ attach Related to attaching via keys, SAS, etc. 🧪 testing Found through regular testing ✅ merged A fix for this issue has been merged
Projects
None yet
Development

No branches or pull requests

3 participants