Partha,

Like Michal suggested, you can use cf-deployment and you'll likely have an
easier time working with the BOSH v2 CLI. In the meantime, the Release
Integration team is going to look into the issues caused by using the v2
CLI against cf-release.

On Mon, Jun 12, 2017 at 6:59 AM Michal Kuratczyk <mkuratczyk(a)pivotal.io>
wrote:

Hi,

I think you'd be better off with cf-deployment - it's a new way of
deploying CF, still under development but mature enough for test
environments. It's built to be used with CLIv2:
https://github.com/cloudfoundry/cf-deployment

Best regards,

On Wed, Jun 7, 2017 at 5:13 PM, parthasarathi_kundu(a)yahoo.com <
parthasarathi_kundu(a)yahoo.com> wrote:

Folks,

Is there any way to build cf-release using bosh cli v2 .

Currently I am stuck up while running

*./scripts/generate-bosh-lite-dev-manifest*

*Unknown command `status'.*

This is obvious as bosh cli v2 does not have status command . I tried to
follow the steps from
https://github.com/cloudfoundry/cf-release/blob/master/CONTRIBUTING.md

I have deployed the bosh-lite using bosh create-env .
--
Regards Partha

--
Michal Kuratczyk | Solution Architect | Pivotal Inc.
Mobile +48602421588 <+48%20602%20421%20588> | mkuratczyk(a)pivotal.io