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

[INPUTS/OUTPUTS] Formalization of requirements and contracts for ODAHU services inputs, description of outputs #614

Open
alinaignatiuk opened this issue Aug 24, 2021 · 1 comment
Assignees
Labels
1.7 documentation Improvements or additions to documentation major without one user can perform the target action in a workaround, but it's not obvious
Milestone

Comments

@alinaignatiuk
Copy link

Create a list of required inputs for ODAHU services (and formats that are currently supported in ODAHU for each input) and outputs that ODAHU services produce (and formats that are currently supported in ODAHU for each output).
Specify for each input whether it is mandatory for ODAHU service (the ODAHU service will not be able to perform the work without it) or non-mandatory/optional.
The purpose of this list is to:

  1. Create visibility for users on how the ODAHU system operate and what are the requirements and supported formats;
  2. Create the dev plan for required improvements in the validation process in ODAHU: what kind of validation should be performed, so that the ODAHU will not crash if the obligatory inputs are not in place, but rather inform the user about missed requirements.
@alinaignatiuk alinaignatiuk added 1.7 major without one user can perform the target action in a workaround, but it's not obvious labels Aug 24, 2021
@alinaignatiuk alinaignatiuk added this to the v1.6 milestone Aug 24, 2021
@alinaignatiuk
Copy link
Author

alinaignatiuk commented Aug 24, 2021

Connected with #609

@alinaignatiuk alinaignatiuk added the documentation Improvements or additions to documentation label Aug 24, 2021
@lev-titov lev-titov assigned alinaignatiuk and unassigned lev-titov Oct 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.7 documentation Improvements or additions to documentation major without one user can perform the target action in a workaround, but it's not obvious
Projects
None yet
Development

No branches or pull requests

2 participants