Different request /response for Dapr storage binding across GCP,Azure and AWS

[bhagya05]

We have noticed inconsistencies in the request and response structures of the Dapr bindings for GCP Bucket, Azure Blob Storage, and AWS S3.
These differences hinder the uniform use of Dapr as a plugin component, as we are required to create and manage distinct request/response objects for each binding.

Example

GCP bucket upload request looks like this

curl -d "{ \"operation\": \"create\", \"data\": \"(YOUR_FILE_CONTENTS)\", 
\"metadata\": { \"key\": \"my-test-file.jpg\" } }" http://localhost:<dapr-port>/v1.0/bindings/<binding-name>

While for Azure looks like this

curl -d "{ \"operation\": \"create\", \"data\": \"Hello World\", 
\"metadata\": { \"blobName\": \"my-test-file.txt\" } }"  http://localhost:<dapr-port>/v1.0/bindings/<binding-name>

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.