You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I successfully create a Sandbox instance, the Delete button is disabled. To delete I need to wait for the status not to be running (e.g. wait until tomorrow?).
It should be possible to stop/delete the instance whenever I am done using it.
The text was updated successfully, but these errors were encountered:
@deboer-tim I agree, but the provider API controls lifecycle commands (delete is lifecycle command) based on connection status. Delete is enabled only when connections is stopped or unknown.
Ok, so maybe we need an API update to distinguish between local instances (that can be started/stopped and deleted) vs remote ones where you can just drop the connection (delete the context)?
In general Delete should probably be always enabled, and podman-desktop should execute Stop command for connection/image/extension if running before executing Delete command.
Another one would be:
Do not restrict provider to specific set of commands
Let provider configure commands that would be shown for connections
Let UI render buttons based on commands state (controlled by provider)
This way for example I would be able to provide custom commands for Developer Sandbox Connection, like 'Refresh authentication token' when sandbox cluster is running but token is expired.
If I successfully create a Sandbox instance, the Delete button is disabled. To delete I need to wait for the status not to be running (e.g. wait until tomorrow?).
It should be possible to stop/delete the instance whenever I am done using it.
The text was updated successfully, but these errors were encountered: