There is software that relies on this repository as principal internal data storage. Software is used to browse registry data and to file/review/resolve change requests.
There are some implications:
There is a commit coming where the data in this repository will be overwritten by the app, with YAML serialized in Node’s js-yaml fashion. This will be a one-time big diff.
After a registry/glossary management app starts being used in production by a customer, legacy data migration script cannot overwrite the repository anymore. This can generate unrelated diffs and possibly cause users to encounter merge conflicts while operating the app.
mlgt-data submodule will be removed (this is already in a PR). We want Git operations performed by software to be as smooth as possible to the user, so we don’t want it to download binary blobs that are not needed for app to function.
Software branding will be added (this is already in a PR).
There is software that relies on this repository as principal internal data storage. Software is used to browse registry data and to file/review/resolve change requests.
There are some implications:
There is a commit coming where the data in this repository will be overwritten by the app, with YAML serialized in Node’s js-yaml fashion. This will be a one-time big diff.
After a registry/glossary management app starts being used in production by a customer, legacy data migration script cannot overwrite the repository anymore. This can generate unrelated diffs and possibly cause users to encounter merge conflicts while operating the app.
mlgt-data submodule will be removed (this is already in a PR). We want Git operations performed by software to be as smooth as possible to the user, so we don’t want it to download binary blobs that are not needed for app to function.
Software branding will be added (this is already in a PR).