Attention is currently required from: fixeria, laforge.

View Change

1 comment:

• File contrib/openapi.yaml:

  • Patch Set #8, Line 27: responses:

    If the requested metric type is invalid, then such a request is considered invalid and rejected with code 400 Bad Request, because it's violating the present specification. I don't think we want to define general response codes like 400 or 500 for each procedure explicitly.

    Acknowledged

    Regarding the path... I guess by invalid path you mean a path that matches no metrics in the S1GW. This can be a mistake, e.g. a typo, but this can also happen if the matching metrics are not registered yet. For instance, this applies to per-eNB metrics: they do not exist before the eNB connects. I can implement returning 404 in this case (in a follow-up patch).

    That sounds useful IMHO.

To view, visit change 41099. To unsubscribe, or for help writing mail filters, visit settings.