Summary
The Storage driver interface is missing bucket-level security and configuration operations that are essential for testing access control and compliance.
What's Missing
- Bucket Policy: PutBucketPolicy / GetBucketPolicy / DeleteBucketPolicy
- CORS Configuration: PutCORSConfig / GetCORSConfig / DeleteCORSConfig
- Encryption Configuration: PutBucketEncryption / GetBucketEncryption
Provider Mapping
| Feature |
AWS S3 |
Azure Blob |
GCP GCS |
| Bucket Policy |
BucketPolicy |
Access Policy |
IAM Policy on Bucket |
| CORS |
CORS Configuration |
CORS Rules |
CORS Config |
| Encryption |
ServerSideEncryption |
Encryption Scope |
Default Encryption |
Why This Matters
- Security testing is blocked — can't verify that policies are correctly applied
- CORS is required for any frontend-to-storage integration test
- Encryption config is a compliance requirement in most organizations
Acceptance Criteria
Summary
The Storage driver interface is missing bucket-level security and configuration operations that are essential for testing access control and compliance.
What's Missing
Provider Mapping
Why This Matters
Acceptance Criteria
storage/driver/driver.go