Properties
This section describes the supported properties of the a9s Deployment Updater component.
Service Broker Configuration
| Property | Default Value | Description |
|---|---|---|
service_broker.api_endpoint | The a9s Service Broker API endpoint of which the Service Instances should be updated. | |
service_broker.username | The a9s Service Broker username that should be used by the a9s Deployment Updater. | |
service_broker.password | The a9s Service Broker password that should be used by the a9s Deployment Updater. | |
service_broker.skip_ssl_validation | false | Indicates if the SSL validation for the a9s Service Broker connection can be skipped, e.g. when self-signed certificates are used. |
service_broker.ca | The CA used for the a9s Service Broker connection in PEM format. | |
service_broker.timeout | 120 | Timeout for requests to the a9s Service Broker in seconds. |
Strategy Configuration
| Property | Default Value | Description |
|---|---|---|
strategy.type | update | Strategy of the a9s Deployment Updater to be used. Available strategies are: update: all Service Instances of the specified instance_type are updated. recreate: all Service Instances known by the configured a9s Service Broker are recreated. |
There are different configuration options depending on the chosen strategy.type that are described in the following.
Strategy Configuration - Update
When using the strategy type update you have the following configuration options:
| Property | Default Value | Description |
|---|---|---|
strategy.update.instance_type | outdated | Service Instances to be updated. Available types are outdated, provisioned and failed. For more information see Instance Type. |
strategy.update.force_update | false | Update Service Instances for which the user has deactivated automatic updates. |
strategy.update.max_in_parallel | 1 | Specifies how many Service Instances should be updated in parallel at maximum. The a9s Deployment Updater will start as many threads as the number that has been set in this property. When an update of a Service Instance fails, the a9s Deployment Updater will stop with an error, but only after the currently running updates are done. Service Instances that have not been updated so far, will remain untouched. Important: Please be aware of the known Limitations. |
strategy.update.canaries | 1 | Specifies how many Service Instances should be updated as canaries before the remaining Service Instances are updated in parallel. The canary Service Instances will be updated sequentially independently what have been configured in strategy.update.max_in_parallel. As soon as one update of a canary Service Instance fails, the a9s Deployment Updater will stop with an error and the remaining Service Instances stay untouched. |
Instance Type
The property strategy.update.instance_type specifies which Service Instances should be updated:
- outdated: Only outdated Service Instances are updated.
A Service Instance is outdated if
- the template of the underlying deployment manifest has changed.
- one of the applied BOSH configs is outdated.
- one of the used BOSH releases is outdated.
- one of the used BOSH stemcells is outdated.
- provisioned: Only provisioned Service Instances are updated.
- failed: Only failed Service Instances are updated.
Strategy Configuration - Recreate
There are currently no configuration options when using the strategy type recreate.