Beyhan Veli

I like it better. It also opens the door for other "updates" if needed.

Hello @a-b, Do you plan to offer build binaries for linux-arm64 after this is merged?

I think this can be closed now because https://github.com/cloudfoundry/cli/pull/2314 got merged.

We would love to review a PR if you want to contribute.

I'm not sure how the generic API metrics are supposed to work at all because: - As defined in the [director job](https://github.com/cloudfoundry/bosh/blob/3a31bc2a63d69a7bc1df8d7bac2a5cc8d6ca2b71/jobs/director/templates/metrics-server#L5-L6) the metrics-server is started as a different process....

Good catch @jpalermo. [This](https://github.com/cloudfoundry/bosh/commit/f0873641303095818b34d39035ee0a672d305e77) is the commit which introduced the change. It looks like initially the `/api_metrics` were called `/director_metrics` but yes they redirect to the director process which I...

I'm wondering what is missing to get this in?

I also asked in the CLI Slack channel https://cloudfoundry.slack.com/archives/C032824SM/p1686818021365519

It is a CPI configuration. E.g. in AWS CPI https://bosh.io/docs/aws-cpi/#global if you configure the `encrypted` global property all volumes are encrypted as documented in the link above.

If you set the global property as [in](https://github.com/cloudfoundry/bosh-deployment/blob/95999496137cfffbf81de65ad8fc74305b365b6d/aws/encrypted-disk.yml#L13-L15) this will encrypt all newly created volumes. This property won't trigger encryption for existing volumes.