Open benbp opened 2 years ago
This should be considered super long term stretch goal, IMO. If anything the script can just print out the proper command lines for some of these things (ie, dry-run).
A full overhaul of the text UI is a stretch, but I think there are some operations that would be helpful to add today, like image build only, use local addon, and show test.
In my experience, people rarely look at or discover the command line output or would know which ones can be run standalone.
See https://github.com/Azure/azure-sdk-for-net/pull/28320#discussion_r855675487
We should support more fine grained operations in dev usage of the stress scripts. Right now the script is written with the approach that its goal is to build and deploy a stress test to a cluster. However, it would be more useful to take an approach that focuses on automating various operations, like
deploy
,build
,buildImage
,debug
. For example, we have some custom configuration around building of dockerfiles with external directories. In order to find the correct docker command you have to run the deploy script and copy the command from the log output. It would be better to just provide a sub-command or function likebuildImage
for this case.Operations I can think of that we do today, some via the script and some manual: