Bug 51999 - Treat emtpy UCRV as "unset"
Treat emtpy UCRV as "unset"
Status: NEW
Product: UCS
Classification: Unclassified
Component: UCR
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-09-11 16:14 CEST by Christian Völker
Modified: 2020-09-16 08:46 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.091
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2020090921000266
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Völker univentionstaff 2020-09-11 16:14:28 CEST
UCRV which are set to an empty string as follows:

ucr set foo/bar=""

Should be automatically unset:
ucr unset foo/bar

Several issues occur with variables being set to an empty string. See ticket comment #10.


Customers setting variables to an empty string does not expect them to have any effect. 
Same applies when customers use the UMC. They set the value and remove it afterwards. But as the value field is empty the variable is not unset and causes issues.

We should change ucr command to unset UCRV when they are set to an empty string.

See also Bug #42170 and Bug #51003
Comment 1 Ingo Steuwer univentionstaff 2020-09-16 08:46:36 CEST
This would be an API change which might lead to problems in UCR templates which expect this behaviour. This can only be done in a point or major release.