Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Header for driver version and other info #440

Closed
tjoubert opened this issue Nov 21, 2022 · 3 comments · Fixed by #441
Closed

Header for driver version and other info #440

tjoubert opened this issue Nov 21, 2022 · 3 comments · Fixed by #441
Assignees
Labels
enhancement New feature or request

Comments

@tjoubert
Copy link
Contributor

There is a requirement for a new header that will contain information about the driver and will be supplied with every request. The name of the header is x-arango-driver and the format of the value is driverName/version ([flags...]).
flags are semicolon separated list of flags/tags. Eg. one flag could be cloud to denote that the driver is configured to use cloud-optimized behavior.
For example:
x-arango-driver : ArangoDBNetStandard/1.2.0 (cloud)

@tjoubert tjoubert added the enhancement New feature or request label Nov 21, 2022
@tjoubert tjoubert self-assigned this Nov 21, 2022
@tjoubert tjoubert linked a pull request Nov 21, 2022 that will close this issue
@DiscoPYF
Copy link
Collaborator

Thanks for the info 👍

There is a requirement for a new header that will contain information about the driver and will be supplied with every request.

What's driving the requirement/Where does it come from? Is it something ArangoDB will use for analytics on Oasis instances?

@tjoubert
Copy link
Contributor Author

@DiscoPYF , this is a requirement from the API team and we are not sure what they are going to use the information for.

@DiscoPYF
Copy link
Collaborator

Copy that, thanks @tjoubert 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants