Open arno01 opened 2 years ago
I'm also curious whether it's possible to really close-close the deployment with the provider's key? Probably not.
I see the use-case behind that is when I want to migrate my provider, I would issue bid close
to all active deployments. Users might not notice that and have their collateral stuck in those "paused" deployments.
Deployment can be closed with the owner key only. The provider can only close the lease.
Tho with a new AuthZ there might be an option to delegate deployment close to another key but there is no planning if it gonna be implemented.
Deployment objects are never in state paused
, but deployment groups are. It looks like we can't query for a list of groups, tho. Couple things we could do:
--group-state
flag to query deployment list
that filters deployment by the state of its groups.query deployment group list
with a --state
filter.At some point we can do an upgrade that moves orphaned escrow funds to the original account or the community fund or something.
At some point we can do an upgrade that moves orphaned escrow funds to the original account or the community fund or something.
That sounds like a great idea! Could also leverage the Governance vote :-)
akash query deployment list
is taking onlyactive/closed
--state
.I suggest adding
paused
state as well.I'm currently able to get it manually with
jq
:Remove
|wc -l
to see the actual list of paused deployments.There is
683.528593
AKT currently locked up as a collateral on these "paused" deployments:So having easy means to query that might help some folks unlocking their AKT's by closing their active but paused deployments.
To reproduce the "paused" deployment simply deploy it and then close it from the provider side using this command:
And am also wondering if we could somehow deliver a message to people with these paused deployments so they can get their collateral back.