Actions
User story #18508
closedMissing a PATCH API for allowed networks
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.
Updated by François ARMAND about 4 years ago
- Status changed from New to In progress
Updated by François ARMAND about 4 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
Updated by François ARMAND about 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|0112666eecb55c1177d83d61ff90673c08febec3.
Updated by François ARMAND about 4 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.7 which was released today.
Updated by François ARMAND over 3 years ago
- Related to Architecture #18730: Move allowed network data to settings added
Actions