Refactor select2 avoidance mechanism
Start comments with capital letter
ASGARD-1146 - Allow short app names in select2 inputs
Merge pull request #304 from joesondow/ASGARD-1146-short-app-names-in-select2

Asgard-1146 - Short app names in select2
ASGARD-1147 - Upgrade CodeNarc to 0.18.1

CodeNarc 0.18+ includes a bug fix that removes a lot of false
positives from Asgard's code violations.
https://sourceforge.net/p/codenarc/bugs/116/
Reduce CodeNarc violations
Merge pull request #305 from joesondow/ASGARD-1147-Upgrade-to-CodeNarc-0.18.1

Asgard-1147 - Upgrade to CodeNarc 0.18.1
Configuring Grails to write its stacktrace.log file to the same directory as the Asgard log file to avoid permission exceptions when running in Tomcat on Ubuntu
Fix offline mode
ASGARD-1137 - Expose ELB "other" policies

These are the policies we're most concerned with today
because they can include the cross-zone routing policy.
ASGARD-1152 - 2nd block device for M3 instance types

Needed until a new Base AMI gets released to handle single-device configs better.
Merge pull request #309 from joesondow/ASGARD-1152-two-block-devices-for-m3

ASGARD-1152 - 2nd block device for M3 instance types
Fix comment
ASGARD-1117 - Prevent double form submission

It's common for people to click a submit button twice by accident or
due to impatience. When that happens for a case like Create Next ASG,
a second task will be created and will fail because the ASG name is
already taken. These errors are distracting, useless noise for the
user, the task list, the log, and Asgard developers.
ASGARD-1153 - Rolling Push block device mappings

Just as a Red Black Push completely replaces all Block Device Mappings based on the standard configuration for the new instance type, the Rolling Push should do the same. There is no convenient way for Asgard users to create their own choice of block device mappings anyway.

Even in the case where a power user created a Launch Configuration with the command line and chose their own Block Device Mappings, there is no consistent, reliable, simple algorithm to determine which of those mappings to retain, which ones to delete, and which ones to replace with standard mappings. We're working around Amazon's lack of a proper instance types API, and their lack of automatic helpful behavior for launching m3 instance types.
Merge pull request #311 from joesondow/ASGARD-1153-rolling-push-block-device-mappings

ASGARD-1153 - Rolling Push block device mappings
Merge pull request #307 from joesondow/ASGARD-1137-expose-ELB-policies

ASGARD-1137 - Expose ELB policies
Merge pull request #306 from pas256/master

Write stacktrace.log to a better location
ASGARD-1157 - Fix fast property breakage
Merge pull request #312 from joesondow/ASGARD-1157-Fix-fast-property-breakage

ASGARD-1157 - Fix fast property breakage