diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-12-21 09:09:12 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-12-21 09:09:12 +0300 |
| commit | 4cd1329b80b80890881be6503958612de3cfdd17 (patch) | |
| tree | 3f935c51aa87d5072708f7090a7e7b45be642a21 /doc/development/geo.md | |
| parent | 6f2278bd4a548e432b0429a9576ab896460941b2 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/geo.md')
| -rw-r--r-- | doc/development/geo.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/development/geo.md b/doc/development/geo.md index 76c75cb1c6a..ee76c54decc 100644 --- a/doc/development/geo.md +++ b/doc/development/geo.md @@ -602,6 +602,8 @@ For comparison with your own features, see [Supported Geo data types](../adminis If you add a feature that is backed by Git repositories, then you must add Geo support. See [the repository replicator strategy of the Geo self-service framework](geo/framework.md#repository-replicator-strategy). +Create an issue based on the [Geo Replicate a new blob type template](https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Geo%20Replicate%20a%20new%20blob%20type) and follow the guidelines. + ### Blobs If you add a subclass of `CarrierWave::Uploader::Base`, then you are adding what Geo calls a blob. If you specifically subclass [`AttachmentUploader` as generally recommended](uploads/working_with_uploads.md#recommendations), then the data has Geo support with no work needed. This is because `AttachmentUploader` tracks blobs with the `Upload` model using the `uploads` table, and Geo support is already implemented for that model. @@ -610,6 +612,8 @@ If your blobs are tracked in a new table, perhaps because you expect millions of [Geo detects new blobs with a spec](https://gitlab.com/gitlab-org/gitlab/-/blob/eeba0e4d231ae39012a5bbaeac43a72c2bd8affb/ee/spec/uploaders/every_gitlab_uploader_spec.rb) that fails when an `Uploader` does not have a corresponding `Replicator`. +Create an issue based on the [Geo Replicate a new Git repository type template](https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Geo%20Replicate%20a%20new%20Git%20repository%20type) and follow the guidelines. + ### Features with more than one kind of data If a new complex feature is backed by multiple kinds of data, for example, a Git repository and a blob, then you can likely consider each kind of data separately. |