Actions
Bug #17325
closed
We can't choose between string and json for global parameters
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
For node properties, we have a choice between json and string value, and when we choose json, it checks json validity.
We need the same choice and check for global parameter.
(it's only an UI problem, backend support both, but currently if the json is incorrect, it is taken as a string, which is unlikely what the user wants)
Updated by Alexis Mousset over 4 years ago
- Subject changed from We can't choose between string and json fro global parameters to We can't choose between string and json for global parameters
Updated by François ARMAND over 4 years ago
- Related to User story #16301: Add JSON support for global parameters added
Updated by Raphael GAUTHIER over 4 years ago
- Status changed from New to In progress
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.0~beta3 to 6.1.0~rc1
Updated by Raphael GAUTHIER over 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2973
Updated by Raphael GAUTHIER over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|fe9666496514801090577d9fd778b75350c8291b.
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.0~rc1 which was released today.
Updated by François ARMAND over 4 years ago
- Fix check changed from To do to Checked
Updated by François ARMAND about 4 years ago
- Related to Bug #18556: Global parameters format is not preserved when editing added
Actions