Hi Rahul Rahul_Mahajan. Thanks for your suggestions. For better tracking and to reflect Agile methodologies and workflows, please post any additional feedback regarding bugs or feature request as a feature request bug or issue directly at the project site. I've already submitted an issue as a feature request at the project 0026 site on your behalf here, so feel free to use this format for any future requests that you may have. This way it will be easier for us to both submit and resolve these types of requests, plus track the status and follow up using the same mechanism in GitHub. We can even check to see when updates are made to the code base by simply looking at the commit history.
I do agree with you that we can make this solution a little more flexible in terms of which workloads to deploy, so that's a great idea and I will add that to the sprint backlog. For the availability sets, I created availability sets for even single workloads to provide the option and flexibility to admins that may want to extend the solution with additional workloads in the future. At this point the implementation effort to update the code for excluding availability sets for the current single instances may not be worthwhile after-all. If anyone else would still like to have that option though, please submit an issue - feature request here and based on demand for that, we will consider implementing it. Thanks again so much for your interest and feedback 🙂