Actions
Bug #18556
closedGlobal parameters format is not preserved when editing
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
Hi,
When editing an existing global parameters in json format, the format is not preserve in the editing form and may lead to error if we change only the value and save without setting up the format again. After saving the format become string by default and can lead to error where the parameters is used for like in jinja templating.
Step to reproduce:
- create a global parameter in JSON format, save
- in the list of parameters, click on "edit" button for the one just created,
=> format is "string" in place of "json"
Updated by François ARMAND about 4 years ago
- Description updated (diff)
- Assignee set to François ARMAND
- Target version set to 6.1.7
Updated by François ARMAND about 4 years ago
- Related to Bug #17325: We can't choose between string and json for global parameters added
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/3422
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.7 to 6.1.8
Updated by François ARMAND almost 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|f6a505a3f9e2f0ffed98de4fb972dbcc15ee8c6f.
Updated by François ARMAND almost 4 years ago
- Fix check changed from To do to Error - Blocking
It is still not working with that PR.
Updated by François ARMAND almost 4 years ago
- Fix check changed from Error - Blocking to Checked
Updated by Vincent MEMBRÉ almost 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.8 and 6.2.1 which were released today.
Actions