Publish maintenance_info to osb clients

[gberche-orange]

• As a coab operator
• In order to expose service update to users including new dashboard urls returned
• I need the maintenance_info to be returned to OSB clients, so that osb client can request a service instance update and receive a refreshed service instance view with an updated dashboard url

Acceptance test scenario

S1: catalog

• Given a coab instance is configured with the following flags
  • maintenance_info.version: the osb-cmdb version
  • maintenance_info.description: the osb-cmdb description of the update
• Then /v2/catalog returns the specified maintenance_info

S2: service provisionning

• Given a coab instance is configured with the following flags
  • maintenance_info.version: the osb-cmdb version
  • maintenance_info.description: the osb-cmdb description of the update
• When service instance provisionning request is received
• Then the coab-vars.yml includes the specified maintenance_info

S3: service update: ignored when maintenance_info match

• Given a coab instance is configured with the following flags
  • maintenance_info.version: v48
  • maintenance_info.description: "mariadb update y"
• And service instance exists with maintenance info

"maintenance_info": {
        "version": "v47",
        "description": "mariadb version update to x"
      }

• When a service instance update request comes with

"maintenance_info": {
        "version": "v47",
        "description": "mariadb version update to x"
      }

• Then no git commit is made to trigger a COA build
• And the service instance update status is a 200 to indicate the request's changes have had no effect
• And a response body includes the configured dashboard url (see Dashboard step1: pass thru support (without CF sso support) #47 )

S4: service update: triggers COA pipeline when maintenance_info don't match

Note: This is delayed and moved into #245 instead

• Given a coab instance is configured with the following flags
  • maintenance_info.version: v48
  • maintenance_info.description: "mariadb update y"
• And service instance exists with maintenance info

"maintenance_info": {
        "version": "v47",
        "description": "mariadb version update to x"
      }

• When a service instance update request comes with

"maintenance_info": {
        "version": "v48",
        "description": "mariadb version update to y"
      }

• Then git commits are to trigger a COA build
• And the service instance update status is a 202 to indicate Service Instance update is in progress.

[gberche-orange]

Scenario S3 was descoped as cloudfoundry CLI prevents such scenario.