Currently App Broker allows users to specify mutually exclusive
manifest properties - specifically `routes` along with any combination
of the deprecated `host`, `hosts`, `domain` and `domains`. This change
makes `routes` take precedence if specified.
- Add PMD checks and resolve failing rules
- Apply Spring Checkstyle rules based on Spring Framework
- Rearrange imports to be more consistent
- Format whitespace
This property is supported by CAPI and `domain` is just a configuration
shortcut. However for compatibility reasons existing `domain` property
can't be removed, instead new `domains` property is added. When both are
provided in the request, `domains` will take priority.
Before only error message was dispalyed in logs providing no
information, like exception details or stacktrace. Now error message is
logged together with exception, including stacktrace.
When the backing applications and services are in created in a separate space, the space can get deleted before we get into the delete backing service instance step.
Ideally, the deletion of the space should be handled after the backing apps and backing service instanes are deleted.
Connected to https://github.com/spring-cloud/spring-cloud-app-broker/issues/267
Before every update-service call would upgrade the backing application.
This changes will only create a new application package when the flag upgrade is provided.
When using the space per service instance strategy, currently the OAuth
client requires `cloud_controller.admin` privileges to deploy apps and
services to a new space. This commit adds support for dynamically granting
the space developer role to a client which has the org manager role but not
admin privileges.
Resolves#203
Requiring client credentials to run ATs
- `CloudFoundryOperationUtils` was accessing the default org
to get operations, which in some cases wasn't correct, e.g.
when getting a service instance not created in the default org.
To solve this problem, we're now exposing a new method `getOperationsForOrgAndSpace`,
which gets the operations in the organization and space specified.
This commit adds support to stop, start, restart, and restage the backing
applications associated with a deployed service instance. The management
functions are available from the new `BackingAppManagementService`.
Resolves#118
Added TargetService to update flow
Added explicit assertion on backing app containin initial parameters afer an update
Updated AT to consider Updates with Target
Added ATs for multiple apps
Not failing when CF returns a DB error when creating a space
Not failing when space does not exist
Connected to #93
