Tldr: Configuration for zork will now be managed on a per-project basis with the goal of enabling autonomous and flexible partner contributions and clearer API boundaries. Once we receive acknowledgement from key stakeholders, and complete the finishing touches on lining up the config, the migration CL will be submitted. An announcement will be sent out before the switchover.
Starlark will be used to generate Protocol Buffer configuration payloads in zork config repos (program, berknip, dalboz, ezkinil, morphius, trembyle, yoruk). model.yaml will be deleted from overlay-zork-private. A few resources to get started:
Changes will be made in the following repos:
CROS_WORKON_PROJECTto new zork repos noted above. model.yaml is deleted.
Why are we doing this migration?
A few benefits:
Will I need to change my ChromeOS platform code?
No. For the time being, the protobuf payloads will be translated backwards into JSON payloads conforming to cros_config_schema.yaml. From the platform point-of-view, the configuration will not change.
Will this break my builds?
No. During the migration, we will ensure that configuration generated by the new repos is the same as the configuration generated by model.yaml. Standard CQ coverage will apply to the migration CLs and stakeholders will be added as reviewers. Migration will be done in a single submission that can be reverted.
How will I cherry pick changes to branches?
If your project has not yet created branches, you will only need to cherry pick changes to the generated payloads in the new config repos. If your project has created branches, you will need to cherry pick the ebuild change to read the new config repos as well. The Boxster team will be available to assist in the cherry pick process.
We understand that getting used to the new configuration management ecosystem may take some time, and are committed to providing the best experience possible for partners and Googlers.