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

Logging to Azure with a stored access policy? #66

Open
pg94au opened this issue Aug 9, 2017 · 0 comments
Open

Logging to Azure with a stored access policy? #66

pg94au opened this issue Aug 9, 2017 · 0 comments

Comments

@pg94au
Copy link

pg94au commented Aug 9, 2017

I've been experimenting with this project, and rather than provide one of the default keys for the storage account as the connection string, I'd like to provide one with limited permissions. Specifically, I'd like to use a connection string that only allows for access to the specific container where the blob appender will be storing logs.

I can create a connection string from a stored access policy that I create that just provides the required permissions for my target container, but ActivateOptions in the AzureBlobAppender throws an exception due to a 403 returned by the remote service. The problem is due to the call to CreateIfNotExists, which cannot be performed without the ability to create containers.

I don't think that providing the ability to create containers should be necessary for logging into one. Would you consider either removing this call or wrapping it in a try/catch, to prevent failure when this permission is not available?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant