Skip to content

Rename DeleteActorRequest.any_state #1161

Closed
Task
#2727
Closed
Rename DeleteActorRequest.any_state#1161
Task
#2727
Assignees
laoj2
Labels
area/apiUser-facing API changesarea/api-machinerykind/cleanupSmall fixes that are not bugs, for example a typo in a code comment

Description

@juli4n
Julian Gutierrez Oschmann (juli4n)
opened on Aug 24, 2026

In #788 a new field any_state was added to allow for force delete Actor resources, irrespective of the Actor state. This looks like a "control" field for delete, so I think it should probably be moved under DeleteOptions. Should we also rename it to force?

Activity

  1. Julian Gutierrez Oschmann (juli4n)
    added
    area/apiUser-facing API changes
    area/api-machinery
    on Aug 24, 2026
  2. Julian Gutierrez Oschmann (juli4n)
    added the
    Task
    issue type on Aug 24, 2026
  3. Aditya Shantanu (aditya-shantanu)
    added
    kind/cleanupSmall fixes that are not bugs, for example a typo in a code comment
    on Aug 24, 2026
  4. Julian Gutierrez Oschmann (juli4n)
    added a parent issue on Aug 24, 2026
  5. github-project-automation
    added this to Substrate Milestones (go/substrate-milestones)on Aug 24, 2026
  6. github-project-automation
    moved this to Todo in Substrate Milestones (go/substrate-milestones)on Aug 24, 2026

  7. zoez7 commented on Aug 24, 2026

    @zoez7
    Zoe Zhao (zoez7)
    on Aug 24, 2026
    Collaborator

    Should we also rename it to force?

    We used the "any_state" boolean to indicate that this will allow users to delete actors from any state, not just suspended or crashed.

    We didn't use "force" because this is not a "force deletion", failed deletion still leaves an actor record (to allow retry). I think "force" is separate from "any-state", if customer calls "force delete actor", we should free up the original actor object ref, and allow creating another actor with the same (atespace, actorname).

  8. Julian Gutierrez Oschmann (juli4n)
    removed a parent issue on Oct 6, 2026
  9. Julian Gutierrez Oschmann (juli4n)
    added a parent issue on Oct 6, 2026
  10. Luiz Oliveira (laoj2)
    self-assigned this
    on Oct 9, 2026
  11. github-project-automation
    moved this from Todo to In Progress in Substrate Milestones (go/substrate-milestones)on Oct 15, 2026

  12. laoj2 commented on Oct 15, 2026

    @laoj2
    Luiz Oliveira (laoj2)
    on Oct 15, 2026
    Collaborator

    Today DeleteActor only accepts CRASHED or SUSPENDED actors unless any_state=true is set.

    Instead of renaming this field to force, we agreed to make any_state=true the default behaviour (there's no strong reason why this isn't the case) and remove any_state altogether.

  13. Julian Gutierrez Oschmann (juli4n)
    closed this as completedin #2727on Oct 19, 2026
  14. github-project-automation
    moved this from In Progress to Done in Substrate Milestones (go/substrate-milestones)on Oct 19, 2026
  15. haiyanmeng
    added a commit that references this issue on Oct 19, 2026

    Remove any_state and allow deleting actors in any state (agent-substr…

    5952cfd
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/apiUser-facing API changesarea/api-machinerykind/cleanupSmall fixes that are not bugs, for example a typo in a code comment

Type

Task

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions