Project

General

Profile

Actions
Copy link

Bug #23563

closed

When a datasource is deleted, its properties should be deleted

Added by François ARMAND about 1 year ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Target version:
Rudder plugins - 7.3
Pull Request:
https://github.com/Normation/rudder-p...
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.

Related issues 1 (1 open — 0 closed)

Related to Datasources - Enhancement #23679: Add a plugin bootstrap check to delete datasource properties owned by deleted datasourceNewActions
Actions
Copy link

Also available in: Atom PDF