We are automatically deploying agents with the fglcmd command.
This works fairly well, but I had a problem with the agent:deploy command. I had a script agent that I went through many iterations fixing it. I finally removed all the agents version by removing the deployed cartridges. Unfortunately this caused me problems when I deployed the new version. Fglam silently ignored the deployment because it had a higher version number of the cartridge already installed.
So I deployed the new cartridge over and over again and it looked like it worked, but it did not.
This is my fault for removing the version numbers.
But it would have cause me less problems if these arguments existed.
1. The agent:deploy command could return a non-zero exit code.
2. The agent:deploy command could take a "-force" option to force the over-writing of the newer version with the cartridge being deployed. (i did use -force, but it did not work this way).
3. An agent:undeploy command would be helpful to remove the old broken cartridges.
4. The agent:deploy command could write "ignoring deployment: a cartridge of version XXX already exists in fglam" to the standard output or error device.