feat: enable retrieving logs from services in stopped enclaves #1213
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.
Description:
Enables retrieving logs in stopped enclaves.
Context:
Logs were stored
/enclave uuid/service uuid.json
. When an enclave is running, id logic translates shortened uuids and service names toservice uuid
. However when an enclave is stopped, the service identifier information is lost and that translation isn't possible so users wouldn't be able to retrieve logs from a stopped enclave via the service name or shortened uuid.Adjusting the id logic would've required a larger refactor to persist service id info beyond enclave lifecycle.
This PR implements a cheaper solution - store logs
/enclave uuid/service uuid.json
, as well as/enclave uuid/service name.json
and/enclave uuid/service short uuid.json
, with the tradeoff of tripling log storage. I've added a TODO to develop a better solution.Is this change user facing?
YES