Project

General

Profile

Actions

User story #18035

closed

API to totally erase a node everywhere

Added by François ARMAND about 2 years ago. Updated 4 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Regression:

Description

We need an API to totally wipe-out a node everywhere, which means:

- whatever its state, node inventory is deleted,
- node properties/state/etc are deleted,
- generated node policies are deleted,
- node cache is deleted,
- groups are regenerated.

Not sure:

- expected reports for node are deleted
- rudder sys event (compliance reports)

We still keep historized information about compliance data.

The most compatible way to do it is to add a "mode" parameter, with possible values "archive" (default, current behaviour) and "erase" (new mode that doesn't keep inventory etc).

Files in FS should be deleted in any case, node cache too.


Related issues 4 (1 open3 closed)

Related to Rudder - Enhancement #16941: delete entries from nodes_info when a node is deletedNewActions
Related to Rudder - Bug #18654: API message when a node details is not found is extremelly misleadingReleasedNicolas CHARLESActions
Related to Rudder - Bug #19394: When a node is totally deleted, cache in NodeInfoService can't know about itReleasedFrançois ARMANDActions
Related to Rudder - User story #21330: Change default behavior from moving node inventories to archive branch to erasing themReleasedVincent MEMBRÉActions
Actions #1

Updated by François ARMAND about 2 years ago

  • Status changed from New to In progress
Actions #2

Updated by François ARMAND about 2 years ago

  • Description updated (diff)
Actions #3

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 5.0.19 to 5.0.20
Actions #4

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 5.0.20 to 797
Actions #5

Updated by François ARMAND almost 2 years ago

  • Target version changed from 797 to 6.1.7
Actions #6

Updated by François ARMAND almost 2 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/3347
Actions #7

Updated by François ARMAND almost 2 years ago

  • Related to Enhancement #16941: delete entries from nodes_info when a node is deleted added
Actions #8

Updated by François ARMAND almost 2 years ago

  • Status changed from Pending technical review to Pending release
Actions #9

Updated by François ARMAND almost 2 years ago

  • Related to Bug #18654: API message when a node details is not found is extremelly misleading added
Actions #11

Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.7 which was released today.

Actions #12

Updated by François ARMAND over 1 year ago

  • Related to Bug #19394: When a node is totally deleted, cache in NodeInfoService can't know about it added
Actions #14

Updated by François ARMAND 3 months ago

  • Related to User story #21330: Change default behavior from moving node inventories to archive branch to erasing them added
Actions

Also available in: Atom PDF