Re: Removing Support for v1 Style Manifests


Morgan Fine
 

Hi all,

A few clarifications and questions that have come up. While the create-env flow is still using "v1 manifest" structure, that code path does not involve the BOSH director itself as create-env is done in the CLI. To that end, we are not intending to change the create-env manifest structure at this time, only the manifest structure used in `bosh deploy` commands. 

In regards to what are we intending to remove, at a high level, we are intending to remove the sections from the v1 manifest page that have migrated to v2 syntax:
  • Deployment Identification i.e. "director_uuid"
  • Networks
  • Resource Pools
  • Disk Pools
  • Compilation
  • Jobs becomes Instance Groups
Best,
Morgan

On Thu, Mar 21, 2019 at 8:10 AM Stanislav German-Evtushenko <s.germanevtushenko@...> wrote:
How to know what exactly is planned to be removed? I remember some overlaps between v1 and v2 as well as not explicitly documented features which worked.

What happens to bosh create-env manifest, will it be documented separately? As of now, it's a mix of both (v1 and v2) because it should support cloud properties.

Good time to update bosh-deployment btw.

Join cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.