Project

General

Profile

Actions

User story #18508

closed

Missing a PATCH API for allowed networks

Added by François ARMAND over 3 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
API
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
To do
Fix check:
Checked
Regression:

Description

On some complex (serious) infrastructures, there can tens of allowed networks. These are sensitive data, often modifed, and it can happen that there is concurrent modification on them. So a "replace" only semantic can't be enought:

(client 1 wants to add n3, client2 remove n2)
* STATE on server: [n1, n2]
client1: get all allowed networks => [n1, n2]
client2: get all allowed networks => [n1, n2]
client1 POST [n1, n2, n3]
* STATE on server: [n1, n2, n3]
client1 POST [n1]
* STATE on server: [n1] <= NOT WHAT WE WANT.

So: add a patch command to handle just add/remove some networks.


Related issues 1 (0 open1 closed)

Related to Rudder - Architecture #18730: Move allowed network data to settings ReleasedVincent MEMBRÉActions
Actions #1

Updated by François ARMAND over 3 years ago

  • Status changed from New to In progress
Actions #2

Updated by François ARMAND over 3 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/3364
Actions #3

Updated by François ARMAND over 3 years ago

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

Updated by François ARMAND over 3 years ago

  • Fix check changed from To do to Checked
Actions #5

Updated by Vincent MEMBRÉ over 3 years ago

  • Status changed from Pending release to Released

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

Actions #6

Updated by François ARMAND over 2 years ago

Actions

Also available in: Atom PDF