Actions
Bug #23563
closed
When a datasource is deleted, its properties should be deleted
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
Today, if a datasources is deleted, then it's property are kept on node, with the datasource provider, which forbids their definition by other means.
This is extremelly surprising. The only way to then delete the property is to create a datasource with the same id than the deleted one, set the "on 404" property to "delete property", and change the target URL to a 404'ing one. Not the best UX.
Updated by François ARMAND about 1 year ago
- Status changed from New to In progress
Updated by François ARMAND about 1 year 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-plugins/pull/602
Updated by François ARMAND about 1 year ago
- Related to Enhancement #23679: Add a plugin bootstrap check to delete datasource properties owned by deleted datasource added
Updated by Anonymous about 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder:rudder-plugins|72f8e537e847fc4214aa8c81c216e5a69ffa73c1.
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder plugin datasources v7.3.9-2.4
Updated by Vincent MEMBRÉ about 1 year ago
This bug has been fixed in Rudder plugin datasources v8.0.2-2.4
Actions