Matthias Vach

Hallo danke für die Antwort, ich werde meine Fragen per mail stellen.

Hi @ragaskar, today I faced the issue again while trying to use locally build AWS CPI. ``` releases: - name: bosh-aws-cpi - sha1: sha256:62173e9bb987b92355836334037175a33223a16d8eb42a8b22d9b9a81b2240be - url: https://:@repositories.sap.ondemand.com:443/nexus/content/groups/build.milestones/com/sap/cp/cloudfoundry/bosh-source/aws-cpi-release/93/aws-cpi-release-93.tgz - version: '93'...

The storage cli will be implemented in: https://github.com/cloudfoundry/bosh-ali-storage-cli There is already a PR that provides the the initial version: https://github.com/cloudfoundry/bosh-ali-storage-cli/pull/1

A very similar integration of the azure-storage-cli into bosh was already done in https://github.com/cloudfoundry/bosh/issues/2457

The CI integration for azure-storage-cli will be added with: - https://github.com/cloudfoundry/bosh-ali-storage-cli/pull/3 - https://github.com/cloudfoundry/bosh-ali-storage-cli/pull/4

Hi, as show case I implemented a tiny puma and prometheus-client integration which serves the expected webserver access metrics https://github.com/mvach/PumaMetricsExample. Sadly I don't see the difference to the current director...

:-) @beyhan, I just noticed that right now and wanted to update the issue.

Currently plan is to implement that at the end of April or beginning of May.

Hi it seems that I'm experiencing just the same issue. Version 1.23.1. is working fine but from 1.24.0 on the issue pops up.