Skip to content

forget currently exits with an exit code 0 even if some snapshots couldn't be removed #5233

@konidev20

Description

@konidev20

Output of restic version

restic 0.17.3

What should restic do differently? Which functionality do you think we should add?

restic must define an appropriate exit code when it is not able to remove all the snapshots when using forget command along with the --prune flag

What are you trying to do? What problem would this solve?

forget currently exits with an exit code 0 even if some snapshots couldn't be removed.

This has been discussed in #5140

Quoting @MichaelEischer:

forget currently does exit with exit code 0 even if some snapshots couldn't be removed (see restic/cmd/restic/cmd_forget.go
That is definitely a problem when using forget --prune and somewhat questionable when called without that option.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions