At some point between initialization and 'up', the aggressive clean is removing the environment file for the Slurms. Because of this, the DevEnv stops execution and the site doesn't come up.
I suspect this affects only Slurm because that stack is complicated and largely auto-generated and does things differently from the others. I'm not sure if it's better to change the behavior of the Slurms or to change the behavior of 'agro'. I think that if the latter cleaned the env directories before initialization, that would fix the problem
To Reproduce:
Start the DevEnv using the command above.
Expected behavior
Using a cleaning operation, even an aggressive one, does not remove critical files after they are generated.
Tool: Developer Platform
Bug Description: When using:
At some point between initialization and 'up', the aggressive clean is removing the environment file for the Slurms. Because of this, the DevEnv stops execution and the site doesn't come up.
I suspect this affects only Slurm because that stack is complicated and largely auto-generated and does things differently from the others. I'm not sure if it's better to change the behavior of the Slurms or to change the behavior of 'agro'. I think that if the latter cleaned the env directories before initialization, that would fix the problem
To Reproduce: Start the DevEnv using the command above.
Expected behavior Using a cleaning operation, even an aggressive one, does not remove critical files after they are generated.