-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Resolve location endpoint #51
Comments
To clarify all of the above is supposed to get eaten by a single input "location". Its not different parameters, they are all examples the user should be able to pass to a single input and get back a resolved json of correctly formatted location parameters that the /measurement endpoint can process. So its a conversion of 1 magic input to many typed inputs |
Summary of internal discussion:
New probe client metadata object:
|
Manual aliases we should add:
|
I don' think we discussed that - do we want to include both ISO and full state/country/continent formats? |
|
Yes, the user should be able to write "Germany" and it should automatically convert to "DE". I have it as an example input in the task. So all those inputs should work correctly |
Resolve location endpoint for magic like "Ping from 10 locations in Eastern Europe".
Its needed for easier development of web and cli tools.
It should also support partial names like "frankfurt" when in reality the probes are at "frankfurt am main" or "amazon" when full is "amazon.com inc"
Example inputs:
The output should be something easily usable for the measurement endpoint.
The text was updated successfully, but these errors were encountered: