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.

Sign up for GitHub

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

Jump to bottom

Provide status on the errors of the service's #24

Closed

Symbianx opened this issue Nov 7, 2017 · 1 comment · Fixed by #25

Assignees

Labels

Projects

Milestone

Contributor

Symbianx commented Nov 7, 2017

By @suvl at nosinovacao/name-registry-api#1

A field should be added to the manifest providing insight on the error level of the last announced manifest. That field should have three levels, as suggested (not final):

OK: no errors

WARN: the current errors won't let NAME know if there's anything wrong or not (dependencies do not have NAME installed or NAME version is invalid)

ERR: all other errors not included in WARN

Symbianx self-assigned this

Symbianx added the enhancement label

Symbianx added this to the 1.1.0 milestone

Symbianx added this to In Progress in NAME Core

Contributor Author

Symbianx commented Nov 7, 2017 •

edited

Loading

Adding the status field to the manifest with the values:

Ok: No errors were found.
Warn: The status of a dependency could not be resolved. E.g.: NAME not installed.
Error: The status of a dependency was successfully resolved and is not valid. (E.g.: Elasticsearch is offline or version mismatch)

Symbianx mentioned this issue

Provide status on the errors of the services #25

Merged

Symbianx closed this as completed in #25

Symbianx moved this from In Progress to Done in NAME Core

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment