vectordotdev / vectordotdev/vector
Support overwriting x-ms-version header in azure_blob sink
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
A note for the community
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Use Cases
When the Azure Blob sink sends requests to a storage service that supports only older Azure Storage API versions, the service can reject them with:
400 InvalidHeaderValue
HeaderName: x-ms-version
HeaderValue: 2025-11-05
This occurs when the x-ms-version header is newer than what's accepted by the storage service.
Attempted Solutions
We tried using different authentication methods for azure_blob sink, and all of them run into the same issue.
Proposal
The Azure Blob sink should provide an api_version configuration option that lets users select a version supported by their storage service, eg api_version: "2021-08-06"
References
Version
0.57
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the azure_blob sink configuration and the code that constructs Azure Blob requests, then check the linked Azure versioning reference. Add the api_version option so it controls the x-ms-version header, and add or update tests showing that a configured version is sent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, rust
- Domain
- cloud, data-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100