Skip to content

Enable deploy v1 to deploy a v2 spec file #1464

Description

@josephjclark

We're changing the exported project.yaml file which lighting generates to use the new v2 spec format.

This means that anyone using CLI deploy v1 and exported project.yamls will find their deploys start breaking. This affects eg ethiopia but maybe others.

To preserve back compatibility, it would be neat for the v1 deploy to:

  1. detect if an incoming yaml is in v2 format
  2. convert it to v1 format (project has APIs for this)
  3. carry on as normal

No need to itervene in v1 pull.

Metadata

Metadata

Assignees

Labels

CLITracking issue to do with the CLIsync v2

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions