On 14. 6. 2024 20:27, Jeremy Spewock wrote:
I think this is definitely a step in the right direction in terms of
how we structure the config files. Something that I think could also
be a cool improvement for how we handle configs is just making a
`conf/` directory and then taking all of the co
On 14. 6. 2024 20:32, Jeremy Spewock wrote:
On Mon, Jun 10, 2024 at 3:37 PM Nicholas Pratte wrote:
-def load_config(config_file_path: Path) -> Configuration:
+def load_config(node_config_file_path: Path, exec_config_file_path: Path) ->
Configuration:
"""Load DTS test run configura
On Mon, Jun 10, 2024 at 3:37 PM Nicholas Pratte wrote:
>
>
>
> > -def load_config(config_file_path: Path) -> Configuration:
> > +def load_config(node_config_file_path: Path, exec_config_file_path: Path)
> > -> Configuration:
> > """Load DTS test run configuration from a file.
> >
> > -L
I think this is definitely a step in the right direction in terms of
how we structure the config files. Something that I think could also
be a cool improvement for how we handle configs is just making a
`conf/` directory and then taking all of the configuration in each of
the yaml files present in
> -def load_config(config_file_path: Path) -> Configuration:
> +def load_config(node_config_file_path: Path, exec_config_file_path: Path) ->
> Configuration:
> """Load DTS test run configuration from a file.
>
> -Load the YAML test run configuration file
> +Load both the YAML testbe
This implementation splits the execution and node configuration
components of the conf.yaml into two separate config files. A
new command line argument is added, allowing the user to specify
both a node configuration file and an execution configuration
file. Be default, these config files are now n
6 matches
Mail list logo
