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

ResourceExistsError mentioned in documentation, but does not exist in code #23875

Closed
maxburke opened this issue Dec 17, 2024 · 1 comment · Fixed by #23888
Closed

ResourceExistsError mentioned in documentation, but does not exist in code #23875

maxburke opened this issue Dec 17, 2024 · 1 comment · Fixed by #23888
Assignees
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage Storage Service (Queues, Blobs, Files)

Comments

@maxburke
Copy link

Bug Report

Import path: github.com/Azure/azure-sdk-for-go/sdk/storage/azblob
SDK version: [email protected]
go version: go version go1.22.5 darwin/arm64

Looking at the documentation for Client.CreateContainer (https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob#Client.CreateContainer), which I found linked off of https://learn.microsoft.com/en-us/azure/storage/blobs/storage-quickstart-blobs-go?tabs=roles-azure-portal, I noticed that the Client.CreateContainer function mentions a ResourceExistsError:

CreateContainer is a lifecycle method to creates a new container under the specified account. If the container with the same name already exists, a ResourceExistsError will be raised. This method returns a client with which to interact with the newly created container.

But this ResourceExistsError isn't defined anywhere within the azure-sdk-for-go.

Where is this error defined? Or is the documentation wrong?

@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 17, 2024
@jhendrixMSFT jhendrixMSFT added the Storage Storage Service (Queues, Blobs, Files) label Dec 18, 2024
@github-actions github-actions bot removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 18, 2024
@tanyasethi-msft tanyasethi-msft linked a pull request Dec 24, 2024 that will close this issue
5 tasks
@tanyasethi-msft
Copy link
Member

Hey @maxburke This seems like a bug in documentation - We have updated the document. The "ContainerAlreadyExists" error is correct in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants