StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POCan't programmatically set permissions to blob container in Azure Storage
primarykey
Id
16571433
data
AcceptedAnswerId
16573775
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-15T17:30:09.537
FavoriteCount
0
LastActivityDate
2013-05-16T14:10:17.717
LastEditDate
2013-05-15T23:40:03.197
LastEditorUserId
3759
OwnerUserId
3759
ParentId
0
PostTypeId
1
Score
2
ViewCount
3265
LastEditorDisplayName
text
Body
After creating a blob container with <code>CreateIfNotExists()</code>, I immediately call <code>SetPermissions()</code> to allow users public access to the blobs in the container, but not to the container itself. Like so: <pre class="lang-cs prettyprint-override"><code>CloudBlobContainer pdfContainer = blobClient.GetContainerReference(ContainerName.PDFs); if (pdfContainer.CreateIfNotExists()) pdfContainer.SetPermissions(new BlobContainerPermissions { PublicAccess = BlobContainerPublicAccessType.Blob }); </code></pre> The container is created successfully, but when I log in to the Azure portal, the blob container permission is <code>Private</code>. Am I missing an additional call to commit the permission changes? None of the examples that I've looked at seem to show that and I don't see anything in the documentation either. I'm using v2.0 of the Azure SDK. UPDATE: It looks like <code>CreateIfNotExists()</code> is always returning false. I pried the assembly open in Reflector and found that it was catching a (409) Conflict HTTP error and swallowing the exception. This appears to be an issue with either the SDK or the server-side REST implementation. Even though the container does not exist and the container creation succeeds, a 409 is still returned from the server. It seems like the best thing to do is call <code>CreateIfNotExists()</code> and ignore the return value for now. Also, it is not necessary to call <code>GetPermissions()</code> before calling <code>SetPermissions()</code>. 
Tags
<azure><permissions><azure-storage-blobs><azure-storage>
Title
Can't programmatically set permissions to blob container in Azure Storage
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAndy S
UserOwnerUserId
1. USAndy S
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POCan't programmatically set permissions to blob container in Azure Storage
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.