ASGARD-1273 pump the maximum number of ASGs allowed in a cluster
ASGARD-1273 adding support for configuring clusters
retire static cluster properties
initial, mindless conversion
Fix NPE on task.thread premature usage in debug message
Merge pull request #493 from joesondow/fix-task-start-bug

Fix NPE on task.thread premature usage in debug message
Unit test for TaskService.startTask
fixing merge
Merge pull request #494 from joesondow/unit-test-taskService-startTask

Unit test for TaskService.startTask
Moved logic into ServerService to decide whether a filter ought to block user requests due to cache loading at startup.

This will make part of the logic more testable by moving it out of LoadingFilters, because LoadingFilters turns out to be surprisingly difficult to unit test effectively.
ASGARD-1286 - Runtime flag to skip cache load

Instead of relying on a startup skipCacheLoad flag only, allow a runtime flag to be set through FlagController, FlagService, and Flag, to skip caching loading even if Asgard is already running and trying to load caches.

This gives Asgard admins an emergency quick back door to bring up a new Asgard instance that is working sufficiently well for use (based on the admin's personal judgement about the situation). This is for times when the existing Asgard instance is behaving very badly and needs to be replaced, but at the same time Amazon is also having problems with a surprising new type of cloud object listing. Last month it was volumes, this month it's snapshots, next month it could be something else.
suppress oppressive codenarc violation. In this circumstance, null return is fine
Merge branch 'master' of github.com:Netflix/asgard
Merge pull request #497 from joesondow/ASGARD-1286-Runtime-flag-to-skipCacheLoad

ASGARD-1286 runtime flag to skip cache load
updates from code review
Docs and style
ASGARD-1287 - Health check should fail if caches are missing during startup but should pass if caches are missing later

This change to the health check will enable us to have the desired behavior from ELBs at each of Asgard's lifecycle phases.

During startup, it's important that Asgard fail its health check while loading caches so that ELB traffic will not be directed to a non-ready Asgard.

After cache loading ends, it's important that ELB traffic continue to flow to the single canonical Asgard instance even when Amazon or Asgard has a problem that causes one of the caches to become temporarily empty. If the initial cache loading processes are done OR SKIPPED then the health check should liberally return 200 so traffic is allowed to reach the Asgard instance.

After careful consideration, I realized the existing logic for constantly checking whether the caches were full was not a useful health check for traffic decisions, at least until Asgard is sufficiently stateless that we can run many concurrent identical Asgard instances that all take traffic from the same source. When we get there, we can craft a better health check that regards more than just the default region, and possibly something better than whether a few caches have items in them. For now, we're better off with a load balancer health check that only fails during server initialization.
Added HTTPS as option when creating load balancer listeners.

Asgard will use SSL certificate specified by cloud.defaultElbSslCertificateId
Fixing failing test:  No such property: controller for class: com.netflix.asgard.LaunchConfigurationControllerTests
Fixing CodeNarc violations