Update to recursively remove a user from each space associated with an organization.
Support for setting a default disk_quota for newly pushed apps.
Fix typo in the app_usage_event_api_spec

Apparently I can't type and I'm a terrible spell check.
Merge pull request #200 from sykesm/fix-api-typo

Fix typo in the app_usage_event_api_spec
Remove detected_buildpack_guid from app api.

* First step to rethink our buildpack strategy

Signed-off-by: Matthew Sykes <matthew.sykes@gmail.com>
Add detected_buildpack_name to apps.

* Remove buildpack_name and buildpack_guid from app model.
* Change staging task to always save buildpack guid when available.
* Do not expose detected_buildpack_name and detected_buildpack_guid to API.

Signed-off-by: Matthew Sykes <matthew.sykes@gmail.com>
Maintain detected_buildpack info when seeding app usage events

Signed-off-by: Matthew Sykes <matthew.sykes@gmail.com>
Fix tests that assume no dirty db state

* In mysql, tests are not running in transactions and in a random order so
  they can leave states behind. We have to use less strict matchers.

Signed-off-by: Matthew Sykes <matthew.sykes@gmail.com>
Change blueprints to use example.com

Signed-off-by: Matthew Sykes <matthew.sykes@gmail.com>
Show specific error when match_app fails.

Signed-off-by: Matthew Sykes <matthew.sykes@gmail.com>
Use UAA's transaction endpoints for create/update/delete of clients

Includes some refactoring of:
- ServiceBrokerRemoval => ServiceBrokerRemover
- uaa command interface changed from apply! to db_command and
  uaa_command
Add ssl support when modifying dashboard clients with UAA.
Handle 404 when requesting token from UAA
Return meaningful errors when the UAA returns an error during
create/update/delete service-broker
Remove buildpack_name and buildpack_guid from app usage events.

* This is because we don't have the app detected build pack names and guid at
* the time a start event get generated. They only become avaiable when staging
* is done and passed back by the DEAs.

Signed-off-by: Kai Zhang <kaizhang@cn.ibm.com>
Remove unused code.

- all these were replaced by the modify_transaction method
ServiceDashboardClientDiffer accepts dashboard clients, not catalog services

-dashboard client differ should not know anything about catalogs
Move dashboard client delete logic into ServiceDashboardClientManager

- now that we use the uaa transactional endpoint, the logic for making
  CC claims and modifying clients on uaa is always the same. move it to
  the object that should know how to do that.
Rename X-Cf-Warning header to X-Cf-Warnings

- also create helper method to add warnings to the warning list returned
  in the header.
Dispaly warning to operator if dashboard sso feature is used but disabled

[#65141758]