Issue

When we do cf push --no-start dora followed by cf restage dora we get the following error message:

❯ cf restage dora                          
This action will cause app downtime.

Restaging app dora in org o / space s as admin...

Staging app and tracing logs...
App has not finished staging
FAILED

We're not sure if this is expected behavior or a bug. If it i

The sample service broker is as below.

https://docs.cloudfoundry.org/services/managing-service-brokers.html

In this case, if a user creates a service instance, it should create or install the service and provide access to it.

We need reporting URL in credentials section Broker returns.

This will save documentation efforts from integrator side. For resource provider this will allow reading the URL in more standardized form. See PR #142 from cf-abacus-broker

_* The issue originally was reported in the deprecated cf-abacus-broker repo: https://gi

Maybe something magic happens and it all works just fine. Would be good to try it and document it at least.

To provide an easier way to install the cloud MTA build tool on MacOS or Linux machines it would be nice to have an own Homebrew Tap containing a formula for Homebrew (Package Manager for MacOS & Linux).

SAP has already provided such a Tap for SapMachine.

To help myself I created a Tap containing the mbt here: https://gith

I found that there's a duplication of logic between the job-secret-smuggler job (https://github.com/cloudfoundry-incubator/eirini-release/blob/3a1bc774dac7eb07b38a81f50edc112d3c8e3185/helm/eirini/templates/job-secret-smuggler.yaml#L25-L32) and eirini configmap (https://github.com/cloudfoundry-incubator/eirini-release/blob/3a1bc774dac7eb07b38a81f50edc112d3c8e3185/helm/eirini/templates/configmap.yam

The code in this repository forms the basis of the example exercise here.

I don't see where to report an issue against the pivotal page, so I'm reporting here in the hope that the loop is closed somewhere behind the curtains.

Here's what happens when I follow that exercise:

[russell]$ cf

Done with cloudfoundry/bosh-openstack-cpi-release#117 but not mentioned in the job spec.

See #231 – it seems like this could help people achieve their goals.

In critical environments, monitoring is a requirement.

So this service broker framework could offer an unauthenticated route like /status.

This route would be bound to a status() method in the ServiceBroker class.
By default, the status method would always return "OK".

Then, any developer using the framework could inherit or overload this status method for his own needs.