One of the most frustrating things for a developer is to discover a template, get excited about it, try to use it... only to discover half way through this that they do not have the right permissions, configuration, subscription, etc... Worse, would be if there is some kind of unintended side effect, e.g. some resource got provisioned and not cleaned up on failure, that results in the developer getting upset. (The most obvious is billing, but there a lots of others).
We should have "pre-flight" checks on both the client, e.g. I have npm and git installed, as well as within the Azure subscription. The result of this should provide a clear indication of what will occur, e.g. what resources will be created, etc.
One of the most frustrating things for a developer is to discover a template, get excited about it, try to use it... only to discover half way through this that they do not have the right permissions, configuration, subscription, etc... Worse, would be if there is some kind of unintended side effect, e.g. some resource got provisioned and not cleaned up on failure, that results in the developer getting upset. (The most obvious is billing, but there a lots of others).
We should have "pre-flight" checks on both the client, e.g. I have npm and git installed, as well as within the Azure subscription. The result of this should provide a clear indication of what will occur, e.g. what resources will be created, etc.