Shouldn't we rather do something similar to atomate2 settings?

Or this approach? https://github.com/materialsproject/pymatgen/blob/da607e86f9ce8aec942067c6c1a4fda6e04915dd/src/pymatgen/io/vasp/sets.py#L86

Hi @JaGeo , i think both above approach we can use to load the default yamls, which I plan to do next : similar to atomate2 settings

But we would still need postinit in the maker if we expect user to provide modified yaml path (so it gets read when the flow is created) and we don't want to copy that yamls to remote cluster. Due to nature of jobflow delayed execution

@naik-aakash okay! Likely pymatgen approach is th closest to what we want for defaults

Another thought: post init will not work if you initialize the flow during run time