RESTful API: Activating a configuration: Difference between revisions
(Added category FAQ) |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:RESTful API: Activating a Configuration}} | |||
== Activating a configuration == | == Activating a configuration == | ||
tbconfig /systems/system_1/target_configuration="config_new" -u <username> -p <password> | tbconfig /systems/system_1/target_configuration="config_new" -u <username> -p <password> | ||
| Line 4: | Line 6: | ||
tbstatus /system::target_configuration=config_new -r -u <username> -p <password> | tbstatus /system::target_configuration=config_new -r -u <username> -p <password> | ||
where username and password is one of your valid user and password to log in the webportal | where username and password is one of your valid user and password to log in the webportal | ||
[[category:FAQ]] | |||
Latest revision as of 10:48, 11 January 2023
Activating a configuration
tbconfig /systems/system_1/target_configuration="config_new" -u <username> -p <password>
or
tbstatus /system::target_configuration=config_new -r -u <username> -p <password>
where username and password is one of your valid user and password to log in the webportal