ZOE 3.0.0 - Breaking change on zapp.yaml - Migration Automation

[FALLAI-Denis]

Hi,

Version 3.0.0 of Z Open Editor introduced a breaking change in the structure of property groups in the zapp.yaml file: the search for copybooks / includes is no longer operational (no compatibility mode) until the zapp.yaml file is modified to meet the new validation scheme.

Given that our sources are managed under Git, with many Repositories, but also many branches, this manual work of restructuring zapp.yaml files is cumbersome and error-prone, especially since it must be provided by developers and not by administrators.

It would have been desirable for the migration to be automatic through Z Open Editor:

• detection of the presence of a zapp.yaml file in the old format, (for example presence of a "property-groups" property)
• automatic triggering of a migration procedure from old format to new format, (it is considered that the old format zapp.yaml file is "well formed" and validated by its old schema)

In the absence of this automation integrated into Z Open Editor, would you be able to provide a migration script for the zapp.yaml file to be triggered manually to avoid input errors and the loss of time performing this migration manually?

We can develop this migration script ourselves, but I think that all users will have exactly the same problem and will have to do exactly the same migration, with the same transformation rules.

[phaumer]

Thanks. That was the reason we posted about these breakages and shown the new format in the discussion forum early so that people could prepare.

Writing a script will take development resources away from other work; so we have to evaluate the pros and cons. If other users also feel strongly about it, please let us know in this issue.