-
Notifications
You must be signed in to change notification settings - Fork 21
feat(specs): create ingestion specs #1100
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
Conversation
✗ The generated branch has been deleted.If the PR has been merged, you can check the generated code on the |
✅ Deploy Preview for api-clients-automation ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
98e6ec5
to
fbec6ec
Compare
type: object | ||
additionalProperties: false | ||
properties: | ||
runID: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we could use a ref from specs/ingestion/common/parameters.yml same for events
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the parameters in parameters.yml
are used for path or query params, not sure they would fit in this object
# lastCursorValue: | ||
# type: integer | ||
# format: int64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there an issue with that field?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not yet used in our API. It will always be null
.
It will be used in the future, for tools that need many run to overview all the data of a Source.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plus one with @Fluf22, there is no point in exposing it right now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oki we can remove it then if we don't mind now
5845069
to
e5b5230
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one last comment
Seems okay overall
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's go 🪨
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nothing more to add GG it's nice :D
$ref: './common.yml#/createdAt' | ||
required: | ||
- authenticationID | ||
- name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this API is so different than the others :( we should maybe focus on making it more consistent
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's already better now !
/1/runs: | ||
$ref: 'paths/runs/runs.yml' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can add the run/task/{taskID}
if you want
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added in 1ae5710
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah maybe we can remove the sources one
I'll remove sources in another PR :) |
algolia/api-clients-automation#1100 Co-authored-by: Pierre Millot <[email protected]>
algolia/api-clients-automation#1100 Co-authored-by: Pierre Millot <[email protected]>
🧭 What and Why
🎟 JIRA Ticket: DI-382
Create the openapi specification for the Ingestion API (repository, RFC).
This first PR is missing the pagination because it's not clear how it will be handled (body or query params).
It's also missing a lot of
description
fields, but we can definitely improve on the doc in the future.