|
2016-05-08
| ||
| 23:02 | • Closed ticket [fea7457de3]: Add last file a variable came from in -show-config and -show-runconfig plus 4 other changes artifact: 0eae115adc user: matt | |
|
2016-04-22
| ||
| 15:37 | • Closed ticket [fea7457de3]. artifact: 02a020b46d user: mrwellan | |
|
2015-09-18
| ||
| 17:48 | • Ticket [fea7457de3]: 3 changes artifact: 1f7d97a6d4 user: tyardeni | |
| 17:44 | • Ticket [fea7457de3]: 5 changes artifact: 9f86e2fdbb user: tyardeni | |
| 17:39 | • New ticket [fea7457de3]. artifact: d50ada22ec user: tyardeni | |
| Ticket Hash: | fea7457de36d2270d7fe06e8159efb46b94ac2da | |||
| Title: | Add last file a variable came from in -show-config and -show-runconfig | |||
| Status: | Closed | Type: | Feature_Request | |
| Severity: | Important | Priority: | Immediate | |
| Subsystem: | Resolution: | Fixed | ||
| Last Modified: | 2016-05-08 23:02:27 | |||
| Version Found In: | 1.6024 | |||
| Description: | ||||
|
Would like to know the last file read to determine a variable name in -show-config and -show-runconfig.
More detail to follow. | ||||
| User Comments: | ||||
|
tyardeni added on 2015-09-18 23:44:59:
Current -show-runconfig output is as follows:
(("default"
("VAR1" "val1")
("VAR2" "val2"))
("target"
("VAR2" "val2")
("VAR3" "val3")))
This tells me what the settings are but with the ability to nest includes, does not tell me when the variable was last set. The output from -debug 9,11 is hard to read. I would like to see the tuple containing the variable extended to include the file name, so if I have includes the output would look something like:
(("default"
("VAR1" "val1" "global.runconfigs.config")
("VAR2" "val2" "user.runconfigs.config))
("target"
("VAR2" "val2" "global.runconfigs.config")
("VAR3" "val3" "runconfigs.include")))
Any other metadata would be great. tyardeni added on 2015-09-18 23:48:18: One more minor extension, a command line option to generate the output as a table: megatest -show-runconfig -target target Section Key Value Source ------- --- ----- ------ default VAR1 val1 global.runconfigs.config target VAR2 val2 user.runconfigs.config target VAR3 val3 runconfigs.include matt added on 2016-05-09 05:02:27: Done. To use specify -debug 0,9 to force debug mode 9. | ||||