mirror of
https://github.com/therealpaulgg/ssh-sync.git
synced 2026-04-26 16:05:51 +03:00
[GH-ISSUE #25] Delete/upload/download specific keys or config entries #4
Labels
No labels
ai-generated
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ssh-sync#4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @therealpaulgg on GitHub (Apr 26, 2023).
Original GitHub issue: https://github.com/therealpaulgg/ssh-sync/issues/25
Originally assigned to: @therealpaulgg, @Copilot on GitHub.
@therealpaulgg commented on GitHub (Mar 20, 2024):
This is really a 'nice to have', not really necessary for v1 release.
@therealpaulgg commented on GitHub (Apr 3, 2024):
It turns out it would be quite nice to have this.
I accidentally added a .duplicate file to my actual ssh-sync store, and I can't get rid of it.
Also we should implement a bug fix for the following situation:
This'll create a problem when having to create another bob.duplicate
A simple fix could be, ssh-sync just never ever uploads .duplicate files. But in the event it does, we should handle that scenario and append some sort of character.
But - now that I'm in this state, I would love to be able to delete a specific entry from my keystore.
Perhaps a TUI to explore the keys...that would be really cool
@therealpaulgg commented on GitHub (Apr 3, 2024):
This will require additional endpoints in ssh-sync-server.
@therealpaulgg commented on GitHub (Nov 9, 2024):
The delete portion of key management is complete.
Next task:
As a user,
I want to be able to delete configuration entries from the configuration store,
so that I may have further control over my configuration.