-
Notifications
You must be signed in to change notification settings - Fork 98
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
[FEATURE] Integration Validation Endpoint #1466
Comments
Further work requires progress on #1456 to get a consistent idea on how integrations will be processed by the API. Paused to prioritize that. |
Outdated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
Per work on integrations, an endpoint needs to be added that can validate an integration. The validation logic was implemented in #1464, so this issue mostly concerns routing.
The endpoint consumes a zip file containing the integrations.
What solution would you like?
The design of the API as a whole is described in #1446, the main action item for this ticket is implementing the
/store/{id}/validate
endpoint.What alternatives have you considered?
Validation could be done as a part of the storage process instead of as its own endpoint. This logic should be included, but having a separate endpoint also enables more-expensive full validation of a completed integration, instead of validating individual components.
Do you have any additional context?
Integration Project
#1443
The text was updated successfully, but these errors were encountered: