RSDK-3534 Add last_reconfigured
to each resource status
#101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RSDK-3534
Updates rust protos (ran
make buf
). UpdatesGetReadingRe*
use
statements. Addsbuild_time
field toLocalRobot
derived from gRPCget_config
header. Convertsbuild_time
to proto and adds that proto to every resource status aslast_reconfigured
.Spoke with @gvaradarajan offline. We've added
LastReconfigured
timestamps to all resources for users of resources to have a better sense of when the resource was last constructed/updated in the backend. The micro RDK has no concept of "reconfiguration" or dynamic updates to resources, so we can just use the time at which we got the cloud config as thebuild_time
for all resources. Note thatbuild_time
does not exist for non-cloudLocalRobot
s, so they'll returnNone
as thelast_reconfigured
value.