Config File For Multiple Proplets

[rodneyosodo]

I think we will also refactor the config file reading, since ideally, the config file product was supposed to give you the connection paramaters then you would copy them to an env and use them, but I will fix this in a following PR

Originally posted by @rodneyosodo in #131 (comment)

[JeffMboya]

This has been resolved. Here is how it works:

Provisioning (cli/provision.go)

When provisioning a single proplet, the config file gets a [proplet] section as before. When provisioning multiple proplets, the CLI generates numbered sections — [proplet1], [proplet2], etc. A new add-proplets subcommand (cli/add_proplets.go) was also added: it reads an existing config.toml, counts the current proplet sections, creates new SuperMQ clients for the additional proplets, and appends the new [propletN] sections to the file without needing to re-provision everything from scratch.

Config reading (proplet/src/config.rs)

The proplet binary now checks the PROPLET_CONFIG_SECTION environment variable to determine which TOML section to load, defaulting to proplet if unset. To run a second proplet pointing at its own credentials, set PROPLET_CONFIG_SECTION=proplet2 before starting the binary.

Example: running two proplets locally

# First proplet — uses [proplet] section (default)
./proplet

# Second proplet — uses [proplet2] section
PROPLET_CONFIG_SECTION=proplet2 ./proplet

This issue should be closed.