Closed victorcolombo closed 10 months ago
Current workaround:
docker container ls | grep kurtosistech/core
(get container id, in this example, 9a9c03eb321f)
docker container inspect 9a9c03eb321f | grep isProduction
Returns
...isProductionEnclave\":true}"
Thanks for filing @victorcolombo - this seems like low-hanging fruit usability feature.
Design: the current enclave inspect header looks like this:
Name: icy-hill
UUID: 0a3065d658b0
Status: RUNNING
Creation Time: Tue, 26 Sep 2023 13:15:16 -03
I'd like to add a Flags section like so:
Name: icy-hill
UUID: 0a3065d658b0
Status: RUNNING
Creation Time: Tue, 26 Sep 2023 13:15:16 -03
Flags: production
The only value will be production
for now, but as we add more enclave flags we'll add those here
IMPL NOTES:
allowLatestImages
, restartServices
, etc.) "Production mode" will then be a set of these flags (and maybe users can ultimately define their own "production mode" set of flags)
Background & motivation
Right now, the only viable way to know if an enclave is on production mode is by inspecting the serialized env variables. This makes it very hard to keep track what would be the behavior of this enclave if a service were to go down (especially when the enclave is long running and you forget the mode)
Desired behaviour
Return the
isProduction
field in CLI, webHow important is this to you?
Painful; the lack of this feature makes using Kurtosis frictionful.