Rather than having to delete and create a new topology/scenario config every time their respective yamls are edited, it would save a considerable number of keystrokes if "phenix config create" simply allowed the user to assign a file path to the config object. Then when issuing "phenix exp start ", the config would point to the yamls, delete existing entries for the topology/scenario, and re-create those objects from the edited yamls.
Rather than having to delete and create a new topology/scenario config every time their respective yamls are edited, it would save a considerable number of keystrokes if "phenix config create" simply allowed the user to assign a file path to the config object. Then when issuing "phenix exp start", the config would point to the yamls, delete existing entries for the topology/scenario, and re-create those objects from the edited yamls.