Avoid boolean for non_transactional specs

So we can introduce truncation as another strategy
API for assigning/unassigning AppSecurityGroups as staging defaults

* filter_dataset allows you to filter collections

[#71584816]

Signed-off-by: Joseph Palermo <jpalermo@pivotallabs.com>
Switch to truncation for non_transactional specs

[#72461888]
Use a dynamic list of tables to detect pollution

[#72455546]
Api Documentation for AppSecurityGroupStagingDefaults endpoints

[#71584816]

Signed-off-by: Joseph Palermo <jpalermo@pivotallabs.com>
Run all controller specs in single suite

Now that they are faster the split has more overhead than it avoids

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>
can connect to tps on non standard port

Signed-off-by: Ted Young <tyoung@pivotallabs.com>
stub out stats_for_app for diego

Signed-off-by: Ted Young <tyoung@pivotallabs.com>
only report instances that are within the app desired instance count

Signed-off-by: Ted Young <tyoung@pivotallabs.com>
Diego reporter properly returns DOWN instances now.

-move app stopped errors into stats controller and out of dea client.

Signed-off-by: Zach Robinson <zrobinson@pivotallabs.com>
API for assigning/unassigning AppSecurityGroups as defaults for running apps

Signed-off-by: James Myers <jmyers@pivotallabs.com>
Avoid recreating tables in acceptance specs

It turns out these specs were reliant on transaction isolation anyway and the transaction does not seem to get in the way of communicating with CC

Signed-off-by: Abhijit Hiremagalur <abhi@pivotallabs.com>