User story #10351
closed
Make datasources behaviour on 404 request configurable
Added by François ARMAND about 7 years ago.
Updated almost 2 years ago.
Suggestion strength:
Advise - This would make Rudder significantly better | easier | simpler
User visibility:
Infrequent - complex configurations | third party integrations
Description
For now, the data sources plugin delete a property content if the request for that node leaded to a 404.
In some case, we may prefer to let the old properties not modified, or even use a default value. So we must make that choice configurable in the data sources options.
- Status changed from New to In progress
- Assignee set to François ARMAND
- Translation missing: en.field_tag_list set to Sponsored
- Suggestion strength set to Advise - This would make Rudder significantly better | easier | simpler
- User visibility set to Infrequent - complex configurations | third party integrations
- Target version changed from 4.1.0 to 4.1.1
- 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-plugin-datasources/pull/12
- Status changed from Pending technical review to Pending release
Applied in changeset commit:rudder-plugin-datasources|361d863aefc1e46e4079340e11540be76ac1c9ba.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.1 which was released today.
- Project changed from Rudder to 54
- Category deleted (
71)
- Target version changed from 4.1.1 to 426
- Project changed from 54 to Datasources
- Target version changed from 426 to 4.1-1.0
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by