### Introduction The Geo team is currently building [a self-service framework](https://docs.gitlab.com/ee/development/geo/framework.html) to make it incredibly easy to add new Resources to Geo. The first iteration of the self-service framework will cover blobs (essentially files) to be replicated with minimal effort. The second iteration focused on replication of git repositories via versioned snippets. This epic tracks the work to be performed so that Geo moves all already existing datatypes to the new framework. ### Problem to solve <!-- What problem do we solve? --> Adding replication for new Resources was hard. We still don't support replication (and verification) for a large number of features that rely on blobs and git repositories. The current list of what is and is not replicated/verified is availabe in https://docs.gitlab.com/ee/administration/geo/replication/datatypes.html#limitations-on-replicationverification ### Intended users * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Sydney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> In case a Geo customer needs to failover the more data is replicated and verified the better. This means no additional steps need to be performed. ### Proposal * Move all existing datatypes to the framework ### Documentation We need to update https://docs.gitlab.com/ee/administration/geo/replication/datatypes.html#limitations-on-replicationverification ### Testing The testing needs should be covered mainly by the self-service framework. We should also test for performance e.g. for LFS files (relevant to verification). ### What does success look like, and how can we measure that? - Percentage of replicated and verified data types ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> * Premium * Ultimate ### Links / references