Bug 2522 - tl-config should warn when creating new parameters
Summary: tl-config should warn when creating new parameters
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Version: pre-1.0
Hardware: PC Linux
: P2 Enhancement
Target Milestone: 4.13.0
Assignee: Linn
URL:
Keywords: prosaic, wilsj_tester
Depends on:
Blocks:
 
Reported: 2007-09-21 16:40 CEST by Peter Åstrand
Modified: 2021-07-22 12:33 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:
* When adding a new parameter, you should see a message saying "Created new parameter: <param>". * When updating the value of an existing parameter, no message should be shown


Attachments

Description Peter Åstrand cendio 2007-09-21 16:40:53 CEST
If you misspell some parameter name, say:

tl-config /vsmagent/agen_hostname=1.2.3.4

you will get no clue about this. I think tl-config should say something like:

"Created new parameter /vsmagent/agen_hostname"

See also discussion in komintern, starting with article 301499.
Comment 2 Linn cendio 2021-04-20 10:25:11 CEST
Tested on Fedora 33 and it works as expected. Use for example this command to set a variable:
> sudo /opt/thinlinc/bin/tl-config test=123

Tested:
✓ Creating new variable
✓ Updating value of existing variable
✓ Removing parameter
Comment 5 Linn cendio 2021-04-22 12:13:31 CEST
Retested the following on Fedora 33 and still works as expected.

✓ Creating new variable
✓ Updating value of existing variable
✓ Removing parameter
Comment 6 William Sjöblom cendio 2021-04-26 14:02:53 CEST
Tested on Fedora 33 on Jenkins build #2013, using UTF-8 encoded variable names both inside and outside the ASCII range. 

✓ Creating new variable
✓ Updating value of existing variable
✓ Removing parameter
Comment 7 William Sjöblom cendio 2021-04-26 14:02:53 CEST
Tested on Fedora 33 on Jenkins build #2013, using UTF-8 encoded variable names both inside and outside the ASCII range. 

✓ Creating new variable
✓ Updating value of existing variable
✓ Removing parameter

Note You need to log in before you can comment on or make changes to this bug.