feature request: support customer-defined http headers

[qweeah]

What would you like to be added? User can specify http headers sent to to the remote registry.

• [x] #521
• [ ] Reusing HttpHeaders field in docker config

Why is this needed? Please describe your user story or scenario.

Customer-defined http headers are also supported in other registry tools like docker and containerd, which gives flexibilty on customerizing the outgoing http request from client side.

[qweeah]

The headers will be consumed by registry service. Below are some examples for Azure Container Registry:

1. X-Meta-Source-Client: tells the service provider who is using the registry service.
2. X-Ms-Correlation-Request-Id: provides an id which can be used to correlate telemetry during trouble-shooting.

[qweeah]

moving to future milestone as there is no user requesting docker config support for customer header

[amands98]

@qweeah btw, do you suggest that I include a fix for the issue of reusing the HttpHeaders field in the Docker configuration?