In S3M (and the other IRI APIs at other institutions), /status is meant to be an unauthenticated endpoint so that folks can access information about a site's resource without having to log in or get some sort of special token.
In the iri-demo repo, here is an example of us separating out the individual machine status endpoint to a separate unauthenticated service object: https://github.com/ORNL/s3m-sdk-python/blob/iri-demo/src/s3m_api/services/status.py
We will want to move over BOTH of the status capabilities for both checking the status of a machine /status/{machine} and of all machines /status to this status service.
In S3M (and the other IRI APIs at other institutions), /status is meant to be an unauthenticated endpoint so that folks can access information about a site's resource without having to log in or get some sort of special token.
In the iri-demo repo, here is an example of us separating out the individual machine status endpoint to a separate unauthenticated service object: https://github.com/ORNL/s3m-sdk-python/blob/iri-demo/src/s3m_api/services/status.py
We will want to move over BOTH of the status capabilities for both checking the status of a machine
/status/{machine}and of all machines/statusto this status service.