Geo group issues requiring attention
Hi @fzimmer,
Here is a list of feature proposals without a milestone.
We would like to ask you to determine whether this issue should be scheduled or closed. For each issue please:
- Close the issue out if it is no longer relevant or a duplicate.
- Assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
For the issues triaged please check off the box in front of the given issue.
Please work with your team to complete the list this week.
-
#5698 (closed) Handle accepting terms for Geo ~"Geo", auto updated, devopsenablement, feature -
#5398 (closed) Use materialized view over Geo FDW tables Architecture decision, ~"Geo", ~"Geo Performance", devopsenablement, feature, ~"performance" -
#5330 (closed) Geo: Provide a way to disable pruning of the event log ~"Geo", Geo Administration, devopsenablement, feature -
#4769 (closed) Add option to trigger webhooks only after Geo replication has completed ~"Geo", ~"Geo Replication/Sync", customer+, devopsenablement, feature, settings, ~"webhooks" -
#4733 (closed) Active-active geo log cursors ~"Geo", Geo Next Gen, ~"Geo Performance", devopsenablement, feature, ha, ~"performance" -
#4591 (closed) Documentation : how to add optional Broadcast message when secondary is promoted ~"Accepting merge requests", ~"Documentation", ~"Geo", Geo Administration, devopsenablement, feature -
#4517 (closed) Full project mirroring between GitLab instances Architecture decision, ~"Geo", ~"Geo Replication/Sync", auto updated, devopsenablement, feature, popular proposal, potential proposal -
#4509 (closed) Allow Geo secondaries to override application settings ~"Geo", Geo Administration, auto updated, awaiting feedback, customer, devopsenablement, feature, needs investigation -
#4405 (closed) Enable local login in Geo secondary instance ~"Geo", Geo Administration, devopsenablement, feature -
#3942 (closed) Document active/passive high availability use-case for Geo/Disaster Recovery ~"Geo", auto updated, devopsenablement, feature -
#3789 (closed) Proposal for GitLab HA/Geo to use Consul ~"Geo", Geo Administration, devopsenablement, feature, ~"product discovery" -
#3448 (closed) Geo: Support clustered deployments with chained replication ~"Geo", ~"Geo Replication/Sync", customer, devopsenablement, feature -
#2859 (closed) Documentation : Ensure FQDNs are used in Geo ~"Documentation", ~"Geo", Geo Administration, devopsenablement, feature -
#1709 (closed) Investigate frontend changes for the "Auditor" user, to reuse in Geo ~"Accepting merge requests", ~"Geo", Geo Administration, UX, devopsenablement, feature -
#1381 (closed) Active active git replication ~"Accepting merge requests", ~"Geo", Geo Next Gen, ~"Geo Replication/Sync", devopsenablement, feature, meta
This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:
Edited by Fabian Zimmer