Remove isWriteOperation on container delete

[kjg]

Hi! For some reasons I'm getting back 500 errors when I attempt to delete a cosmos container. If I remove isWriteOperation: true, the Delete is successful.

I'm not sure if this is a server issue, or a client issue, but my hopes is that this PR can either spark the investigation or lead to a fix.

Interestingly I see that (Database).Delete also uses isWriteOperation: true, and that operation is successful for me (both with and without the option set)

I didn't see any tests added when this option was first added, so I'm not sure if there are any tests might be relevant for this change. I'd be happy to update the CHANGELOG if this is accepted, but wanted to start the discussion first since I think there is a chance that this is a server side issue (since Database deletion works).

• The purpose of this PR is explained in this or a referenced issue.
• The PR does not update generated files.
  • These files are managed by the codegen framework at Azure/autorest.go.
• Tests are included and/or updated for code changes.
• Updates to module CHANGELOG.md are included.
• MIT license headers are included in each file.

[github-actions]

Thank you for your contribution @kjg! We will review the pull request and get back to you soon.

[ealsur]

A delete is a Write operation. And we have tests that use this. The Write operation is used to define routing (write operations can only be sent to the primary region)

Please verify with the service team the origin of the HTTP 500.

[ealsur]

isWriteOperation does not modify the request that is sent, it is used to know which region to route it to.

azure-sdk-for-go/sdk/data/azcosmos/cosmos_location_cache.go

Line 116 in 2532a53

func (lc *locationCache) resolveServiceEndpoint(locationIndex int, isWriteOperation, useWriteEndpoint bool) url.URL {

[kjg]

Closing this because #23335 is the correct fix for my issue