dapr / dapr/components-contrib
[AWS Bindings S3] Add Metadata Fields Corresponding to Those Ending with "SSL" to "TLS"
- Dominant language
- Go
- Stars
- 602
- Forks
- 580
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
## Describe the feature
[AWS Bindings S3] Add Metadata Fields Correspoinding to Those Ending with "SSL" to "TLS".
The current fields must be kept for backwards compatibility while new ones being aliases.
`DisableTLS` ==> [DisableSSL](https://github.com/dapr/components-contrib/blob/master/bindings/aws/s3/s3.go#L74)
`InsecureSSL` ==> [InsecureSSL](https://github.com/dapr/components-contrib/blob/master/bindings/aws/s3/s3.go#L75)
Contributor guide
Research direction
Start in bindings/aws/s3/s3.go, especially the metadata fields around lines 74-75. Check how the existing SSL-named fields are parsed and identify the intended TLS aliases while preserving backward compatibility. Confirm the metadata names and alias behavior with the S3 binding's existing tests, if present; done means both naming forms work without breaking the old fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100