A next step in automated lab deployment and configuration would be to have a one-click deployment&configuration.
This could be done by augmenting the lab definition file with a structure that would tell which command(s) should be executed once the lab is deployed.
For instance, the remote command that would clone the repo and pull the CATS container could be executed if nuxctl connects to the jumbox (once lab is ready) and invoke the command(s).
The user-specific variables that are missing in the vars.robot file of a lab could be as well provided beforehand by a user using the same (or different) file
A next step in automated lab deployment and configuration would be to have a one-click deployment&configuration.
This could be done by augmenting the lab definition file with a structure that would tell which command(s) should be executed once the lab is deployed.
For instance, the remote command that would clone the repo and pull the CATS container could be executed if nuxctl connects to the jumbox (once lab is ready) and invoke the command(s).
The user-specific variables that are missing in the vars.robot file of a lab could be as well provided beforehand by a user using the same (or different) file