Closed Badgerati closed 7 years ago
When creating IaaS in Azure, certain resources having naming convention length limits (like passwords must be 12-123 chars).
Fogg doesn't check naming conventions during validation, so this issue is to add in support for the most common ones:
(for the username/password, if possible, ask 3 times if the requirements aren't met, then fail)
More can be added in later for things like availability sets.
When creating IaaS in Azure, certain resources having naming convention length limits (like passwords must be 12-123 chars).
Fogg doesn't check naming conventions during validation, so this issue is to add in support for the most common ones:
(for the username/password, if possible, ask 3 times if the requirements aren't met, then fail)
More can be added in later for things like availability sets.